2005-02-23, 12:58 AM
Re-hashing the problem from the old conflict bug, which is as follows (in a nutshell):
Manually update the EPG in the config, conflicts show up (which also re-starts the recording service).
Let GB-PVR do it iself in the 3-4AM update, the conflicts never show up.
This is with the Zap2It configuration not XMLTV.
Now I've stumbled on a NEW conflict bug.
You have a program that conflicts with a season record program. You cancel the season record for that program. The conflict still remains in the conflict list, but when you choose "resolve" there's nothing TO resolve, and your only option is "make no changes leave conflict in place". Updating the EPG manually DOES NOT fix this problem!!
Manually update the EPG in the config, conflicts show up (which also re-starts the recording service).
Let GB-PVR do it iself in the 3-4AM update, the conflicts never show up.
This is with the Zap2It configuration not XMLTV.
Now I've stumbled on a NEW conflict bug.
You have a program that conflicts with a season record program. You cancel the season record for that program. The conflict still remains in the conflict list, but when you choose "resolve" there's nothing TO resolve, and your only option is "make no changes leave conflict in place". Updating the EPG manually DOES NOT fix this problem!!