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
Submit: code patches (MediaPortal/TV-Server/etc.)
DVB-IP scanning improvements
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="AlexPlas" data-source="post: 748511" data-attributes="member: 24336"><p>What is the reason why I haven't change URLs for UDP and RTP protocols? I think about it like about DiSEqC parameters for satellite receiving. User has to setup something which cannot be specified in common tuning parameters, because it does depend on user's hardware configurations. There are additional fields for DVB-S channels, we can add such additional filed for DVB-IP channels, but I think it's unnecessary.</p><p></p><p>Let's parse UDP URL structure. There are only four possible elements - protocol, binding address (optional), multicast address and port. I think that URLs in tuning parameters must not contain binding address, because it's make it specific for only one user and unusable as a result. So, my change of URL its only addition of one parameter which is always absent in original URL. Anyway I translate one valid URL into another valid URL, which is conforming to standard (unofficial for now).</p></blockquote><p></p>
[QUOTE="AlexPlas, post: 748511, member: 24336"] What is the reason why I haven't change URLs for UDP and RTP protocols? I think about it like about DiSEqC parameters for satellite receiving. User has to setup something which cannot be specified in common tuning parameters, because it does depend on user's hardware configurations. There are additional fields for DVB-S channels, we can add such additional filed for DVB-IP channels, but I think it's unnecessary. Let's parse UDP URL structure. There are only four possible elements - protocol, binding address (optional), multicast address and port. I think that URLs in tuning parameters must not contain binding address, because it's make it specific for only one user and unusable as a result. So, my change of URL its only addition of one parameter which is always absent in original URL. Anyway I translate one valid URL into another valid URL, which is conforming to standard (unofficial for now). [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Submit: code patches (MediaPortal/TV-Server/etc.)
DVB-IP scanning improvements
Contact us
RSS
Top
Bottom