[mythtv] [mythtv-commits] Ticket #1203: Fix channels.conf import for ATSC OTA/QAM

Boleslaw Ciesielski bolek-mythtv at curl.com
Fri Feb 3 23:02:03 UTC 2006

Daniel Kristjansson wrote:
>>> If you can fix the channum column issue (assign consecutive 
>>> numbers starting at 1 if you must, but don't use any numbers 
>>> already assigned to a channel from a previous scan),

Unfortunately this won't work, because the channel numbers in the guide
data can be arbitrary and are not known in advance.

Unless we run mythfilldatabase first and then the scan? Hmm...

> * match channels by callsign This will cause too many problems. Can
> you write something that tries to fill in the blank XMLTV id's from
> the callsigns instead?

I am not sure what you mean? This is exactly what it's doing now.

> Unfortunately, it's impossible to do this automatically with zap2it 
> information since the scan doesn't find anything that can be 
> translated into an XMLTV id. You need to either enter in the channel
>  numbers or the channel name manually...

Well, my idea was to use the callsign from channels.conf. Are you saying
that this is not unique enough (within a sourceid)? If this is so, then
like you said maybe we need to table this issue for now although I will 
think some more.

You can still commit the first part though.

> Otherwise work on this for 0.20, though it might be a better use of 
> your time to figure out why the internal QAM scanner isn't working 
> for you.

It's working for me but the problem is that it produces tons of junk
channels and there is no easy way to get rid of them. Also, for the
desired channels, there is no way to associate the guide data without
manually entering xmltvid.

Also, having an accurate channels.conf has other benefits outside of
myth. And once you do the work, why not reuse it?


More information about the mythtv-dev mailing list