Recurring recording priority bug?

[BerkA]

I noticed a conflict flagged in my recordings that I wasn't expecting. The scenario looks like this:

• Show A and B are recurring recordings (Record Season -- all episodes on this channel)
  
• Show A has higher priority than show B on my recurring recordings menu.
  
• On some day, show B runs 9pm to 10:30pm, show A runs 10pm to 11pm.
  

I expect show A (higher priority) to record and show B to be cut short or not record at all because of the conflict.

GBPVR seems to indicate that show A won't record due to a conflict with show B. On TV Guide, show A is orange (conflict) and show B is red (will record). The conflicts menu lists show A as having a conflict.

I do not know what will happen when the time comes to record, since this case happens sometime in the next week. However, the UI seems to indicate that the lower-priority show will record.

Is this a bug? Is it known/expected? What will happen when the show is actually aired?

[sub]

Its pretty hard to tell why this happened after the fact unless you still have the GBPVRRecordingService.log that covers the time period when these shows first appeared in the EPG?

What will happen when the show is actually aired?

It wont attempt to record any shows that is marked as a conflict.

[philly_phenom]

I've occasionally seen a couple shows flagged as conflicts that didn't make sense. One time I checked & it was flagged as conflicting with a show that didn't even overlap timewise.

When I deleted the recording & added it back, everything was good. I usually don't worry about it since it doesn't happen that often & I usually make a point of checking for conflicts every couple of days.

[pBS]

probably a case of epg timeslot changes...when first scheduled, it was a conflict...but after update, the conflict isn't there in times, but it's already been marked as conflicted...
at least i think that's how it works...

but yea, hard to know from the logs...

hey, i think a -emptyepg would clear it... [or do empty/reload epg manually]
if it's a schedule thing, it'll re-schedule it with current epg times, which shouldn't be a conflict..

[philly_phenom]

probably a case of epg timeslot changes...when first scheduled, it was a conflict...but after update, the conflict isn't there in times, but it's already been marked as conflicted...

That makes sense. Like I said, I'm not really concerned about it since it doesn't happen all that much.

[BerkA]

Its pretty hard to tell why this happened after the fact unless you still have the GBPVRRecordingService.log that covers the time period when these shows first appeared in the EPG?

OK, I believe you'll have what you need in the attached logs. However, this isn't going to be a case of the show appearing in the EPG. I had been removing/adding these shows to the recurring recordings list. I had then rearranged their priority. Is the change in priority honored right away or do new episodes have to appear in the EPG?

Show A is "Eli Stone" Show B is "Masterpiece" The case where I see the problem happens on April 13.

[sub]

Is the change in priority honored right away or do new episodes have to appear in the EPG?

No, not right away. It only affects new shows scheduled.

[BerkA]

Sub,
That seems to explain the behavior I saw. Here's my informal reconstruction of events:
When I added a new show, it -- by default -- became the highest-priority show. As a result, I guess GBPVR went ahead and scheduled the next two weeks with the newly-added show as the highest priority. Then I went to the recurring recordings list and changed the show's priority to where I wanted it to be. Unfortunately, this had no effect, leaving the next two weeks worth of shows out-of-order in terms of priority.

I've gone ahead and resolved the conflicts for the next two weeks.

Is there another way to tell GBPVR to "reschedule everything" to "automagically" resolve conflicts?

[sub]

Is there another way to tell GBPVR to "reschedule everything" to "automagically" resolve conflicts?

This will usually happen at the next EPG update anyway, since it deletes the pending episodes of the season recordings, then recreates them with the new data in the database. The only exception is the first episode in any season recording - it stays in the database as the master record.