System.OverflowException: Overflow error.

[dennit]

I've had trouble for a while in stopping recordings. I've just switched to 1.3.7 from 1.2.13. The logs now show the error above, which appears after it refuses to stop recording.

Code:

2008-12-13 20:00:48.625    VERBOSE    [1]    Checking if resume prompt needs to be shown
2008-12-13 20:00:48.625    VERBOSE    [1]    PlaybackPositionManager.getLastPlaybackPosition(H:\GBPVR\Recordings\Haunted History\Haunted History_20081213_20002100.mpg)
2008-12-13 20:00:48.718    VERBOSE    [1]    Received event code: 14
2008-12-13 20:00:48.718    VERBOSE    [1]    Received event code: 0
2008-12-13 20:00:48.718    VERBOSE    [1]    HideMouse ref=-1
2008-12-13 20:00:49.890    VERBOSE    [1]    ShowMouse ref=0
2008-12-13 20:00:50.031    ERROR    [1]    Unexpected error: System.OverflowException: Overflow error.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.FillPath(Brush brush, GraphicsPath path)
   at GBPVRX2.Players.x977e0aa739bd29d7.x2935cc5f251a17b0()
   at GBPVRX2.Players.x977e0aa739bd29d7.GetRenderList()
   at GBPVRX2.x0061b801bdf12d35.xdb012c437aec4a40(Boolean xd23bf32f3b17e3be)
   at GBPVRX2.xb979ad394703258e.xfb409e85bd292293(String[] xf18a926310372520)
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbsbbtn.png
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbrwbtn.png
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbpausebtn.png
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbffbtn.png
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbsfbtn.png
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbsubtv.png
2008-12-13 20:00:50.031    VERBOSE    [1]    Skinhelper loading image from file: C:\graf\GBPVR\skin2\Blue\OSD\pbclosebtn.png
2008-12-13 20:00:50.812    ERROR    [1]    Unexpected error: System.OverflowException: Overflow error.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.FillPath(Brush brush, GraphicsPath path)
   at GBPVRX2.Players.x977e0aa739bd29d7.x2935cc5f251a17b0()
   at GBPVRX2.Players.x977e0aa739bd29d7.GetRenderList()
   at GBPVRX2.x0061b801bdf12d35.xdb012c437aec4a40(Boolean xd23bf32f3b17e3be)
   at GBPVRX2.xb979ad394703258e.xfb409e85bd292293(String[] xf18a926310372520)
2008-12-13 20:00:57.406    VERBOSE    [1]    HideMouse ref=-1
2008-12-13 20:01:47.703    VERBOSE    [1]    DisplayStillInUse
2008-12-13 20:01:58.000    VERBOSE    [1]    PlaybackPositionManager.storeLastPlaybackPosition(H:\GBPVR\Recordings\Haunted History\Haunted History_20081213_20002100.mpg, 69)
2008-12-13 20:01:58.093    VERBOSE    [1]    EnableScreenSaver()
2008-12-13 20:01:58.093    VERBOSE    [1]    getValue cached value: /settings/ScreenSaverEnabled : true

[sub]

Post the logs and I'll take a look.

[dennit]

Post the logs and I'll take a look.

Logs1 include the logs with that error. In an attempt to get a clean set of logs, I stopped the recording service, renamed the logs, then restarted and let it build fresh logs as I tried to stop the same recording. Logs2 are the fresh set of logs. It still failed to stop, but I don't see that error in there this time. I did see it in the set of logs prior to the logs1 attached.

[sub]

Other than seeing the error message in the logs, are you seeing any problem in the app?

[dennit]

Other than seeing the error message in the logs, are you seeing any problem in the app?

I really appreciate your help.

I'm working through a variety of problems upgrading to 1.3.7. You've already helped me solve the two big ones today - the ignore error settings were wrong and I needed AC3Filter to solve the half-speed sound issue.

The reason I wanted to upgrade was to get the multirecord capability, so I've been testing that, which requires turning on and off recordings. This problem with stopping recordings has made testing difficult. I've been reduced to manually entering the db with SQL Browser and deleting the last record in the recording_schedule table.

