I have two tuners. 150 and 150mce

I'm recording Smallville from 9-10
and another Smallville from 10-11.
Both of these are recurring season recordings.

I tried to add recording (for my wife) the Oscars from 7:30-10:30
and got a recording conflict message. That doesn't seem like a conflict for a two tuner system.

I deleted one of the Smallvilles, added the Oscars, and added the deleted Smallville back in and got no conflicts.
Is this expected?

Do you have <PreferAlternatingCaptureSources> set to true in config.xml?

PreferAlternatingCaptureSources is set to false.

I'm not really sure.

I tried the same type of scenario for next week as well. Same conflict shows up when there shouldn't be one.
If logs would help let me know.

Sorry, I'm recovering from the flu and the drive just isnt there to chase this bug today. Tell me next week if it happens again.

Sorry you're not feeling well. Maybe it's time to activate the Vbulletin automatic answer BOT for a few days.
Take care.

pastro Wrote:Maybe it's time to activate the Vbulletin automatic answer BOT for a few days.

LoL!!!

Hope you feel better sub!

I just wish I could take credit for the original idea. Bgowland
wrote this the other day.

bgowland Wrote:I was thinking the other day that he might have a 'Special Edition' vBulletin client with buttons for 'Post your logs...', 'No', 'Never going to happen', 'Maybe in a future release', 'This is fixed for the next release'.

pastro Wrote:That doesn't seem like a conflict for a two tuner system.

I've seen this behavior as well, where deleting and rescheduling an episode of a reoccuring recording resolves the conflict. But then after EPG update, the conflict returns. I found that deleting the reoccuring recording and then rescheduling it in proper order resolved it. I think it has to do with GBPVR reassigning predetermined tuners for a reocurring recording after an EPG update. Some of these reoccuring recordings may have been originally scheduled with <PreferAlternatingCaptureSources>true. I now have <PreferAlternatingCaptureSources>false and <TryToHonourPaddingIfPossible>true, so the conflict may have resolved itself upon recording, but I didn't try it.