One recording scheduled twice

[Nomad101]

I found the duplicates reduced to almost zero by appending /d7 to my xmltvgui grab scheduled task to limit the EPG to 7 days. They seem to do the schedule changes a week in advance and doing the above seems to just grab the latest schedule time.

Thanks for the tip. I didn't think of reducing the number of days to avoid schedule changes!

Cheers
Tony

[gEd]

The way I appear to have fixed my overlapping recordings (when the show is rescheduled) is to run these commands after downloading my epg.
It is line 2 that fixes the problem. It deletes the pending shows which are then rescheduled when line 3 runs (I think)

"C:\Program Files\devnz\gbpvr\pvrx2.exe" -EmptyEPGOnly
"C:\Program Files\devnz\gbpvr\pvrx2.exe" -deletependingrecurring
"C:\Program Files\devnz\gbpvr\pvrx2.exe" -OnlyUpdateEPG

[Nomad101]

The way I appear to have fixed my overlapping recordings (when the show is rescheduled) is to run these commands after downloading my epg.
It is line 2 that fixes the problem. It deletes the pending shows which are then rescheduled when line 3 runs (I think)

"C:\Program Files\devnz\gbpvr\pvrx2.exe" -EmptyEPGOnly
"C:\Program Files\devnz\gbpvr\pvrx2.exe" -deletependingrecurring
"C:\Program Files\devnz\gbpvr\pvrx2.exe" -OnlyUpdateEPG

Hi gEd

Yes, that's exactly what I was running until a week or two ago. In fact I think you might have got that middle command from my post in this thread:
http://forums.nextpvr.com/showthread.php?t=29357

Have you had any problems with failed recordings (which haven't actually failed) or recordings being saved with the wrong name and details? I was having those problems so reverted back to the standard EPG update in config to see if it was related. After the change all the failed or incorrectly named recordings stopped. I haven't tried going back to the scripted update yet to see if they return but might do that.

Cheers
Tony

[HtV]

In this thread: http://forums.nextpvr.com/showthread.php?t=32684
Sub wrote:

One-off recordings, or the first recording in a season recording are never removed from the database, so wont reflect later changes made to these programmes in the EPG source.

Hans

[Nomad101]

Yeah, I've seen Sub mention that before but my season recordings were scheduled months ago so the current ones which are being duplicated are not "master" recordings.

Cheers
Tony

[gEd]

Hi gEd

Yes, that's exactly what I was running until a week or two ago. In fact I think you might have got that middle command from my post in this thread:
http://forums.nextpvr.com/showthread.php?t=29357

oops, sorry I didn;t pay attention to who was posting!

Have you had any problems with failed recordings.

now that you come to mention it, I was just wondering why so many of my Simpsons recordings fail at 6pm every evening.....

or recordings being saved with the wrong name and details?

yep but I need to collect some evidence.

[Nomad101]

now that you come to mention it, I was just wondering why so many of my Simpsons recordings fail at 6pm every evening.....

Next time a Simpsons recording fails have a look in your recordings folder and you might find the file is actually there and has recorded properly other than the fact that it's missing a few minutes at the beginning or end.

[gEd]

I had one fail yesterday
the file is there and the show is the correct length.
comskip ran on the file ok but the file was not renamed by addepisode, probably because gbpvr did not update the recording_schedule table with the filename once the recording had finished but instead marked it as failed.

The log shows the correct message at the end of the recording
VERBOSE BDARecorder::StopRecording() finished, followed by messages
2008-01-15 18:34:00.343 VERBOSE BDARecorder::StopRecording() finished
2008-01-15 18:34:01.687 VERBOSE Asking Windows to be awake for recording (oid: 7872) at 2008-1-15 20:56:30 (UTC 2008-1-15 20:56:30)
2008-01-15 18:34:01.687 VERBOSE Asking Windows to be awake for recording (oid: 7888) at 2008-1-15 21:55:30 (UTC 2008-1-15 21:55:30)

i need another failed show to try and spot a pattern. The only things so far are that it is the first recording of the day and the "stay awake" messages right after the recording finishes.

[HtV]

This could ofcourse very well be a addepisode flaw, starting to early or the gbpvr.db3 being locked for some reason or whatever.
Are the other folks with problems also using a postrecording batch or something like that?

Hans

[gEd]

I did originally wonder if it was addepisode but I can't see it.

my postprocessing.bat:
run comskip
sleep 5
run addepisode

The entry in the recording_schedule table should show the original filename rather than the show name but instead it is marked it as failed.

I think addepisode then queried the db and decided not to rename the as it couldn't get a match to the original filename.