Pause/Resume problem

[time_lord]

Hi I've seen a few posts regarding the issue where resuming playback from pause causes problems, but nothing quite fits my situation (I think).
I'm often watching recordings on my PC so using the keyboard. These are dvb-t recordings; I have an hvr2200 dual-tuner hybrid capture card.

If I pause (ctrl-Q) a recording for a few seconds, when I unpause (ctrl-Q) the audio resumes immediately but the picture remains 'frozen'. After 3-4 seconds of audio it stops. If I ctrl-Q to pause again (appears to do nothing - no surprise because it should be going back into pause) then unpause, playback resumes and there's no problem.
I can repeat this pretty much every time - first unpause it fails to resume properly but the second unpause it's ok. I.e I can pause/unpause repeatedly and every alternate unpause it fails to resume properly.
Also from what I recall, when it fails to resume correctly, if I hit ctrl-D (to rewind a little), then it plays from there and continues to play ok.

Another slighly related issue... in my config I have my fastforward step to be 30 seconds. But when I click ctrl-F it only seems to advance 15 seconds... is this somehow related to the situation??

Any ideas?

[sub]

Another slighly related issue... in my config I have my fastforward step to be 30 seconds. But when I click ctrl-F it only seems to advance 15 seconds... is this somehow related to the situation??

The skip times in the config app relate to the skip keys (Ctrl-RightArrow/Ctrl-LeftArrow), rather than the FF/RW keys.

I'm not sure on the other thing. Maybe set the audio renderer back to 'system default' if you havnt already got it set this way.

[time_lord]

The skip times in the config app relate to the skip keys (Ctrl-RightArrow/Ctrl-LeftArrow), rather than the FF/RW keys.

errr... is there a difference?

I'm not sure on the other thing. Maybe set the audio renderer back to 'system default' if you havnt already got it set this way.

Pretty sure I do have it set to system default. Nothing to do with our AAC encoding? (I assume not otherwise everyone would have this problem?)

[sub]

errr... is there a difference?

Yes there is a difference. By default the skip keys (Ctrl-Right/Ctrl-Left) will jump forward 60 seconds, or back 30 seconds, or whatever you've changed them to in the config app. The FF/RW keys (Ctrl-F/Ctrl-D) will jump forward/back 10 seconds.

Pretty sure I do have it set to system default. Nothing to do with our AAC encoding? (I assume not otherwise everyone would have this problem?)

Maybe. I dont know.

[Reddwarf]

I have the very same problem, but I havent botherd to report it since a small skip-backwards seems to solve the problem. It appares also when I play a show during recording of it. I'm only using analog tv, with hauppage PVR150 ant ATI550 cards.

[time_lord]

I'm not sure on the other thing. Maybe set the audio renderer back to 'system default' if you havnt already got it set this way.

Ok, as it turns out I had both the "AAC Decoder" and "HE-AAC Decoder" set to the Monogram aac decoder... I went back to system defaults and the problem still happens - pvrx2 fails to resume properly after pausing.

I also noted that once playback was running correctly, the lag between audio and picture was terrible... so looks like I really do need the monogram aac decoder.

I have some questions:

1) What is the difference between the "AAC Decoder" and "HE-AAC Decoder" settings? It seems the wiki screenshots are old and it doesn't mention this...

2) When I go back to 'system default', other than the lag between audio and picture, I do actually have audio (whereas before I installed the monogram decoder I had no audio). So what is the 'system default' using? Pressing the ellipsis '...' button does nothing so how can I tell...
I did install HDpack1.7 (iirc for a video decoder), so is the 'system default' reverting to something out of this? How can I tell because clicking '...' does nothing...

Regardless, this failing to resume correctly - would logs help?

[sub]

1) What is the difference between the "AAC Decoder" and "HE-AAC Decoder" settings? It seems the wiki screenshots are old and it doesn't mention this...

Our DVB-T system uses HE-AAC, so this is the only one you need to worry about.

2) When I go back to 'system default', other than the lag between audio and picture, I do actually have audio (whereas before I installed the monogram decoder I had no audio). So what is the 'system default' using? Pressing the ellipsis '...' button does nothing so how can I tell...
I did install HDpack1.7 (iirc for a video decoder), so is the 'system default' reverting to something out of this? How can I tell because clicking '...' does nothing...

The "..." doesnt nothing with "system default" since it has no idea what decoder the system will choose. You'd have to look in the filter list from pvrx2.exe-native.log to check what decoder is being used.

[engnz]

What's your setting in the config for <UseBuiltInTSReader>?

Try opposite setting (true or false) to see if it makes a difference.

I found that works better for me set to false although I get an annoying one backward skip when I do a forward skip.

[time_lord]

Ah, I see what HE-AAC is... wikipedia to the rescue ;-)

What's your setting in the config for <UseBuiltInTSReader>?

Try opposite setting (true or false) to see if it makes a difference.

I found that works better for me set to false although I get an annoying one backward skip when I do a forward skip.

Thanks, will try out later

[time_lord]

Yes there is a difference. By default the skip keys (Ctrl-Right/Ctrl-Left) will jump forward 60 seconds, or back 30 seconds, or whatever you've changed them to in the config app. The FF/RW keys (Ctrl-F/Ctrl-D) will jump forward/back 10 seconds.
Maybe. I dont know.

Couple of days ago I was using Ctrl+Right to just thru a dvb-t recording (i.e not one of the dodgy analog ones where the FF/RW is not always the same. But it was jumping forward 2min 50 sec or thereabouts (but the ff time is set to 30 seconds)... and the Ctrl-Left was also jumping forwards! Real pain.
I FF'd to the end to see if the time elapsed matched the total time indicated (on the top-of-screen graphic), but found when I FF'd when I should have been at the end, it jumped back 2 seconds from the end and played those last 2 seconds. I could repeat this over & over and it kept replaying the last 2 seconds. Just when I was wondering why it would jump backwards, I suddenly got a BSOD, faulted in watchdog.sys.
Any ideas what could have caused this?