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: 1049575" data-attributes="member: 82144"><p>Hello again John</p><p></p><p></p><p>Okay - so tuners not detected. The logs confirm this.</p><p></p><p></p><p>The tuners are listed because TV Server knew about them previously. It hasn't actually detected the tuners at all.</p><p></p><p></p><p>Yes, so that is what you'd normally expect to see. Tuners detected and available for use within ~5 seconds.</p><p></p><p></p><p>As far as I'm aware, QuickTV and N-PVR both use libhdhomerun for their HDHR support. Without getting into too much detail, libhdhomerun uses a proprietary way of detecting and controlling the tuners (which is why Ceton tuners aren't natively supported by N-PVR). MP uses standard non-proprietary communication/interfaces. In other words, it isn't really a fair comparison... but I do take your point that the tuners are available on the network.</p><p></p><p></p><p>Thanks <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up (y)" loading="lazy" data-shortname="(y)" /></p><p>TV Server is clearly having trouble detecting your tuners.</p><p>One thing that doesn't help is that it appears you have "delay before detecting..." set to 15 seconds:</p><p><a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/06_General#Delay_for_TV_card_detection" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/06_General#Delay_for_TV_card_detection</a></p><p></p><p>Please set that back down to zero.</p><p></p><p></p><p>It was a good test.</p><p>Did you also try disabling all firewalls as suggested? The process for this test would be:</p><ol> <li data-xf-list-type="ol">Disable all firewalls.</li> <li data-xf-list-type="ol">Restart the TV service.</li> <li data-xf-list-type="ol">Check how quickly the tuners are detected automatically.</li> </ol><p>In other words, don't reboot the tuner.</p><p></p><p>Another thing you can try is disabling IPv6 on your network adaptor.</p><p><a href="http://support.microsoft.com/kb/929852" target="_blank">http://support.microsoft.com/kb/929852</a></p><p>Refer to the steps under the heading "Unbind IPv6 from a specific network adapter".</p><p></p><p>Finally, I've also attached a debug tool which should pick up all the UPnP devices on your network. Can you please:</p><ol> <li data-xf-list-type="ol">Download and extract the files into a folder somewhere on the TV Server PC.</li> <li data-xf-list-type="ol">Run UPnPDeviceSpy.exe.</li> <li data-xf-list-type="ol">See how long it takes for it to pick up your PRIME.</li> </ol><p>I note this tool uses the exact same code as TV Server does... so if it is able to detect your tuner quickly, it tells us that the problem is with TV Server or configuration for TV Server (ie. both TV Server configuration and external configuration like firewalls etc.). If not, it tells us there is some kind of funky network issue in your environment or we have a code problem.</p><p>I also note that the tool should list two entries for the PRIME - a DRI (ie. native CableLabs tuner) interface and a DLNA interface (which is part of the Silicondust project connect thing).</p><p></p><p>Hopefully I haven't confused you with such a long reply. Summary of key points:</p><ol> <li data-xf-list-type="ol">I acknowledge TV Server is having trouble detecting your tuner.</li> <li data-xf-list-type="ol">I'm suggesting three things you can try to help resolve the problem:<ul> <li data-xf-list-type="ul">disable all firewalls</li> <li data-xf-list-type="ul">disable IPv6 on your network adaptors<br /> </li> <li data-xf-list-type="ul">try the MP2 device spy tool</li> </ul></li> </ol><p>Please don't hesitate to ask if you have any questions. Looking forward to the test results... <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>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1049575, member: 82144"] Hello again John Okay - so tuners not detected. The logs confirm this. The tuners are listed because TV Server knew about them previously. It hasn't actually detected the tuners at all. Yes, so that is what you'd normally expect to see. Tuners detected and available for use within ~5 seconds. As far as I'm aware, QuickTV and N-PVR both use libhdhomerun for their HDHR support. Without getting into too much detail, libhdhomerun uses a proprietary way of detecting and controlling the tuners (which is why Ceton tuners aren't natively supported by N-PVR). MP uses standard non-proprietary communication/interfaces. In other words, it isn't really a fair comparison... but I do take your point that the tuners are available on the network. Thanks (y) TV Server is clearly having trouble detecting your tuners. One thing that doesn't help is that it appears you have "delay before detecting..." set to 15 seconds: [url]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/06_General#Delay_for_TV_card_detection[/url] Please set that back down to zero. It was a good test. Did you also try disabling all firewalls as suggested? The process for this test would be: [LIST=1] [*]Disable all firewalls. [*]Restart the TV service. [*]Check how quickly the tuners are detected automatically. [/LIST] In other words, don't reboot the tuner. Another thing you can try is disabling IPv6 on your network adaptor. [url]http://support.microsoft.com/kb/929852[/url] Refer to the steps under the heading "Unbind IPv6 from a specific network adapter". Finally, I've also attached a debug tool which should pick up all the UPnP devices on your network. Can you please: [LIST=1] [*]Download and extract the files into a folder somewhere on the TV Server PC. [*]Run UPnPDeviceSpy.exe. [*]See how long it takes for it to pick up your PRIME. [/LIST] I note this tool uses the exact same code as TV Server does... so if it is able to detect your tuner quickly, it tells us that the problem is with TV Server or configuration for TV Server (ie. both TV Server configuration and external configuration like firewalls etc.). If not, it tells us there is some kind of funky network issue in your environment or we have a code problem. I also note that the tool should list two entries for the PRIME - a DRI (ie. native CableLabs tuner) interface and a DLNA interface (which is part of the Silicondust project connect thing). Hopefully I haven't confused you with such a long reply. Summary of key points: [LIST=1] [*]I acknowledge TV Server is having trouble detecting your tuner. [*]I'm suggesting three things you can try to help resolve the problem: [LIST] [*]disable all firewalls [*]disable IPv6 on your network adaptors [*]try the MP2 device spy tool [/LIST] [/LIST] Please don't hesitate to ask if you have any questions. Looking forward to the test results... :) mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Products
MPTvClient (stand alone TV client)
HDHomerun Prime & MediaPortal 1.5
Contact us
RSS
Top
Bottom