Reoccuring Recordings not scheduling

[roy]

Sorry to be a pest, but...
I have a third machine with v99.5 installed. I replaced gbpvr.db3 with empty.db3. Created a capture source with zap2it epg and did epg update.

Created a daily recording of "Dragon Tales" at 2pm on channel 2. It scheduled as pending for 3/8-3/13, but not for 3/14 or 3/15.

I see in log gbpvr.exe-1.log (attached) that it skipped these episodes:

Code:

3/8/2007 12:34:29 PM.593    VERBOSE    [1]    Found potential match at 3/14/2007 2:00:00 PM  (EP3239630108)
3/8/2007 12:34:29 PM.593    VERBOSE    [1]     - skipping episode because a schedule recording already matches this episode: EP3239630108

"Don't record duplicates (zap2it)" is not checked in config.

Why does it skip these episodes? Is it an error in the listings?

[River_Styx]

Hi Sub
Very strange. I always get my XMLTV file fresh in the morning at 07:00 (local time). After that is done I empty the TV Guide with the command "GBPVR.exe -OnlyEmptyEpg" and the load the fresh XMLTV file with the command "GBPVR.exe -OnlyUpdateEPG". All this is done in a command file.

After that was done I checked the pending recordings. None was scheduled although 5 should be there. Via the config program I scheduled the "Complete EPG reload" at 14:00. After this the 5 scheduled programs showed up at the Pending recordings!!!!

Is there a different command used in the Config file than you can use from the command line?

[HtV]

- There is a lot of empty <programme></programme> tags in your xmltv which leads to a lot of errors. I think these are the source of your errors.

