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
Products
MPTvClient (stand alone TV client)
HDHomerun Prime & MediaPortal 1.5
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: 1053436" data-attributes="member: 82144"><p>Thanks Valk <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>TVE 3 (MP1) only for the moment.</p><p></p><p></p><p>It does.</p><p></p><p></p><p>It is not DLNA.</p><p>Basically it is a UPnP tuner.</p><p>Device discovery is SSDP; tuning is custom interfaces defined by CableLabs (US cable TV organisation); streaming is standard UPnP connection manager and AV transport services.</p><p></p><p></p><p>I'm not asking you to tackle code, and definitely not asking you to understand how CableCARD tuners work. I was only hoping that with your superior understanding of the MP2 UPnP and Windows networking stacks that you might be able to suggest a way to debug this problem.</p><p></p><p>The problem here is very narrow and fundamental.</p><p>In as few words as I can say it...</p><p>Both TVE 3 and the MP2 UPnP device spy tool use the same UPnP DLLs.</p><p>The device spy tool detects the tuner immediately.</p><p>TVE 3 can't detect the tuner until the tuner broadcasts NOTIFY packets.</p><p></p><p>In other words, seems like there is a difference in behaviour of the SSDP code when using M-SEARCH due to the different environment in which the library is used. Could be a network or configuration issue. I don't know.</p><p></p><p>Still nothing? (I had to ask... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /> )</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1053436, member: 82144"] Thanks Valk :) TVE 3 (MP1) only for the moment. It does. It is not DLNA. Basically it is a UPnP tuner. Device discovery is SSDP; tuning is custom interfaces defined by CableLabs (US cable TV organisation); streaming is standard UPnP connection manager and AV transport services. I'm not asking you to tackle code, and definitely not asking you to understand how CableCARD tuners work. I was only hoping that with your superior understanding of the MP2 UPnP and Windows networking stacks that you might be able to suggest a way to debug this problem. The problem here is very narrow and fundamental. In as few words as I can say it... Both TVE 3 and the MP2 UPnP device spy tool use the same UPnP DLLs. The device spy tool detects the tuner immediately. TVE 3 can't detect the tuner until the tuner broadcasts NOTIFY packets. In other words, seems like there is a difference in behaviour of the SSDP code when using M-SEARCH due to the different environment in which the library is used. Could be a network or configuration issue. I don't know. Still nothing? (I had to ask... :P ) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
MPTvClient (stand alone TV client)
HDHomerun Prime & MediaPortal 1.5
Contact us
RSS
Top
Bottom