My very first failed recordings:-(

[Pob]

May have been a bit premature after posting about my initial success upgrading to 1.0.16!
I have never had a failed recording before, but have had two since switching to PVRX2.

I hibernated the PC last night, and it turned on to record today. First sign of a problem was that the PC was still running some hours later - it did not hibernate again after the usual 30 minutes.
I turned on the monitor but it was just a black screen - no reponse to any key presses. I had to CTRL-ALT-DEL to get control of the PC. First thing I did was to check the recording, and it was there, but when I tried to play it, it only lasted for a few seconds. Checked the file and it is only 634kb...

Unfortunately I only had error logging enabled, so I scheduled a manual recording from 7.40pm to 7.50pm, and put the system into hibernate again from the System menu in PVRX2. This time the recording file was larger - 156mb - but it only plays for a few seconds before the video freezes (Logs attached). Loaded it into VideoRedo to analyse and these are the results:
Audio frame errors: 171
Input Sequence Errors: 658
Video resync frames removed: 224
Audio resync frames removed: 523
Video output frames: 6984
Audio output frames: 11641
I should stress that recordings done without the PC waking from hibernate have been fine - it definately seems to be a problem with the PC waking from hiberbnate to record...
I am using Cyberlink mux v1307 on a Hauppage Nova-T 9002 DVB-T card.
Pob

[Pob]

I have narrowed this down a bit. The problem seems to be that, on wake from hibernate, PVRX2 -fse is using 99% of cpu resources. This results in either a failed recording, or at least a recording so full of errors that it will not play.

If the PC is hibernated AFTER PVRX2 -fse is exited - then recordings are fine - in fact better than before, as the recordings are totally free of errors (I always used to get a few) and the recording service only uses 3-5% of CPU resources.

So the issue is using hibernate from within the PVRX2 -fse system menu. I don't want to get out of bed to turn off the PC last thing at night!, so one way around this would be to exit PVRX2 first, and then use one of the remote buttons to hibernate the PC. No idea how to do this though - I can only find remote command to shutdown the PC...
Pob

[Pob]

I did search the forums before posting the OT, honest!, but I searched for failed recordings - now I have seen posts like this:
http://forums.nextpvr.com/showthread.php...+hibernate
which seems to be about the same issue, so will wait for a future release. In the meantime a Hauppage 45-button remote command to hibernate windoze would be much appreciated!
Pob

[Pob]

I did search the forums before posting the OT, honest!, but I searched for failed recordings - now I have seen posts like this:
http://forums.nextpvr.com/showthread.php...+hibernate
which seems to be about the same issue, so will wait for a future release. In the meantime a Hauppage 45-button remote command to hibernate windoze would be much appreciated!
Pob

And looking for through the forums found me this thread:
http://forums.nextpvr.com/showthread.php...+hibernate
So I just used the ={run(rundll32.exe powrprof.dll,SetSuspendState)} in the default section of Irremote.ini, so I can now hibernate from the desktop, and all problems now worked around.

[COLOR="Navy"][Default]
OLD0=
0=
1=
2=
3=
4=
5=
6=
7=
8=
9=
SOURCE={switch(*task*)}{shift}{tab}
MINIMIZE=
FULLSCREEN={alt}{space}x
RESERVED=

; close current active window; disabled for now
;GRNPOWER={sys(0xF060)}

GRNPOWER={run(C:\Progra~1\devnz\gbpvr\PVRX2.exe -fse)}
BLUE={run(C:reschange.exe -width=1280 -height=720 -refresh=50)}
YELLOW={run(C:reschange.exe -width=1360 -height=768 -refresh=60)}
GREEN={run(C:reschange.exe -width=1280 -height=720 -refresh=60)}
RED={run(rundll32.exe powrprof.dll,SetSuspendState)}[/COLOR]

[sub]

I have narrowed this down a bit. The problem seems to be that, on wake from hibernate, PVRX2 -fse is using 99% of cpu resources. This results in either a failed recording, or at least a recording so full of errors that it will not play.

If the PC is hibernated AFTER PVRX2 -fse is exited - then recordings are fine - in fact better than before, as the recordings are totally free of errors (I always used to get a few) and the recording service only uses 3-5% of CPU resources.

So the issue is using hibernate from within the PVRX2 -fse system menu. I don't want to get out of bed to turn off the PC last thing at night!, so one way around this would be to exit PVRX2 first, and then use one of the remote buttons to hibernate the PC. No idea how to do this though - I can only find remote command to shutdown the PC...
Pob

Have you applied this patch from the survival guide: http://forums.gbpvr.com/showpost.php?p=2...ostcount=4?

I'm aware that there has been a couple of people it didnt work for, but it seems to have worked for the majority of users.

[Pob]

Have you applied this patch from the survival guide: http://forums.gbpvr.com/showpost.php?p=2...ostcount=4?

I'm aware that there has been a couple of people it didnt work for, but it seems to have worked for the majority of users.

Yes I did install all the patches from the survival guide before starting PVRX2-fse for the first time, including the delayed start.
The only error I could see in the logs when the PC woke from hibernate was:
2007-10-27 19:38:00.546 ERROR m_pD3D->CreateDevice(displayAdapter, D3DDEVTYPE_HAL, m_hWnd, dwBehaviour, &pp, &m_pD3DDev) failed
Error code : 88760868
D3DERR_DEVICELOST
Device lost

[sub]

2007-10-27 19:38:00.546 ERROR m_pD3D->CreateDevice(displayAdapter, D3DDEVTYPE_HAL, m_hWnd, dwBehaviour, &pp, &m_pD3DDev) failed
Error code : 88760868
D3DERR_DEVICELOST

This is the specific thing that delayed start was supposed to address.

If you reproduce the problem then zip and attach a set of logs, I'll take a look.

[Pob]

This is the specific thing that delayed start was supposed to address.

If you reproduce the problem then zip and attach a set of logs, I'll take a look.

I did recreate the problem and the logs were attached with the first post...the recording was 7.40pm to 7.50pm yesterday, the 27th.
Pob

[sub]

Sorry, didnt notice them

2007-10-27 19:38:00.546 VERBOSE [1] System is waking from low power state...
2007-10-27 19:38:00.546 VERBOSE [1] FSE mode, so needs restart...

I can see you're missing the message that normally follows this, like the other couple of users that problems with this. I've put a change in to the next release to help with this. Unfortunately I'm unable to supply it as a patch since my build is no longer compatible with 1.0.16.

[Pob]

Sorry, didnt notice them

I can see you're missing the message that normally follows this, like the other couple of users that problems with this. I've put a change in to the next release to help with this. Unfortunately I'm unable to supply it as a patch since my build is no longer compatible with 1.0.16.

Thank you Sub.