Styx are you using some epg-filter program? Because I use that [Ton's epg-filter) and have had also a problems with the empty <programme> </programme> tags. In fact in my case it's a "lonely" <programme> tag.

- It is the first xmltv file I've seen that specifies a <icon> tag for the rating system. This confuses GB-PVR and it tries to download it as a channel icon. It results in an error in the logs, but doesnt stop it from processing the rest of the file. I've modified it for the next build so it knows to ignore this icon tag.

I guess you can turn of this behaviour by deselecting "kijkwijzer" in the tvgids_to_xml.ini file.

Dutch epg listings are a nightmare I think. At the moment Amontillado's grabber works pretty well, but a few weeks ago I had to switch over to xmltv without descriptions or whatever extra's. There were always quite some mistakes in the tvgids.nl website and therefore also in the epg.
As I said at the moment they seem to do pretty well.

cya Hans

[sub]

Roy, I've been looking at that set of files you emailed through.

I went in to take a good look at the scheduler messages relating to the scheduling of Arthur, but found a whole lot of unfamiliar log messages starting "TVListings: " interspersed among the scheduling for this show, and the sequence of events were not what I would expect.

Can you temporarily disable the TV Listings plugin and try to reproduce with the built in TV Guide? Assuming you can still reproduce it, send the logs and database through again.

[roy]

Can you temporarily disable the TV Listings plugin and try to reproduce with the built in TV Guide? Assuming you can still reproduce it, send the logs and database through again.

sub, thanks for the support. I sent logs from fresh install with no other plugins, with some recordings still not scheduling.

[sub]

From your most recent emailed logs, here is a break down of when I see in the logs for Caillou. Please note the comments I've highlighted in bold. It details why several episodes where not scheduled (basically because the same episode is already scheduled for another time). Does this explain the recordings you thought were missing, or does it still not tally up? I get the feel something is not 100%, but I'm not sure what.

The only thing I can see wrong in the logs is that it applies part of the zap2it 'dont recording duplicates' logic, even though you havnt explicitly enabled it in the config. In it itself this isnt a huge problem though, unless you explicitly wanted the duplicates.

First its saves the master season recording record for Caillou:

2007-03-08 04:51:19.421 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:19.421 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:19.421 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:19.437 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:19.531 VERBOSE [1] Save(): Inserted new scheduled recording



Next it tells the system to look for any season recording episodes to record:

2007-03-08 04:51:19.546 VERBOSE [1] RecordingFactor.ScheduleSeasonRecordings(43, Caillou)
2007-03-08 04:51:19.546 VERBOSE [1] getValue() loading new key/value into cache: /settings/AvoidDuplicateRecordingsIfPossible
2007-03-08 04:51:19.546 VERBOSE [1] getValue: /settings/AvoidDuplicateRecordingsIfPossible : false
2007-03-08 04:51:19.593 VERBOSE [1] RecordingFactory.getExtrasForGroup(1)


Found a potential episode at 3/9/2007 6:30:00 AM, schedules a recording for it

2007-03-08 04:51:19.609 VERBOSE [1] Found potential match at 3/9/2007 6:30:00 AM (EP2335490203)
2007-03-08 04:51:19.609 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:19.609 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:19.609 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:19.609 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:19.609 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:19.750 VERBOSE [1] Save(): Inserted new scheduled recording
2007-03-08 04:51:19.750 VERBOSE [1] Requesting recording service schedule reload


Found a potential episode at 3/9/2007 12:00:00 PM, schedules a recording for it

2007-03-08 04:51:19.812 VERBOSE [1] Found potential match at 3/9/2007 12:00:00 PM (EP2335490205)
2007-03-08 04:51:19.812 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:19.812 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:19.812 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:19.812 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:19.812 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:19.906 VERBOSE [1] Save(): Inserted new scheduled recording
2007-03-08 04:51:19.906 VERBOSE [1] Requesting recording service schedule reload


Found a potential episode at 3/10/2007 6:30:00 AM, schedules a recording for it

2007-03-08 04:51:19.906 VERBOSE [1] Found potential match at 3/10/2007 6:30:00 AM (EP2335490201)
2007-03-08 04:51:19.906 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:19.906 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:19.906 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:19.906 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:19.906 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:19.968 VERBOSE [1] Save(): Inserted new scheduled recording
2007-03-08 04:51:19.968 VERBOSE [1] Requesting recording service schedule reload


Found a potential episode at 3/12/2007 6:30:00 AM, schedules a recording for it

2007-03-08 04:51:19.984 VERBOSE [1] Found potential match at 3/12/2007 6:30:00 AM (EP2335490199)
2007-03-08 04:51:19.984 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:19.984 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:19.984 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:19.984 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:19.984 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:20.062 VERBOSE [1] Save(): Inserted new scheduled recording
2007-03-08 04:51:20.062 VERBOSE [1] Requesting recording service schedule reload


Found a potential episode at 3/12/2007 12:00:00 PM, doesnt schedule a recording for this episode (EP2335490205) since this specific episode is already scheduled. See episode numbers for scheduled recordings above.

2007-03-08 04:51:20.062 VERBOSE [1] Found potential match at 3/12/2007 12:00:00 PM (EP2335490205)
2007-03-08 04:51:20.062 VERBOSE [1] - skipping episode because a schedule recording already matches this episode: EP2335490205


Found another potential episode. Again, a schedule recording already exists for this episode, so no point in scheduling it.

2007-03-08 04:51:20.062 VERBOSE [1] Found potential match at 3/13/2007 6:30:00 AM (EP2335490205)
2007-03-08 04:51:20.062 VERBOSE [1] - skipping episode because a schedule recording already matches this episode: EP2335490205


Found another potential episode at 3/13/2007 12:00:00 PM. Schedules a recording

2007-03-08 04:51:20.062 VERBOSE [1] Found potential match at 3/13/2007 12:00:00 PM (EP2335490206)
2007-03-08 04:51:20.062 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:20.062 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:20.062 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:20.062 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:20.062 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:20.140 VERBOSE [1] Save(): Inserted new scheduled recording
2007-03-08 04:51:20.140 VERBOSE [1] Requesting recording service schedule reload


Skipping another recording, due to existing scheduled recording for this episode

2007-03-08 04:51:20.140 VERBOSE [1] Found potential match at 3/14/2007 6:30:00 AM (EP2335490206)
2007-03-08 04:51:20.140 VERBOSE [1] - skipping episode because a schedule recording already matches this episode: EP2335490206


Found another potential episode at 3/14/2007 12:00:00 PM. Schedules a recording

2007-03-08 04:51:20.140 VERBOSE [1] Found potential match at 3/14/2007 12:00:00 PM (EP2335490207)
2007-03-08 04:51:20.140 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:20.140 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:20.140 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:20.140 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:20.140 VERBOSE [1] RecordingFactory.save()
2007-03-08 04:51:20.250 VERBOSE [1] Save(): Inserted new scheduled recording
2007-03-08 04:51:20.250 VERBOSE [1] Requesting recording service schedule reload


Skipping another recording, due to existing scheduled recording for this episode

2007-03-08 04:51:20.250 VERBOSE [1] Found potential match at 3/15/2007 6:30:00 AM (EP2335490207)
2007-03-08 04:51:20.250 VERBOSE [1] - skipping episode because a schedule recording already matches this episode: EP2335490207


Found another potential episode at 3/15/2007 12:00:00 PM . Schedules a recording

2007-03-08 04:51:20.250 VERBOSE [1] Found potential match at 3/15/2007 12:00:00 PM (EP2335490208)
2007-03-08 04:51:20.250 VERBOSE [1] - scheduling this episode
2007-03-08 04:51:20.250 VERBOSE [1] Looking for capture source to record: Caillou
2007-03-08 04:51:20.250 VERBOSE [1] Possible capture device: DEVICE:Hauppauge PVR150:1
2007-03-08 04:51:20.250 VERBOSE [1] Checking 'dummy' (DEVICE:Hauppauge PVR150:1)
2007-03-08 04:51:20.250 VERBOSE [1] RecordingFactory.save()

[roy]

From your most recent emailed logs,... The only thing I can see wrong in the logs is that it applies part of the zap2it 'dont recording duplicates' logic, even though you havnt explicitly enabled it in the config.

I won't quote the rest

This seems to explain it. I've been messing around so much trying to break it on two test PCs that I can't be sure what I've done anymore.

My HTPC has updated fine for the last few days, with I-xmltv and TVListings, so I'm happy to drop it now. Hopefully end of thread.

[roy]

Just to confirm, the patch posted in the v99.12 survival guide resolved this issue for me.

[sub]

Great.

[LesMcQueen]

Try the attached patch to see if it helps your machine boot for the EPG update. If it doesnt, then post the logs again because I've added some additional logging messages, which should give us more of an idea.

After upgrading to 99.12, I found that my PVR wasn't going back into standby after a recording.

Using this build of the Recording Service appears to have fixed the problem.



EDIT: Oops. I'm not quite sure how my reply ended up in this thread.