LiveTV Freezes Are Back on Clients

[sub]

For the first time since I can remember my hdpvr did not freeze on live tv after a good run 4+ hours, so very impressed

Ok, good. Have you tried running it up again today?

[mvallevand]

It's about an hour in right now. I should add I was/am running these tests on wifi because of some renovations and @ 720p no issues at all. During that hour I walked with the laptop to show my wife a bathroom vanity picture totally forgetting about the test and nextpvr didn't seem to miss a beat.

Martin

[Graham]

... a bathroom vanity picture ...

Someone posing in front of a mirror perhaps ...

[mvallevand]

LOL

Martin

[mvallevand]

I thought you it licked but here's a freeze, stopping the recording service wasn't enough I had to kill the client task and restart the backend to get the tuner back

Code:

System.ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value
   at System.DateTime.Add(Double value, Int32 scale)
   at NextPVR.Players.BasePlayer.UpdateTimeline()
   at NextPVR.Players.BasePlayer.RefeshOSD()
   at NextPVR.Players.LiveTvPlayer.RefeshOSD()
   at NextPVR.ControllerForm.timer1_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Martin

[sub]

I only added logging, so it shouldn't really have fixed anything.

[mvallevand]

Same error on another try do you want the logs? This time I just killed NextPVR and the graph cleaned up ok so no reboot.

Martin

[sub]

A couple of things:

1) Was that from a live tv session? The nrecord.logs don't look like it. It looks like it was just playing a large file (in progress recording?). You should be getting messages like this in your log, with the xml and references to 'base offset' etc. Your logs don't have these. Typically you'd have messages like:

2013-02-10 18:57:51.021 [DEBUG][15] CLIENT-READ: 169200 bytes from offset 2302473600 (file length: 2304106200)
2013-02-10 18:57:51.022 [DEBUG][15] RollingFile.Seek(2302473600)
2013-02-10 18:57:51.022 [DEBUG][15] RollingFile base offset is now: 1216249856
2013-02-10 18:57:51.022 [DEBUG][15] <Files>
<Length>2304106200</Length>
<File offset="1216249856">C:\temp\live-MTIMEHD-8013-2.ts</File>
<File offset="0">C:\temp\live-MTIMEHD-8013.ts</File>
<Duration>2809406</Duration>
<Complete>0</Complete>
</Files>

2013-02-10 18:57:51.022 [DEBUG][15] about to read 169200 from location 1086223744 (current length = 1087078400)
2013-02-10 18:57:51.023 [DEBUG][15] GetDurationMS() live: 2809406
2013-02-10 18:57:51.023 [DEBUG][15] In-progress duration is now: 2809406
2013-02-10 18:57:51.023 [DEBUG][15] READ: data read, about to send
2013-02-10 18:57:51.023 [DEBUG][15] READabout to send
2013-02-10 18:57:51.223 [DEBUG][15] READ: complete

If you're positive it was from a live tv session, how big is the current buffer file?

2) For this other client side error you get, is this something that happens after the freeze (like clicking the screen when it's frozen), or does it cause the freeze (like was working fine, then client froze because of exception then stopped asking for more data). Might be hard to tell.

System.ArgumentOutOfRangeException: Value to add was out of range.
Parameter name: value
at System.DateTime.Add(Double value, Int32 scale)

[mvallevand]

I am positive it is a live tv file your xml log should show the pieces. I use a larger buffer so that I can save my capture file.

For the other question, the trace popup comes up even when nextpvr is hidden so I can't say.

Martin

[mvallevand]

Slip seconds is 4608

Martin