[mythtv-users] Show Recording on Two Encoders at The Same Time

[Michael T. Dean]

On 12/13/2009 01:08 PM, Mike Perkins wrote:
> Larry K wrote:
>> On Sun, Dec 13, 2009 at 9:26 AM, Charles Wright wrote:
>>> I think I found my problem, the callsigns were different one was
>>> "WWOR" the other was "WWOR ", causing them to be treated like two
>>> separate channels.  I'm still not sure what the reason for both
>>> getting recorded (because I selected a specific showing), but since my
>>> setup was buggy; it really doesn't matter.
>>>  
>> I've been seeing similar issues, but it never occurred to me that the
>> channel callsign is controlling the scheduler.  I just assumed the
>> scheduler
>> uses the xmltvid.

As you found, it's not the xmltvid.  xmltvid is only used to determine
which listings data is associated with a channel.  See
http://www.gossamer-threads.com/lists/mythtv/users/413008#413008 .

>>    Now that I have corrected my callsigns (i.e., WETA vs.
>> WETADT4), the duplicate recordings have stopped.
>>
> Oh, I do hope not. On my Virgin source, I have ten channels labelled
> SKYMO (Sky Movies various) and five labelled SKYSP (Sky Sports 1, 2,
> 3, Extra and News).

Yes.  The callsign is simply a /user-editable/ field whose purpose is to
allow users to specify which channel contain "substantially" identical
content (read "completely identical").

A callsign is used for /every/ "this channel" rule to define the meaning
of "this channel."  So, if you create a "this channel" rule for a
showing listed on a channel with a callsign of "SKYMO", then Myth will
record it from any channel with the callsign SKYMO.  If last-minute
schedule changes are required (due to LiveTV or other interruptions),
having multiple /different/ channels with the same callsign may cause
other problems, too.

> The brief callsigns that work in the US don't work elsewhere in the
> world.

The /only/ thing that doesn't work for the rest of the world is the name
of the field.  So, call it, "Unique identifer of channel content," if
you prefer.  But, no 2 channels having differing content should /ever/
have the same callsign.  2 channels having identical content /may/ or
/may not/ have the same callsign--depending on whether you want them
treated as identical channels.  This is useful if you want to
distinguish between standard def and high def versions of a channel.

Let's see if I can help you make those channels work...

SKYMO0, SKYMO1, SKYMO2, SKYMO3, SKYMO4, SKYMO5, SKYMO6, SKYMO7, SKYMO8,
SKYMO9
and
SKYSP0, SKYSP1, SKYSP2, SKYSP3, SKYSP4

Or, get a little more creative.  You have 20 characters with which to
make your unique identifiers, so the only thing that's limiting non-US
users is their preconceptions that callsign is meaningless outside the US.

It's /your/ responsibility to ensure that your user-editable data is . 
Just because your broadcaster gives garbage that's not usable, doesn't
mean that Myth can automatically determine that the channels are not, in
fact, the same channel.

Myth does realize when the listings differ, but that doesn't make a
configuration with 10 different channels having the same callsign any
less broken.  So, if things don't work right, don't blame Myth.  The
ability to notice when listings differ slightly is only there to support
those who have channels that are "substantially" identical--but really,
if you notice that there are any differences in listings, your channels
are probably not identical enough (we're talking about the once in a
blue moon differences when we say "substantially" identical).

Mike