[mythtv-users] scheduling conflict that should not be

David Engel david at istwok.net
Mon Aug 23 17:02:50 UTC 2010

On Sun, Aug 22, 2010 at 02:56:27PM -0400, Brian J. Murrell wrote:
> I proceeded to force the conflicts to analog tuners with success,
> however even with the digital tuner now free, the new recording is still
> showing as a conflict.
> Here's the --printsched output for the time window of the conflicting
> recording:
> [...]
> As you can see, "OGHNM" is a conflict in the Recording Status even
> though the only recordings that overlap with it have been forced onto
> the analog broadcast for the same channels.
> Any thoughts as to what's going on here?

The --printsched doesn't provide enough information to draw any
conclusions.  What does "mythbackend -v schedule --testsched
--printsched" report?

David Engel
david at istwok.net

More information about the mythtv-users mailing list