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

Michael T. Dean mtdean at thirdcontact.com
Sun May 6 18:24:22 UTC 2007

On 05/06/2007 02:01 PM, MythTV wrote:
> #3418: [13136] prevents seeing channels with duplicate callsigns
> Comment(by danielk):
>  Just for the record, the program guide groups channels with the same
>  callsign iff they have the same channel number. Take for example WABC-DT,
>  it is listed as 7-1 from OTA and 1071 from CATV. The reason the channel is
>  listed under both channel number in the program guide is only so that if
>  you remember that the channel number is 1071 or 7-1 you will find it where
>  you expect it in the ordered list. As far as MythTV is concerned they are
>  the same channel, if you set up a manual recording on 1071 it is just as
>  likely that it will be recorded on 7-1 as 1071.

For the benefit of the OP, can we go a step farther and say that Myth 
requires that any channels with different programming content must have 
unique callsigns?  The OP does not have his system set up that way 
("I've been unable to browse listings for channels with duplicate 
callsigns, even though they have different programming.").

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?  After all, channel.callsign 
is a NOT NULL column, so officially allowing the empty string sounds 
like extra work with no real benefit.  (Not to say trying to recover 
even with broken configs is bad, but I just want to ensure I don't pass 
on bad info when I tell people we need unique callsigns for channels 
with different content.)


More information about the mythtv-dev mailing list