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="mm1352000" data-source="post: 1136261" data-attributes="member: 82144"><p>Understood, thank you. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p></p><p>I think you misunderstood.</p><p>With the old filter there was filter configuration [in MPIPTVSource.ini] and separate URL configuration. I'm talking about the "MPIPTVSource.ini" settings. From your new code, it looks like those settings are stored in MediaPortalIptvFilterAndUrlSourceSplitter.xml:</p><p><a href="https://github.com/MediaPortal/MediaPortal-1/blob/MP1-4155-FEAT-Merge_of_IPTV_filter_and_MediaPortal_Url_Source_Splitter/TvEngine3/TVLibrary/Plugins/MediaPortalIptvFilterAndUrlSourceSplitter/Settings.cs#L102" target="_blank">https://github.com/MediaPortal/MediaPortal-1/blob/MP1-4155-FEAT-Merge_of_IPTV_filter_and_MediaPortal_Url_Source_Splitter/TvEngine3/TVLibrary/Plugins/MediaPortalIptvFilterAndUrlSourceSplitter/Settings.cs#L102</a></p><p><a href="https://github.com/MediaPortal/MediaPortal-1/blob/MP1-4155-FEAT-Merge_of_IPTV_filter_and_MediaPortal_Url_Source_Splitter/TvEngine3/TVLibrary/Plugins/MediaPortalIptvFilterAndUrlSourceSplitter/Settings.cs#L115" target="_blank">https://github.com/MediaPortal/MediaPortal-1/blob/MP1-4155-FEAT-Merge_of_IPTV_filter_and_MediaPortal_Url_Source_Splitter/TvEngine3/TVLibrary/Plugins/MediaPortalIptvFilterAndUrlSourceSplitter/Settings.cs#L115</a></p><p></p><p>...not in the URL.</p><p></p><p></p><p>I was not saying that people should have one IPTV tuner per protocol. Just have one tuner per "needed different settings" (it's hard to describe! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> ).</p><p></p><p>So for example, say that person X receives RTSP streams from their IPTV provider, and also has a SAT>IP network tuner [which also uses RTSP]. For best results/compatibility, these two sources need different settings (definitely different network interface, maybe different open connection timeout, client port range etc.). How can this be done?</p><p></p><p>Right now I'm not sure if it is possible. Maybe you can set default values in MediaPortalIptvFilterAndUrlSourceSplitter.xml for the SAT>IP tuner... and then somehow override the defaults with the IPTV provider channel URLs. However, this is not very manageable when each source/provider has hundreds of channels.</p><p></p><p>My suggestion is that person X could create 2 tuners - 1 for the IPTV provider and 1 for the SAT>IP tuner. Each tuner would get its own filter with its own settings (stored in TVE database eg. "Card" table).</p><p></p><p>Now, maybe person X also wants to receive some HTTP streams from a closed circuit camera on their network. The settings for the SAT>IP network tuner (network interface, connection timeout etc.) are okay for the closed circuit camera too... so the existing tuner can be used for both sources (HTTP and RTSP). To be clear, there is only one "preferred network interface" setting which is shared for all protocols. If person X has sources which need different values of "preferred network interface", create another tuner with the different setting.</p><p></p><p>Does it make sense?</p><p></p><p></p><p>Just create 2 tuners - 1 for the provider streams, and another tuner for the M3U8 streams - and assign the required timeout, network interface etc. to each. Channels are mapped/linked only to the tuner with the correct settings.</p><p></p><p></p><p>When I say "common" I mean...</p><p>RTSP, RTMP, RTP/UDP, HTTP... all have [for example] a "preferred network interface" setting.</p><p>Currently you have [for example] 4 settings:</p><ul> <li data-xf-list-type="ul">RTSP preferred network interface</li> <li data-xf-list-type="ul">RTMP preferred network interface</li> <li data-xf-list-type="ul">RTP/UDP preferred network interface</li> <li data-xf-list-type="ul">HTTP preferred network interface</li> </ul><p>I am suggesting to have 1 "preferred network interface" setting (shared for all protocols) instead of 4. I think that might be more flexible and simpler for the code and for the end-user.</p><p>For the code...</p><p>What happens if you add support for another protocol (eg. M3U8)? Do you have to add another setting? No, the existing setting will be reused.</p><p>What happens if the user wants to access streams with different preferred network interface values? Just create another tuner. That way the user can also have different preferred network interface for streams which use the same protocol (eg. HTTP provider and web stream, or RTSP provider and network tuner).</p><p></p><p></p><p>But what about MediaPortalIptvFilterAndUrlSourceSplitter.xml/MPIPTVSource.ini? Doesn't the filter read that file directly?</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1136261, member: 82144"] Understood, thank you. :) I think you misunderstood. With the old filter there was filter configuration [in MPIPTVSource.ini] and separate URL configuration. I'm talking about the "MPIPTVSource.ini" settings. From your new code, it looks like those settings are stored in MediaPortalIptvFilterAndUrlSourceSplitter.xml: [URL]https://github.com/MediaPortal/MediaPortal-1/blob/MP1-4155-FEAT-Merge_of_IPTV_filter_and_MediaPortal_Url_Source_Splitter/TvEngine3/TVLibrary/Plugins/MediaPortalIptvFilterAndUrlSourceSplitter/Settings.cs#L102[/URL] [URL]https://github.com/MediaPortal/MediaPortal-1/blob/MP1-4155-FEAT-Merge_of_IPTV_filter_and_MediaPortal_Url_Source_Splitter/TvEngine3/TVLibrary/Plugins/MediaPortalIptvFilterAndUrlSourceSplitter/Settings.cs#L115[/URL] ...not in the URL. I was not saying that people should have one IPTV tuner per protocol. Just have one tuner per "needed different settings" (it's hard to describe! :) ). So for example, say that person X receives RTSP streams from their IPTV provider, and also has a SAT>IP network tuner [which also uses RTSP]. For best results/compatibility, these two sources need different settings (definitely different network interface, maybe different open connection timeout, client port range etc.). How can this be done? Right now I'm not sure if it is possible. Maybe you can set default values in MediaPortalIptvFilterAndUrlSourceSplitter.xml for the SAT>IP tuner... and then somehow override the defaults with the IPTV provider channel URLs. However, this is not very manageable when each source/provider has hundreds of channels. My suggestion is that person X could create 2 tuners - 1 for the IPTV provider and 1 for the SAT>IP tuner. Each tuner would get its own filter with its own settings (stored in TVE database eg. "Card" table). Now, maybe person X also wants to receive some HTTP streams from a closed circuit camera on their network. The settings for the SAT>IP network tuner (network interface, connection timeout etc.) are okay for the closed circuit camera too... so the existing tuner can be used for both sources (HTTP and RTSP). To be clear, there is only one "preferred network interface" setting which is shared for all protocols. If person X has sources which need different values of "preferred network interface", create another tuner with the different setting. Does it make sense? Just create 2 tuners - 1 for the provider streams, and another tuner for the M3U8 streams - and assign the required timeout, network interface etc. to each. Channels are mapped/linked only to the tuner with the correct settings. When I say "common" I mean... RTSP, RTMP, RTP/UDP, HTTP... all have [for example] a "preferred network interface" setting. Currently you have [for example] 4 settings: [LIST] [*]RTSP preferred network interface [*]RTMP preferred network interface [*]RTP/UDP preferred network interface [*]HTTP preferred network interface [/LIST] I am suggesting to have 1 "preferred network interface" setting (shared for all protocols) instead of 4. I think that might be more flexible and simpler for the code and for the end-user. For the code... What happens if you add support for another protocol (eg. M3U8)? Do you have to add another setting? No, the existing setting will be reused. What happens if the user wants to access streams with different preferred network interface values? Just create another tuner. That way the user can also have different preferred network interface for streams which use the same protocol (eg. HTTP provider and web stream, or RTSP provider and network tuner). But what about MediaPortalIptvFilterAndUrlSourceSplitter.xml/MPIPTVSource.ini? Doesn't the filter read that file directly? [/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