[mythtv] [mythtv-commits] Ticket #3418: [13136] prevents seeing channels with duplicate callsigns

Nick Morrott knowledgejunkie at gmail.com
Sun May 6 21:08:24 UTC 2007

On 06/05/07, Daniel Kristjansson <danielk at cuymedia.net> wrote:
> On Sun, 2007-05-06 at 14:24 -0400, Michael T. Dean wrote:
> > The reason I'm asking first is because of [13407] (
> > http://svn.mythtv.org/trac/changeset/13407 ).  Regarding that change,
> > Daniel, are we really saying that blank callsigns are allowed in a valid
> > MythTV configuration or is the extra code just to try to prevent
> > failures even with broken configurations?
> It is extra code to avoid some avoidable failures when there
> are blank callsigns. Not all problems are avoidable when you
> have blank callsigns because there can be a real ambiguity as
> to which channels are equivalent.

Should mythtvsetup not check for blank callsigns before it will allow
a user to exit and/or start mythbackend? As a somewhat experienced
user, it seems allowing a user to start mythbackend with an already
borked channel configuration is a very bad idea. If enforcing the
presence of a callsign for each channel is not deemed necessary, in
what circumstances is the absence of a callsign valid? Doesn't this
break the scheduler?

Wouldn't the introduction of some rudimentary checking in mythtvsetup,
such as for:

i) locating channels unassociated with video sources,
ii) locating card inputs unassociated with capture cards,
iii) locating listings information unassociated with video sources, and
iv) locating video sources unassociated with card inputs (this could
be due to temporary disabling of an input connection)

be of significant help to stop users from running broken
configurations in the first place?

MythTV Official wiki:
MythTV users list archive:

"An investment in knowledge always pays the best interest." - Benjamin Franklin

More information about the mythtv-dev mailing list