Netherlands
- Thread starter
- #21
Sorry Mr HIPP
It doesn't work for me also. I'm setting my hopes on Charly's solution.
Gerwin
No scheduled resume from standby for recording (2 Viewers)
- Thread starter ggb
- Start date
Sorry Mr HIPP
It doesn't work for me also. I'm setting my hopes on Charly's solution.
Gerwin
No need for new loggs. I think I now what went wrong. ( thanks to charly). But we will not implement Charlie's solution, since it's kind of hack that coves the underlying problem (sorry Charlie) at least not as first hand choice.
Regards
Mr Hipp
Regards
Mr Hipp
Just confirming that I am also having this issue, using Vista (64bit) with latest SVN for MP.
Little note that I tried 'For the Record' 1.3.3 SVN and it wakes the computer fine (from standby) for the scheduled recording but does not record.
Look forward to a solution! Thanks.
Little note that I tried 'For the Record' 1.3.3 SVN and it wakes the computer fine (from standby) for the scheduled recording but does not record.
Look forward to a solution! Thanks.
- Thread starter
- #25
Mr Hipp
Charly's solution works perfect for me.
I will be awaiting your solution and will test it when its ready.
Gerwin
Charly's solution works perfect for me.
I will be awaiting your solution and will test it when its ready. Gerwin
Problem
I found following case in the release plan (1.0.2):
- 0001995: [TVServer Power Scheduler] [Vista Specific] When Reinitialize it's used & computer suspends with button/remote it fails to wakeup to event (MrHipp) - assigned.
This problem is huge, and have it not fixed before 1.0.2 causes the pain to continue at least until summer.
- Reinitialize flag ON: the PC doesn't wake up for recording, is S3 has been put with remote.
- Reinitialize flag OFF: the PC does wake up for recording even if S3 has been put with remote. The bad thing is that PC goes to S3 again, just before the recording is about to start, and the recording is missed. I have set wake up 2 minutes before recording, and the standby occures quite same time the recording should start. "Pre no shutdown time" is way larger, something like 15 minutes.
Otherwise I have no problems with any MediaPortal feature. I'll try to gather the logs about the issue, and hope the problem is fixed in 1.0.1, not in 1.0.2. I'm having latest SVN build. Anyone else having still similar problems?
Which is the more preferred and better working way? To re-initialize TVServer on resume, or not?
EDIT 1: Would it be sensible to implement a setting, where you can configure that no S3 if recording is starting in X minutes? Or does this "pre no shutdown time" in TVServer configuration mean exactly the same (if yes, better description for the setting would be good)?
EDIT 2: I have understood the wake up time is set when PC is going to S3. Would it be possible/sensible to set the wake up time every time you schedule a new recording or modify recordings?
EDIT 3: Added logs. In this case recording was scheduled at 23:50. PC was put to S3 by remote about 23:41. PC woke up 23:47, and went back to S3 at 23:49 ==> recording missed. No any user actions performed after resume. After the failure I manually started PC to gather the logs (that's why there is extra stuff in the end of the log, and recording is started). In this case the re-initialize setting was off.
I found following case in the release plan (1.0.2):
- 0001995: [TVServer Power Scheduler] [Vista Specific] When Reinitialize it's used & computer suspends with button/remote it fails to wakeup to event (MrHipp) - assigned.
This problem is huge, and have it not fixed before 1.0.2 causes the pain to continue at least until summer.
- Reinitialize flag ON: the PC doesn't wake up for recording, is S3 has been put with remote.
- Reinitialize flag OFF: the PC does wake up for recording even if S3 has been put with remote. The bad thing is that PC goes to S3 again, just before the recording is about to start, and the recording is missed. I have set wake up 2 minutes before recording, and the standby occures quite same time the recording should start. "Pre no shutdown time" is way larger, something like 15 minutes.
Otherwise I have no problems with any MediaPortal feature. I'll try to gather the logs about the issue, and hope the problem is fixed in 1.0.1, not in 1.0.2. I'm having latest SVN build. Anyone else having still similar problems?
Which is the more preferred and better working way? To re-initialize TVServer on resume, or not?
EDIT 1: Would it be sensible to implement a setting, where you can configure that no S3 if recording is starting in X minutes? Or does this "pre no shutdown time" in TVServer configuration mean exactly the same (if yes, better description for the setting would be good)?
EDIT 2: I have understood the wake up time is set when PC is going to S3. Would it be possible/sensible to set the wake up time every time you schedule a new recording or modify recordings?
EDIT 3: Added logs. In this case recording was scheduled at 23:50. PC was put to S3 by remote about 23:41. PC woke up 23:47, and went back to S3 at 23:49 ==> recording missed. No any user actions performed after resume. After the failure I manually started PC to gather the logs (that's why there is extra stuff in the end of the log, and recording is started). In this case the re-initialize setting was off.
As a workaround don't use the remote to initiate the S3 state. Leave it up to MediaPortal and you have no missed recordings.
Then you need to start coding yourself(Mr.Hipp it's working on it, but has a real life too)
Works fine here with latest SVN so logs required to go further.
Hmmm, this should be catch-ed in PS & disallow suspend(ofc if it's not initiated by remote), your logs idicate that it is not taken into account & thats a bug - need to check it & see if i has the same problem here.
Don't use it if you have no problems with card not working after suspend, only a workaround for "bad" drivers.
Btw: Post your system specification
Regards
Roy
"fix"
Update after a while. I have set the pre wake up time from 120 seconds to 60 seconds. Then there is no problem, and having "re-initialize tuners..." as false, I'm able to shut down and resume my PC every time. More than one month, no problems related to standby/resume or scheduled recordings. It's very nice when software is working this well.
Update after a while. I have set the pre wake up time from 120 seconds to 60 seconds. Then there is no problem, and having "re-initialize tuners..." as false, I'm able to shut down and resume my PC every time. More than one month, no problems related to standby/resume or scheduled recordings. It's very nice when software is working this well.