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
General Support
Recording stuck in endless loop
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: 1159570" data-attributes="member: 82144"><p>Hello again Jim</p><p></p><p>With regard to the computer addresses...</p><p>I have to confess that I should have looked at your previous log files more closely. If I had looked more closely I would have seen that the tuner is a PCIe tuner rather than an ETH one. That fact explains why your computer has 2 addresses. One address is the connection to your local network; the other is the connection/interface to your tuner.</p><p></p><p>So, that avenue of enquiry is mostly a dead end. However, I think there's one important thing to note, and that is that TV Server should always expect to detect that your computer has 2 addresses. The fact that it doesn't is interesting and causes me to wonder whether the redetection is related to driver reinitialisation after resume.</p><p></p><p>It's frustrating to not know exactly what is going on. However, it should still be possible to work around the problem by increasing the value of the PowerScheduler "pre-wakeup time..." setting. You can find that setting within the PowerScheduler plugin settings in TV Server Configuration; enable "expert mode", then go to the "legacy" tab. Increasing the value to something like 180 seconds (3 minutes) should allow enough time for TV Server to wake, detect the tuner, lose the tuner, then finally redetect the tuner before a recording has to start.</p><p></p><p>Regards,</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1159570, member: 82144"] Hello again Jim With regard to the computer addresses... I have to confess that I should have looked at your previous log files more closely. If I had looked more closely I would have seen that the tuner is a PCIe tuner rather than an ETH one. That fact explains why your computer has 2 addresses. One address is the connection to your local network; the other is the connection/interface to your tuner. So, that avenue of enquiry is mostly a dead end. However, I think there's one important thing to note, and that is that TV Server should always expect to detect that your computer has 2 addresses. The fact that it doesn't is interesting and causes me to wonder whether the redetection is related to driver reinitialisation after resume. It's frustrating to not know exactly what is going on. However, it should still be possible to work around the problem by increasing the value of the PowerScheduler "pre-wakeup time..." setting. You can find that setting within the PowerScheduler plugin settings in TV Server Configuration; enable "expert mode", then go to the "legacy" tab. Increasing the value to something like 180 seconds (3 minutes) should allow enough time for TV Server to wake, detect the tuner, lose the tuner, then finally redetect the tuner before a recording has to start. Regards, mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Recording stuck in endless loop
Contact us
RSS
Top
Bottom