What is wrong w/ SageTV Conflicts?

[RRSwan3]

Tonight I was given a conflict notification only 1 hour before the programs were scheduled to be recorded at 9 p.m.. After further study of the EPG, the conflict could have easily been resolved if SageTV was able to decide on it's own to record one of the programs that was airing again in just 4 hours from the original conflicted time to resolve the conflict. I ended up having to manually set one of the programs to be recorded at the scheduled 9 p.m. and then manually set the other conflicted program to record at 1 a.m. to resolve the conflict myself. My experience with SageTV 1.4 was that the program did this on it's own and there was never a reason for the user to manually correct these sort of conflicts. I also never experienced conflicts being discovered so short of the scheduled time. With SageTV 1.4 I would normally get a notification of this kind of conflict at least 2 days prior to the recording date / time. What gives? I never had this problem with SageTV 1.4, and I'm curious if there is a setting in SageTV 2.0 that is different to resolve this. Any help would be appreciated. I'm afraid at this point that SageTV 2.0 isn't looking as good as I first thought if these sort of problems are going to continue. This feature spoiled me tremendously with 1.4.

[Opus4]

When was the last EPG update done? If the listings changed, it wouldn't show up until now. Also, what show was it?

Does each episode have the same ShowID or does it have the sam # for each? If SageTV can't tell episodes apart, it won't know they are the same.

I don't know if either of those covers what actually happened, but they are possibilities.

- Andy

[xlr8shun]

i noticed some weird behavior with the conflict screen the other day.

i added 2 new favorites, and was moving them around in the list.. well i noticed i got some conflict warnings.. no big deal this was expected. so i go to the conflict screen. and i have like 50 conflicts listed.. only thing is only like 2 of them had the conflict icon next to them (listed as being new)

all the conflicts involved the 2 new favorites i added, so the only conclusion i can come to right now is, while i was arranging my favorites, sage was immediatly starting to resolve the conflicts, as well as listing them. whether or not it tries to resolve immediatly i dont particularly care about, but i dont really need sage to tell me about every single one of them.

on a side note, i think it would be usefull for a way to delete conflict notifications.. and/or the ability to set it to 'resolved' or 'unresolved', manually. the conflict section still seems... a bit screwry sometimes, i just havent pinned it down.