Here's what I'm seeing: I can watch all channels on all 3 sources - QAM, analog and DVB-S. (Live) I can record all channels/sources in mpg and dvr-ms, but not TS. I can record and multirecord in TS on QAM. I can't record or multirecord TS on DVB-S. I get 0 byte size TS files for the satellites - even non-encrypted channels.

I'm using MDAPI/emunation and have read that it is not going to work with multirecord, but I want multirecord for QAM, so if I can get TS working w/o multirecord for DVB-S I'll be happy.

When I try to stop a recording, it asks me if I'm sure, I say yes, then it goes off to lala for a moment, then returns control to me. It seems to work fine thereafter, but the program in guide stays red, and the recording service reports in status via GBPVRTray that it is still recording.

It doesn't matter if I try to stop the recording from the guide or the Recording Pending screen. I'm running parallel processing comskip and have considered perhaps this is doing something? I also have 500 channels, with perhaps 600 sources/channels (same channel on multiple sources), so I know I'm potentially stressing things.

I hope this info is useful (but I have my doubts ;-)
Thanks for great program. The wife thanks you, too. Have a great Christmas! (I hope you aren't planning on flying around the world for this holiday too!)

I grabbed a third set of logs just after asking again for it to stop recording, just in case - let me know if they are of interest.

[sub]

Here's what I'm seeing: I can watch all channels on all 3 sources - QAM, analog and DVB-S. (Live) I can record all channels/sources in mpg and dvr-ms, but not TS. I can record and multirecord in TS on QAM. I can't record or multirecord TS on DVB-S. I get 0 byte size TS files for the satellites - even non-encrypted channels.

I'm using MDAPI/emunation and have read that it is not going to work with multirecord, but I want multirecord for QAM, so if I can get TS working w/o multirecord for DVB-S I'll be happy.

Unfortunately its either on or off. You cant have it for just QAM not DVB-S.

When I try to stop a recording, it asks me if I'm sure, I say yes, then it goes off to lala for a moment, then returns control to me. It seems to work fine thereafter, but the program in guide stays red, and the recording service reports in status via GBPVRTray that it is still recording.

I'm sure that log message you quoted is nothing to do with this. Its a problem with trying to display the time line graphic in the OSD. Its having problems working out how big the bars should be.

[sub]

If you can produce a set of logs, where you try to cancel a recording from the recording screen, and let me know exactly what time you tried to cancel it, then I'll take a look.

[dennit]

Unfortunately its either on or off. You cant have it for just QAM not DVB-S.

Thanks, I'm aware of this. The system is running great now, under 1.3.7 using the Cyberlink BDA mux - mpg. I'll keep an eye on the issue of refusal to stop recording and get an exact time with matching logs. I see you're busy with multirecord and 0 byte files on another thread, so I'll just hang back on that issue.

I'm sure that log message you quoted is nothing to do with this. Its a problem with trying to display the time line graphic in the OSD. Its having problems working out how big the bars should be.

So you were asking if I was seeing some problem in the display time line graphic, and the answer to that is - "no."

[dennit]

If you can produce a set of logs, where you try to cancel a recording from the recording screen, and let me know exactly what time you tried to cancel it, then I'll take a look.

Here are 4 attempts to cancel a 3 hour recording with one hour padding, all attempts being made from the recording screen, all made in the last hour of padding, and all fail. I see "database locked" for some but not all. The first attempt locked up the system for 30 seconds. The last 3 gave me back control almost immediately. The moment I had control, I grabbed copies of logs and rared them up. If the logs had not changed after logs.rar I did not include them.

The attempts were made at:

Code:

2008-12-14 19:32:00.937    VERBOSE    [5]    Received request to cancel recording: 1106
2008-12-14 19:35:20.937    VERBOSE    [5]    Received request to cancel recording: 1106
2008-12-14 19:48:36.187    VERBOSE    [5]    Received request to cancel recording: 1106
2008-12-14 19:52:40.609    VERBOSE    [5]    Received request to cancel recording: 1106

Perhaps these will give some clues.