home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MERGING MediaPortal Url Source Splitter & IPTV Filter
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="georgius" data-source="post: 1136232" data-attributes="member: 107951"><p>Not implemented, so online videos can be watched only in OnlineVideos.</p><p></p><p></p><p>RTSP stream mostly should works, but ... stream must be MPEG 2 transport stream, not separate audio or video streams.</p><p></p><p></p><p>It was needed, because setting parameters directly in URL was very complicated. There is also option to test url and see if stream is compatible with TV service.</p><p></p><p></p><p>You can set different settings for each URL, so yes, you can set different settings for each filter instance. But ... these settings are in URL, so such URL must be stored in TV server database or must be scanned through scan playlist. Whole filter instance configuration is in URL, there are no common settings.</p><p></p><p></p><p>This is for discussion, but I don't think that's good idea. E.g. HTTP protocol hides M3U8 (Apple HTTP streaming, using MPEG2 TS, so it can be used with TV service), MSHS (Microsoft Smooth Streaming, not usable with TV server - yet) and AFHS (Adobe Flash HTTP Streaming, not usable with TV server - yet). RTMP is not usable with TV server (FLV video/audio stream), RTSP is usable, but only when MPEG2 TS stream is available, UDP/RTP is usable.</p><p></p><p>I'm not sure, how do you want to distinguish between provider's HTTP stream and online video M3U8 stream (watched through TV service). There will be probably different timeout settings and with highest probability also different network interface.</p><p></p><p>Also, as I write upper, there are no common settings, so everything must be passed in URL. So, in that case, each URL from database or playlist must be analysed by TV service, set required parameters and passed to filter. It's not impossible, only complicated.</p></blockquote><p></p>
[QUOTE="georgius, post: 1136232, member: 107951"] Not implemented, so online videos can be watched only in OnlineVideos. RTSP stream mostly should works, but ... stream must be MPEG 2 transport stream, not separate audio or video streams. It was needed, because setting parameters directly in URL was very complicated. There is also option to test url and see if stream is compatible with TV service. You can set different settings for each URL, so yes, you can set different settings for each filter instance. But ... these settings are in URL, so such URL must be stored in TV server database or must be scanned through scan playlist. Whole filter instance configuration is in URL, there are no common settings. This is for discussion, but I don't think that's good idea. E.g. HTTP protocol hides M3U8 (Apple HTTP streaming, using MPEG2 TS, so it can be used with TV service), MSHS (Microsoft Smooth Streaming, not usable with TV server - yet) and AFHS (Adobe Flash HTTP Streaming, not usable with TV server - yet). RTMP is not usable with TV server (FLV video/audio stream), RTSP is usable, but only when MPEG2 TS stream is available, UDP/RTP is usable. I'm not sure, how do you want to distinguish between provider's HTTP stream and online video M3U8 stream (watched through TV service). There will be probably different timeout settings and with highest probability also different network interface. Also, as I write upper, there are no common settings, so everything must be passed in URL. So, in that case, each URL from database or playlist must be analysed by TV service, set required parameters and passed to filter. It's not impossible, only complicated. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
MERGING MediaPortal Url Source Splitter & IPTV Filter
Contact us
RSS
Top
Bottom