Inconsistent recurring recording issue

[baj1]

This problem is back. According to my wife, it has been for quite some time, but I didn't notice and she didn't mention it. I noticed because I've been missing the first of the back-to-back episodes of "Lost" (Wednesdays 7-9pm) and my wife pointed out that it missed both of the "Law and Order" episodes this week (I believe it was Monday 7-9pm). These are both setup as reoccurring "season". Logs are attached.

[martint123]

I'm always suspicious of "Don't record duplicates" when I read of this happening.

p.s.

Logs are attached.

I don't see them :confused:

[baj1]

Oops, got a little click-happy. Here's the logs. I'll look for the "duplicates" setting.

Thanks,
-Brad

[baj1]

Forgot to mention I did look in the logs, but didn't see anything suspicious (to me). But what do I know. I can resend after I notice the issue again, I presume that may be more useful?

Martin, is this the setting you were referring to in config.xml?
<AvoidDuplicateRecordingsIfPossible>true</AvoidDuplicateRecordingsIfPossible>

Thanks,
-Brad

[martint123]

Martin, is this the setting you were referring to in config.xml?
<AvoidDuplicateRecordingsIfPossible>true</AvoidDuplicateRecordingsIfPossible>

Yes, that is it, but is normally used from config.exe in the front page of 'capture sources'

GBPVR keeps a list of what I call magic numbers that the EPG supplier provides that is unique to a show. gbpvr uses this to prevent recording repeats. I was just wondering if changing it to false would help to pin down one possible reason for missing a recording as it has cropped up in the past. The US is one of the very few places that provide this EPG facility.

These sorts of entries from the recordingserviceexe.log show recordings that are being skipped as the database says they have already been seen. Cross referencing them is another matter though. If you can put up with some repeats getting recorded it may be worthwhile turning this option off for a day or two to see if that is it??

Code:

2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP004461600051
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP004461600130
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP000039860066
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP009248440042
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP001151270041
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP001151270224
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP004461600052
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP004461600131
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP000039860070
2010-03-05 07:07:37.660    VERBOSE    [12]    Already has recording: EP001151270042

[TomR]

I have had this happen several times to me as well. It seems to happen sporadicly maybe every couple of months.

I have not done any trouble shooting on what may be causing this. I'll try to do some when it happens again.

The workaround I use is to delete the reoccurring recording and recreate it. Once recreated it recognizes and recordings. While this workaround works it requires you to notice the problems to begin with.

I'd be interested to see how many others are noticing this happening.