2.4.3 Unhandled Exception when Skipping on Client

[mvallevand]

You can use streams http://technet.microsoft.com/en-us/sysin...s/bb897440 to delete the Timing.Info You can back it up first with

more < filename:Timing.Info > Timing

and restore it with

echo Timing > filename:Timing

Martin

[sub]

For some reason its not getting the timing info from the server (otherwise it'd have a "Got Timing.Info from server" in npvr.log), so it's falling back to looking at the PCR timestamps to determine the duration. When it does this, it's managing to find the PCR at the start of the file, but not managing to find the one at the end.

[sub]

Can you see if this patch on the client helps?

[smajor]

Assuming I got the syntax correct, it appears to have the same duration.

streams -d filename:Timing.Info

It didn't throw an error at that.

[smajor]

Can you see if this patch on the client helps?

I'm afraid it didn't. Same error, logs attached if needed.

[sub]

Should npvr.log (ie from last run of nextpvr.exe) have shown this attempted playback? I cant see it.

[smajor]

Try these, I may have accidentally attached the wrong ones with all the logging lately. I captured two sets of logs, along with record.txt for good measure.

Each should have a problem recording as the last played. The second one was recorded back in December.

[sub]

It now looks like it got the duration from the server. Was it still showing zero during playback?

2012-03-27 21:11:25.070 [DEBUG][1] Got Timing.Info from server
2012-03-27 21:11:25.084 [DEBUG][1] Server's Timing.info reports duration 3772993ms

[smajor]

It now looks like it got the duration from the server. Was it still showing zero during playback?

Yes, it is still showing zero duration during playback.

[jcjefferies]

I have recently had very occasional “Divide by Zero” exception errors when “Skipping” on my client. Last night I had the error when I tried to skip a recording even after restarting NextPVR or a client reboot. However I was able to skip other recordings but today I still get the same exception if I skip that recording. Looking at the database I see the probable cause of the error with duration = 0 under Playback Position. I have two more recent recordings with same zero duration and when played on the client the “Position” increments but the “Duration” is always Zero. However these all play ok on the server giving the correct duration on the time bar. I tried running Write Time by mvallevand on one of the recordings but that does not help. I briefly looked at the last 20 recordings and all except the one with the problem last night start playing with the correct “Duration” info on the time bar.

I reported a similar problem several weeks ago where the client would occasionally lose the timing info part way through certain recording but the server kept the timing info. I saw that at the point in the recording the client lost all timing the server saw the “Position” time jump several seconds. However that problem may be different as I think it caused a negative position number.