[mythtv-users] Scheduling: prefer input

Yeechang Lee ylee at pobox.com
Sat Aug 5 20:47:30 UTC 2006

I wrote:
> Of my two identical FireWire cable boxes (both on the same backend,
> of course), I've noticed over the past few months that mythbackend
> always chooses box #2 first. It only uses box #1 when #2 is already
> in use. Needless to say, both boxes hve identical priorities in
> mythtv-setup. More to the point, I am almost certain that when I
> first set up MythTV with dual cable boxes in January, and for some
> time afterward, mythbackend chose either box first seemingly
> randomly; indeed, I figured the system was intentionally designed to
> randomly pick a box when all else was equal. I think, but can't be
> sure, that this may have changed when I moved from 0.18.1 to
> 0.19. Am I imagining things, or did the codebase change in this
> regard?

Michael T. Dean <mtdean at thirdcontact.com> says:
> It didn't change.  Perhaps your configuration/recording rules did.

That's an extremely unhelpful answer, but then I'm used to such from
you (with
a prior example).

As mentioned previously in the thread, I don't use SVN so can't
specify the input I want within a program listing. And as I mention
above, the two cable boxes carry the same input priorities. Thus, as
far as I kow, there's *nowhere else* I can tell MythTV to prefer
recording from one cable box over the other. Nonetheless, the behavior
*has* changed (unless, as I also note the possibility of, I'm
imagining things) sometime during the past few months, possibly in the
0.18-0.19 upgrade, from "sometimes #1, sometimes #2" to "always
#2 unless it is already being used").

As I don't contribute to the MythTV source I'll have to accept your
word that the relevant portion of the mythbackend code didn't change,
but that only deepens the mystery.

Yeechang Lee <ylee at pobox.com> | +1 650 776 7763 | San Francisco CA US

More information about the mythtv-users mailing list