Video freezing

[Dale Dewing]

In another thread you asked me to post a new thread with my problems.  Here is a video freeze.  I skipped back and forth to get it.  Of course, when I was trying to get it it took a few tries.  Hopefully attached is a screen shot and logs. I have tried several decoders.  I am using the LAV decoder for MPEG2 now.

[sub]

2022-03-26 11:24:23.919 [DEBUG][1] Graph filter list:
2022-03-26 11:24:23.919 [DEBUG][1] - NPVR CC Dump
2022-03-26 11:24:23.919 [DEBUG][1] - EVR Renderer
2022-03-26 11:24:23.919 [DEBUG][1] - AC3 Audio Renderer
2022-03-26 11:24:23.919 [DEBUG][1] - Nablet MPEG-2 Decoder
2022-03-26 11:24:23.919 [DEBUG][1] - Line 21 Decoder
2022-03-26 11:24:23.919 [DEBUG][1] - ffdshow Audio Decoder
2022-03-26 11:24:23.919 [DEBUG][1] - NPVR CC Extractor
2022-03-26 11:24:23.919 [DEBUG][1] - NPVR TS Reader 5

This is using a couple of particularly uncommon decoders. (Nablet and ffdshow)

I'd suggest installing the LAV decoders from https://github.com/Nevcairiel/LAVFilters...taller.exe, and setting all your decoders to the LAV decoders. These are the most widely used decoders here. These decoders are based on the popular ffmpeg project, and they perform well. (ffdshow also based on this, but is very old and way out of date now)

2022-03-26 11:24:23.372 [DEBUG][1] adding audio renderer: SPDIF-Out (Sound Blaster Z)

This could also be the problem. In general it's best to set the audio renderer to 'Default', and just set windows to use your SPDIF as the default audio device.

The audio renderer is chosen as the clock source for playback, and some of these audio renderers (other than 'Default DirectSound Renderer') where known to produce problematic clock timestamps. Microsoft's Default DirectSound Renderer does a good job providing a clock source that works well with Directshow. This was also a common cause of freezing in v4 etc in the past too.

I'm sure the changes I've suggested above will fix your issues with freezing.

[BrettB]

2022-03-26 11:24:23.919 [DEBUG][1] Graph filter list:
2022-03-26 11:24:23.919 [DEBUG][1] - NPVR CC Dump
2022-03-26 11:24:23.919 [DEBUG][1] - EVR Renderer
2022-03-26 11:24:23.919 [DEBUG][1] - AC3 Audio Renderer
2022-03-26 11:24:23.919 [DEBUG][1] - Nablet MPEG-2 Decoder
2022-03-26 11:24:23.919 [DEBUG][1] - Line 21 Decoder
2022-03-26 11:24:23.919 [DEBUG][1] - ffdshow Audio Decoder
2022-03-26 11:24:23.919 [DEBUG][1] - NPVR CC Extractor
2022-03-26 11:24:23.919 [DEBUG][1] - NPVR TS Reader 5

This is using a couple of particularly uncommon decoders. (Nablet and ffdshow)

I'd suggest installing the LAV decoders from https://github.com/Nevcairiel/LAVFilters...taller.exe, and setting all your decoders to the LAV decoders. These are the most widely used decoders here. These decoders are based on the popular ffmpeg project, and they perform well. (ffdshow also based on this, but is very old and way out of date now)

Also, a friendly reminder that you must install the 32-bit LAV filters--even on a 64-bit Windows platform because NextPVR.exe is a 32-bit application!

[antantnz]

Hi ... jumping in on this thread also as I have unfortunately been having similar issues to Dale which we've kind of just been living with - normally nothing that can't be resolved by exiting the recording and reopening it ... but, still gets a bit frustrating.

Example in logs is of playing a recording tonight, of an episode of the Simpsons recorded last night. 

Started playing 19:31:25.274 and then paused while waiting for kids to get ready. Attempting to skip to find start of episode, so skipped forward 60, skipped forward 60, skipped forward 60, too far, skipped back 30, skipped back 30, with intent to just let it play instead until I get to the start. Hit play (19:32:43.229), nothing happens on screen (about 5 - 10 secs wait), so then exit, and reopen file. Not uncommon behaviour, so tend not to do as much skipping around as we once did. 

Any advice from the logs?

One recurring theme in my mind is to start completely fresh again (clean Windows install, clean nextpvr install). 

Logs should be attached (hopefully).

[antantnz]

Logs ...

[sub]

No logs attached.

They need to be zipped to attach. If they're larger than 2MB zipped, you might need to put them somewhere like onedrive / googledrive and let me know the download link.

EDIT: scratch that...they just arrived.

[sub]

Hi ... jumping in on this thread also as I have unfortunately been having similar issues to Dale which we've kind of just been living with - normally nothing that can't be resolved by exiting the recording and reopening it ... but, still gets a bit frustrating.

Example in logs is of playing a recording tonight, of an episode of the Simpsons recorded last night. 

Started playing 19:31:25.274 and then paused while waiting for kids to get ready. Attempting to skip to find start of episode, so skipped forward 60, skipped forward 60, skipped forward 60, too far, skipped back 30, skipped back 30, with intent to just let it play instead until I get to the start. Hit play (19:32:43.229), nothing happens on screen (about 5 - 10 secs wait), so then exit, and reopen file. Not uncommon behaviour, so tend not to do as much skipping around as we once did. 

Any advice from the logs?

One recurring theme in my mind is to start completely fresh again (clean Windows install, clean nextpvr install). 

Logs should be attached (hopefully).

Do you see the issue with recordings from all channels, or just certain channels? If not certain, look for a pattern (rather than guessing).

If you want to supply the Simpsons recording, and I'll take a look at it here. If you focus on playing that specific file, are you able to reproduce problems with certain actions?

[antantnz]

Will drop you a link to the Simpsons recording.

What I have noticed in doing some more testing is that currently it seems it's only an issue if I pause and then skip ... if the video is playing when I skip, it seems to be ok.

Seems to be consistent across a variety of recordings that I tested on just now (tried recordings from One, Three, Duke, Eden, Rush) .

So if, while playing, I go -> skip forward, skip forward, skip forward, skip back, skip back -> it continues playing.
If however, I go -> *pause*, skip forward, skip forward, skip forward, skip back, skip back, *un-pause* -> it will fail to un-pause cleanly (picture freezes, some audio starts, then stops, picture may move, but never seems to recover).

The realisation that I might just need to make sure I un-pause first, before skipping, might actually be enough to resolve the issue from my point of view. But will send file just in case it's any use.