Recording not stopping, Failed Recording, Patch Causing Erroneous Recording Times...

[Pilot]

After encountering a ton-o-problems in my GBPVR system, I decided to simply cut my losses and reinstall. I'm running v0.97.13 with one PVR150 and one PVR500 with a 160GB hard drive (80GB available and defragged less than 24 hours ago) on a P4/1.8ghz. I'm running no plugins other than the default and the default Blue skin.

Of course, everything was running blazingly fast because of the fresh install, but the first recording on this new system would not stop recording. It was the Barefoot Contessa (cooking show) at 5:00pm-5:30pm EST with a 5 minute buffer set at either end. It started recording at 4:55pm, but although the GBPVR tray icon (and status screen) said that it was still recording this show at 9:00pm, the actual video file is only 22 minutes long so it's missing almost 20 minutes of the recording. Also, the show scheduled at 9:00pm-10:00pm ("Bones") did not record at all and is reported as failed. Another show at 10:00pm-11:00pm started recording just fine, but that's only after I restarted the recording service because that's the only way I could get the 5:00pm show to stop recording.

To get the failed recording to delete, I had to apply the appropriate patch. Now my recorded shows show weird start and stop times that do not correspond to the 5 minute buffer at either end.

The last time I went through the above process, I ended up with quite a few of my recordings playing at fast forward speed for the last five minutes of the show. The verdict is still out on whether or not that will start happening now, as I haven't had a successful recording yet.

My previous GBPVR versions have all been extremely reliable, even after numerous upgrades/updates being applied. This is a very fresh, plain vanilla install, and I am a bit surprised that the same thing that happened to my old install is now starting to happen to this brand new install.

I've attached all the logs.

Thanks for any insight anyone can provide.

[sub]

I cant see any definitive reason in the logs, but I'm guessing it is something to do with your EPG being updated during that recording, which is reloading the recording list and maybe forgetting that the recording is in progress. That doesnt really explain why it finished after 22 minutes though.

[Pilot]

Thanks, Sub. That's true -- I do have the EPG update set for 5:00pm. I forgot about that, and it is a bit suspect. Another thing that is suspect is the power options/standby of the computer. Before recording the 5:00pm-5:30pm show, the PC was in standby, and therefore woke up to start the recording. When I first check on the recording it was about 9:00pm and although the computer was still on the monitor (video card?) still hadn't come out of suspend yet. So maybe the power saving options did something weird, causing the PC to not completely wake up or to go back to standby early (and cut off the recording at 22 minutes). I've since changed the power settings profile to Always On.

Thankfully, the 10:00pm show I recorded didn't end up with fast-forwarded last five minutes, so that's a very good thing!

All of my pending recordings used to have normal times, like 5:00pm-5:30pm, but now they all have something like 4:58pm-5:29pm. When I highlight this same show in the TV Guide, the times are normal. Now here's a really weird thing -- if I just delete one of these pending recordings, then go to the TV Guide, and reconfigure it to record this same show, all of the other pending recordings with the weird start/stop times listed are corrected to the normal start/stop times. Weird....

[sub]

All of my pending recordings used to have normal times, like 5:00pm-5:30pm, but now they all have something like 4:58pm-5:29pm. When I highlight this same show in the TV Guide, the times are normal. Now here's a really weird thing -- if I just delete one of these pending recordings, then go to the TV Guide, and reconfigure it to record this same show, all of the other pending recordings with the weird start/stop times listed are corrected to the normal start/stop times. Weird....

If you email your gbpvr.mdb file to me at support@devnz.com, and include an indication of a show / recording that exhibits this problem, then I'll take a look. There have been a couple of people report this over the last year or so, but I've never seen it myself. Reven was one of the users who reported this problem in the past.

[frumbert]

All of my pending recordings used to have normal times, like 5:00pm-5:30pm, but now they all have something like 4:58pm-5:29pm. When I highlight this same show in the TV Guide, the times are normal. Now here's a really weird thing -- if I just delete one of these pending recordings, then go to the TV Guide, and reconfigure it to record this same show, all of the other pending recordings with the weird start/stop times listed are corrected to the normal start/stop times. Weird....

huh, I've noticed exactly the same thing on mine. But I've had so many other little wierd errors that I've been ignoring this one. Glad it's not just me!

[sub]

Same offer - if you email your gbpvr.mdb file to me at support@devnz.com, and include an indication of a show / recording that exhibits this problem, then I'll take a look

[sub]

What database are you guys using Access or SQLite?

[Pilot]

If you email your gbpvr.mdb file to me at support@devnz.com, and include an indication of a show / recording that exhibits this problem, then I'll take a look. There have been a couple of people report this over the last year or so, but I've never seen it myself. Reven was one of the users who reported this problem in the past.

I'll do that and remind you with a link to this thread if it happens again in the future. For now, all the times are back to normal after deleting the one reoccurring recording and then re-entering it. Just doing that to one of the recordings corrected the times for all of the recordings.

What database are you guys using Access or SQLite?

This happened in my old install of GBPVR which was using SQLite, as well as this new fresh install which is using Access. I never tried the "fix" noted above (deleting one pending/reoccuring recording and then re-entering it) on the old GBPVR system, so I don't know if that would've fixed it for that install or not. I forgot to run the ChangeDatabase.exe when I did the new install. Anyway, it appears that the "problem" (if it is one) will occur using either SQLite or Access if my experience is any indication.

Which is better to use? I'm remembering that you were going to stop supporting Access soon, right? I guess I should probably switch to SQLite before the Access database gets any bigger.

As always, Sub, thanks for looking into this.