2009-11-12, 03:33 AM
Hello dears,
I would like to give notice about the problem with wake-up functionality.
If I do the following steps:
- schedule manually new recording for example for 5:00 am ,
- close GBPVR software
- go to GBPVR again, update pending recording: change the time from 5:00 am to 10:00 am
The effect will be:
- computer wakes up at 5:00, but nothing records
- if will be computer at 10:00 on, recording will be done, but if computer will be in stand-by mode, it doesn't wake up and nothing will be recorded
Simple said: update of date/time in pending recording doesn't update wake-up events .
You can also see it in GBPVRRecordingService.exe-native.log .
I have done exactly these steps and file contained only first setting of wake-up event:
2009-11-12 03:55:12.640 INFO Log started
2009-11-12 03:55:12.640 VERBOSE getSetting(LoggingLevel)
2009-11-12 03:55:12.671 INFO Logging Level is Debug
2009-11-12 03:55:12.671 VERBOSE getSetting(LoggingForceFlush)
2009-11-12 03:55:12.671 INFO Log flushing enabled
2009-11-12 03:55:12.671 VERBOSE Asking Windows to be awake for recording (oid: 5) at 2009-11-12 4:57:30 (UTC 2009-11-12 3:57:30)
Is it possible to repair this bug or is there any way to avoid this bug ? ( also "deletion" of update button in detailed screen for pending recording would be better than AS-IS state )
Thanks a lot
Roman
I would like to give notice about the problem with wake-up functionality.
If I do the following steps:
- schedule manually new recording for example for 5:00 am ,
- close GBPVR software
- go to GBPVR again, update pending recording: change the time from 5:00 am to 10:00 am
The effect will be:
- computer wakes up at 5:00, but nothing records
- if will be computer at 10:00 on, recording will be done, but if computer will be in stand-by mode, it doesn't wake up and nothing will be recorded
Simple said: update of date/time in pending recording doesn't update wake-up events .
You can also see it in GBPVRRecordingService.exe-native.log .
I have done exactly these steps and file contained only first setting of wake-up event:
2009-11-12 03:55:12.640 INFO Log started
2009-11-12 03:55:12.640 VERBOSE getSetting(LoggingLevel)
2009-11-12 03:55:12.671 INFO Logging Level is Debug
2009-11-12 03:55:12.671 VERBOSE getSetting(LoggingForceFlush)
2009-11-12 03:55:12.671 INFO Log flushing enabled
2009-11-12 03:55:12.671 VERBOSE Asking Windows to be awake for recording (oid: 5) at 2009-11-12 4:57:30 (UTC 2009-11-12 3:57:30)
Is it possible to repair this bug or is there any way to avoid this bug ? ( also "deletion" of update button in detailed screen for pending recording would be better than AS-IS state )
Thanks a lot
Roman