v9 Conflict Confusion

[amg]

I have been using SageTV for more than a decade. I recently upgraded my setup to unRaid and v9 when my old hardware decided it had enough. It has been a long time since I saw a conflict icon, but have had a few since migrating to v9.

Last night a conflict popped up for the show Imposters on 3/21. It conflicts with The Americans. Both episodes have additional airings, which I thought would resolve the conflict. Is the conflict resolution behavior different in v9?

[waynedunham]

Originally Posted by amg

I have been using SageTV for more than a decade. I recently upgraded my setup to unRaid and v9 when my old hardware decided it had enough. It has been a long time since I saw a conflict icon, but have had a few since migrating to v9.

Last night a conflict popped up for the show Imposters on 3/21. It conflicts with The Americans. Both episodes have additional airings, which I thought would resolve the conflict. Is the conflict resolution behavior different in v9?

I have a LOT of favorites and see this all the time in V7 and V9 (I have 2 Sage machines) when the recordings are that far out (13 days in your instance)

I usually can't wait for it to possibly revolve itself when the date gets closer and end up setting up one or as many of the conflicting recordings as necessary to manual alternate airings to make the conflict go away.

Another thing I have seen that may cause this is when the EPG data doesn't mark new airings as 1st run so even though there are multiple additional airings if your favorite is set to 1st run only it won't consider the ones not marked as 1st run (even though they indeed are)

[EnterNoEscape]

Originally Posted by waynedunham

I have a LOT of favorites and see this all the time in V7 and V9 (I have 2 Sage machines) when the recordings are that far out (13 days in your instance)

I usually can't wait for it to possibly revolve itself when the date gets closer and end up setting up one or as many of the conflicting recordings as necessary to manual alternate airings to make the conflict go away.

Another thing I have seen that may cause this is when the EPG data doesn't mark new airings as 1st run so even though there are multiple additional airings if your favorite is set to 1st run only it won't consider the ones not marked as 1st run (even though they indeed are)

First run is based on a few criteria. The first one is if the EPG data flags it as a first run. The second one is if the original airing date is I believe within the last two weeks. There might be a third criteria that I'm missing, but that's what I remember from when I looked at that last. Is that kind of what you were expecting would be checked when determined a first run?

[waynedunham]

Originally Posted by EnterNoEscape

First run is based on a few criteria. The first one is if the EPG data flags it as a first run. The second one is if the original airing date is I believe within the last two weeks. There might be a third criteria that I'm missing, but that's what I remember from when I looked at that last. Is that kind of what you were expecting would be checked when determined a first run?

From my experience whether the 1st run flag is set or not it seems that the conflicts that have other options for times/dates only show up when you are out near the end of the EPG data window.
It may also be a factor of how many days you have it looking out in settings (or is that only for Intelligent Recordings which I use?). I was an early adopter of extending the look ahead window, back before it was part of the settings menu and you had to set the value manually in sage.properties.

I did also notice that the Schedules Direct EPG data seems to go out further than the old built in Sage EPG. I'm seeing 20-21 days of EPG data with SD where you'd only get what 12-14 with the old EPG? May that be a factor?

[Tiki]

Actually, it may not be your imagination - I've noticed something seems a little different in v9 too.

In my case, I have 2 HDHR-primes (3 tuners each) for recording most channels, and 1 HD-PVR for the premiums. I have Sage set to schedule recordings 7 days out. I'm still using the old Sage EPG service which gets guide data about 12 days into the future.

Since upgrading to v9, I now get conflict notices every Sunday that will clear up on their own after a few days. I've noticed that most of the premium channels debut their new episodes on Sunday nights, and then repeat throughout the week.

I'm not 100% sure, but I think Sage used to use all available guide data for conflict resolution. So even though I told it to only schedule recordings 7 days in advance, if it had 12 days of data available and if there were conflicts and they could be resolved on days 8-12, Sage would go ahead and schedule the recordings outside the 7 day window. It seems to me that in version 9, Sage no longer looks beyond that 7-day window for conflict resolution.

[EnterNoEscape]

It's not your imagination. One of the Scheduler performance optimizations added to v9 was to give up after a fairly large number of permutations with the assumption that it's not going to get anywhere. The problem is what you're seeing proves that idea wrong.

[mechling-burgh]

I have noticed this also, and have just been correcting them manually by telling it to record a future airing. I thought it was my imagination, glad to see other people having this problem.

[waynedunham]

Originally Posted by EnterNoEscape

It's not your imagination. One of the Scheduler performance optimizations added to v9 was to give up after a fairly large number of permutations with the assumption that it's not going to get anywhere. The problem is what you're seeing proves that idea wrong.

That may be why I've been seeing far out in the EPG conflicts in V7 and even more in V9. As I said, I have a LOT of favorites, and 8 tuners on the V7 machine (4 HDHR Prime Tuners, a full prime and one tuner from a 2nd prime, 2 HD-PVR/STBs, and 2 OTA original HDHRs), and 9 tuners on the V9 Win8.1 machine. (5 HDHR Prime tuners, a full Prime and 2 tuners from a 2nd prime, and 2 HDHR Connects giving me 4 OTA tuners)

So lots of conflict options for SageTV to figure out and it may just be "giving up" earlier on the V9 machine. I probably should start waiting longer to see if it resolves the conflicts on its own as time goes on. But that little conflict icon in the header just bugs me.

[BobPhoenix]

I've always seen this even back on v6 of SageTV. Like others I just force a manual recording for later and the conflict will go away. I've even done that and then the next day cancelled the manual recording and the favorite says with the later time - maybe because of the delay of a day between setting the manual recording and then canceling it - don't know.

[waynedunham]

Originally Posted by EnterNoEscape

First run is based on a few criteria. The first one is if the EPG data flags it as a first run. The second one is if the original airing date is I believe within the last two weeks. There might be a third criteria that I'm missing, but that's what I remember from when I looked at that last. Is that kind of what you were expecting would be checked when determined a first run?

I just remembered that in v7 anyway I HAVE seen instances where the EPG data not marked as 1st run has the same original air dates as listings that were marked as 1st run. All within the 2 week window (going forward from present time/date). Going through the adjust favorites menu and using "additional airings" on a 1st run favorite it does not show the ones not marked as 1st run, but if I change the favorite to 1st runs and reruns they do show up in the additional airings.
I haven't noticed it in v9, but haven't been running it long enough to have seen many of these scenarios and haven't been paying close enough attention to the marked as 1st run and other airings with the same original air date that weren't marked as 1st run.

So, at least in v7 there seems to be some criteria that is superseding the original air date and knocking those not marked as 1st run out of the equation. Whether that still holds true in v9 I don't have any evidence one way or the other.

Id does appear that even though it is little used by most SageTV users they did do some massaging of the Intelligent Recording algorithms. Either that, or it is just due to the changeover to SD EPG data causing me to do wholesale "ignores" on a whole rash of stuff that popped up as soon as I started running V9 and set it up for SD EPG. I do, and always have run IR with "aggressive negative profiling" turned on.