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
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Scheduled recordings fail to start with HDHomerun
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: 1154323" data-attributes="member: 82144"><p>Thank you for the direct answers. <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>More questions coming...</p><p></p><p></p><p>To be clear: the "Les feux de l'amour" recording from TF1 HD (same frequency as France 2 HD) <em>started</em> only 5 minutes before the errors with France 2 HD started and ended after 3 PM, when the problem had been going on for at least an hour. If that recording is completely okay, it seems to mean that the problem must have been triggered between 13:55 - 14:00.</p><p></p><p>Have you checked the Windows application and system event log files for the corresponding period to see if anything stands out?</p><p>You also had a "Journal" recording on France 2 HD that finished at 14:00:02. Would I be correct to assume that recording was also completely okay right until the end?</p><p></p><p></p><p>Okay.</p><p></p><p></p><p>Okay, please let me know if you find/hear anything. <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>Ahhh, this problem is more and more interesting! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>In all my years working on MediaPortal I have never read a problem report where that happens.</p><p></p><p>Are you sure that the network link to the HDHR is not dropping out? (...router/switch failure, DHCP IP address expiry/renewal, security/firewall software failure, high network load???)</p><p></p><p></p><p>Yes, that is a good test. <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>In the case of the failure of "Toute une histoire", tuner 5 was already tuned to the correct frequency (for recording "Les feux de l'amour"). Therefore no tune request was sent; only signal was checked. That is when you see the first "could not lock onto channel - no signal or bad signal" message. On the other hand, tuner 6 was idle so TV Server was definitely sending proper tune requests to that tuner. The time taken for tuning is quite extreme:</p><p>[2015-09-28 14:00:<strong>06</strong>,562] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest calling put_TuneRequest</p><p>[2015-09-28 14:00:<strong>09</strong>,890] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest done calling put_TuneRequest</p><p></p><p>That's more than 3 seconds. Normally it should be <em>much</em> faster - approximately 50 milliseconds. For comparison:</p><p>[2015-09-28 11:45:04,349] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest calling put_TuneRequest</p><p>[2015-09-28 11:45:04,380] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest done calling put_TuneRequest</p><p></p><p>[2015-09-28 12:00:11,399] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest calling put_TuneRequest</p><p>[2015-09-28 12:00:11,455] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest done calling put_TuneRequest</p><p></p><p>[2015-09-28 13:00:03,269] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest calling put_TuneRequest</p><p>[2015-09-28 13:00:03,303] [Log ] [scheduler thread] [INFO ] - dvb<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ubmit tunerequest done calling put_TuneRequest</p><p></p><p>It seems to me that when the problem happens, something is definitely wrong with the tuner or with the network link...</p><p></p><p>Regards,</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1154323, member: 82144"] Thank you for the direct answers. :) More questions coming... To be clear: the "Les feux de l'amour" recording from TF1 HD (same frequency as France 2 HD) [I]started[/I] only 5 minutes before the errors with France 2 HD started and ended after 3 PM, when the problem had been going on for at least an hour. If that recording is completely okay, it seems to mean that the problem must have been triggered between 13:55 - 14:00. Have you checked the Windows application and system event log files for the corresponding period to see if anything stands out? You also had a "Journal" recording on France 2 HD that finished at 14:00:02. Would I be correct to assume that recording was also completely okay right until the end? Okay. Okay, please let me know if you find/hear anything. :) Ahhh, this problem is more and more interesting! :) In all my years working on MediaPortal I have never read a problem report where that happens. Are you sure that the network link to the HDHR is not dropping out? (...router/switch failure, DHCP IP address expiry/renewal, security/firewall software failure, high network load???) Yes, that is a good test. :) In the case of the failure of "Toute une histoire", tuner 5 was already tuned to the correct frequency (for recording "Les feux de l'amour"). Therefore no tune request was sent; only signal was checked. That is when you see the first "could not lock onto channel - no signal or bad signal" message. On the other hand, tuner 6 was idle so TV Server was definitely sending proper tune requests to that tuner. The time taken for tuning is quite extreme: [2015-09-28 14:00:[B]06[/B],562] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest calling put_TuneRequest [2015-09-28 14:00:[B]09[/B],890] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest done calling put_TuneRequest That's more than 3 seconds. Normally it should be [I]much[/I] faster - approximately 50 milliseconds. For comparison: [2015-09-28 11:45:04,349] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest calling put_TuneRequest [2015-09-28 11:45:04,380] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest done calling put_TuneRequest [2015-09-28 12:00:11,399] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest calling put_TuneRequest [2015-09-28 12:00:11,455] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest done calling put_TuneRequest [2015-09-28 13:00:03,269] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest calling put_TuneRequest [2015-09-28 13:00:03,303] [Log ] [scheduler thread] [INFO ] - dvb:Submit tunerequest done calling put_TuneRequest It seems to me that when the problem happens, something is definitely wrong with the tuner or with the network link... Regards, mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
Scheduled recordings fail to start with HDHomerun
Contact us
RSS
Top
Bottom