[mythtv-users] [RANT] mythtv-users] Deal with non-HD in SD only frontends?

Michael T. Dean mtdean at thirdcontact.com
Mon Dec 21 22:03:33 UTC 2009

On 12/21/2009 02:32 PM, Bill Bogstad wrote:
> On Mon, Dec 21, 2009 at 1:37 PM, Michael T. Dean wrote:
>> On 12/21/2009 01:18 PM, David Brodbeck wrote:
>>> On Mon, December 21, 2009 9:34 am, Bill Bogstad wrote:
>>>> If some poor unfortunate soul who can't get ATSC listings to import
>>>> from SchedulesDirect finds
>>>> this note, the solution is to set your ATSC separator to a dash "-"
>>>> not a period ".".  The only reference
>>>> I found to this is on a blog. http://murraysaul.wordpress.com/.
>>> That seems like the kind of thing that ought to be tested for in the code;
>>> it sounds like an easy, basic sanity check.
>> THe problem occurred because the channel information reported by the stream
>> and captured into the database during scanning used different identifiers
>> from the ones used by SD.  Therefore, mfdb was unable to automatically link
>> MythTV channel information to SD listings information.
> I believe in this case that the 'stream' comes from MythTV's built in
> channel scanner

No, the stream is the data coming from the capture card.

>  and the separator is specifiable by the user (if they
> know to do so) in mythtv-setup.

And the formatted channel number is only one of many pieces of data 
compared to see if a channel described in the listings whose ID doesn't 
match any of the xmltvid's in the MythTV database matches any channels 
in the MythTV database without xmltvid.

>  Michael Dean seems to be advocating
> that rather then changing one setting so that mfdb's voodoo can work
> correctly with SD listings  that one should instead go in and manually
> set the xmltvid's for all of one's  OTA ATSC channels.   This seems to
> me to be the wrong solution for SD listings, ATSC and MythTV
> integration.  The solution the author of that blog advocated (and I
> repeated) seems to be less prone to user error.   Micheal: Are you
> suggesting that whatever voodoo that causes this to work now is likely
> to go away?  (and therefore should NOT be documented/suggested)

I'm simply suggesting that you use the UI-provided means of editing 
channel information until someone goes to the trouble of fixing all of 
the issues with the brand new channel scanner (which has /already/ fixed 
a significant number of issues with the old channel scanner):


Feel free to change the channel separator, but do so through the UI when 
scanning channels--don't do it through editing the DB.


More information about the mythtv-users mailing list