npvr 1.5.28 crashes on live tv

[elbryyan]

When I select Live TV, I get this error message.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Native.PlaybackNative.PlayLiveStream(IntPtr hwndIntPtr, String filename, Int32 serviceType, String& message)
at NextPVR.Players.PlaybackProxyFactory.StartLiveStreamPlaybackProxy(IntPtr window, String target, Int32 serviceType, String& reason)
at NextPVR.Players.LiveTvPlayer.StartLiveTV(Channel channel, String& reason)
at NextPVR.Players.LiveTvPlayer.StartLiveTV(String& reason)
at NextPVR.ControllerForm.PlayLiveTV()
at NextPVR.Menu.AeonLike.OnKeyDown(KeyEventArgs e)
at NextPVR.ControllerForm.OnKeyDown(Object sender, KeyEventArgs e)
at System.Windows.Forms.Control.OnKeyDown(KeyEventArgs e)
at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
at System.Windows.Forms.Control.WmKeyChar(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at NextPVR.ControllerForm.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[sub]

Post the logs and I'll take a look.

[TheShadow]

Don't want to hijack this thread but after a few seconds of play I get the message "the tuner used for live tv is no longer available". I am not sure what I did as it seemed to be fine for most of the morningafter the install of 1.5.28.

[elbryyan]

Sorry, Sub. It's been a busy weekend for me as I got back from traveling all week and was trying to get my HTPC updated to WIN 7 and using the new NPVR. Right now I reverted back to my xp hard drive and am back to GBPVR 1.47 until I can get some more time together to troubleshoot. I will get the logs to you as soon as I can as the drive is still hooked up and I can probably browse the the log location as it has probably not been updated since the error occured because of the switch. It may not be until this weekend unless I can get to it tonight. Wife is going out for girls night but left a honey do list as well.

Edit: forgot to say thanks for the great product and all your hard work.

[johnsonx42]

@TheShadow: nice hijack... I'll remember to run away if you ever say you don't want to shoot me and then pull out a gun

Your problem is discussed here: http://forums.gbpvr.com//showthread.php?...lable-quot

No solution yet, but the work-around is to restart the recording service. For me the problem seems to be exclusively caused by changing channels while in Live TV, so we just don't do that any more - we just exit back to the guide each time and select a new channel.

[Reddwarf]

@TheShadow: nice hijack... I'll remember to run away if you ever say you don't want to shoot me and then pull out a gun

Your problem is discussed here: http://forums.gbpvr.com//showthread.php?...lable-quot

No solution yet, but the work-around is to restart the recording service. For me the problem seems to be exclusively caused by changing channels while in Live TV, so we just don't do that any more - we just exit back to the guide each time and select a new channel.

It's strange thou, I can change channel all day and never experience that problem, and we'r running the same SW, right?

[tjb]

I get the same type error the 2nd time that I run LiveTV, no channel change is required.

[johnsonx42]

It's strange thou, I can change channel all day and never experience that problem, and we'r running the same SW, right?

Yeah, it doesn't happen to sub either. What can I say? Software is crazy stuff. It seems that NRECORD can lose track of which stream id's or handles are which; I've had various cases where NRECORD will think a graph is no longer in use and tear it down, which results in killing an active recording or LiveTV; of course NRECORD doesn't think it did that, and so later when it tries to end the recording for real then it has no graph to end. A similar logical failure seems to sometimes result in NPVR trying to end a recording, but not finding the graph to end because it has again lost track of which stream id is which; so NRECORD thinks it's ended the recording and shows it as "Ready", meanwhile the orphaned graph is still running, still recording the broadcast stream to the file until the hard drive fills up or the system is restarted (restarting the recording service does nothing, the graph is somehow 'detached' from the recording service). I'm sure when sub has the time and can go over his code for this area he'll find the error.

[johnsonx42]

@tjb: I've been observing your threads with some interest to see if it's related to this problem. So far it has looked to me like a different sort of issue, but it may well be just a different manifestation of the same underlying problem.

[johnsonx42]

@elbryyan: sorry for the hijaak... TheShadow started it!!! Also, I fixed your thread title to 1.5.28, just in case we ever do have a 1.58 or 1.5.8. (edit: on further thought I guess 1.58 is very unlikely for the way sub numbers releases, and 1.5.8 is already past.. I suppose 1.5.80 is still possible, but I suspect we'll get to 1.6.x or 2.x before then... either way, I've gone and done it so there it is).