[mythtv-commits] Ticket #11509: mythfilldatabase pulls incorrect channel information from Schedules Direct

[MythTV]

#11509: mythfilldatabase pulls incorrect channel information from Schedules Direct
----------------------------------+--------------------------------
 Reporter:  ccoager@…             |          Owner:
     Type:  Bug Report - General  |         Status:  infoneeded_new
 Priority:  minor                 |      Milestone:
Component:  MythTV - General      |        Version:  0.26-fixes
 Severity:  medium                |     Resolution:
 Keywords:                        |  Ticket locked:  0
----------------------------------+--------------------------------

Comment (by mdean):

 Actually, channel 6 and channel 506 (I'm glad you figured out my typo in
 my post, where I had said 468) are the same channel in MythTV because:

 a) they have the same call sign, which says they should be treated as
 exactly identical for the purposes of scheduled recordings--meaning you do
 not care which one is used

 b) they have the same channel number (6), which says that they should be
 treated as exactly identical for the purposes of Live TV--meaning you do
 not care which one MythTV tunes when you type in 6 in Live TV

 c) they have the same call sign /and/ channel number, so they are treated
 as identical for the purposes of the EPG (guide)--meaning you only want to
 see the channel once in the guide

 To tell MythTV they are different, you will need to use mythtv-setup or
 MythWeb's or mythfrontend's Channel Editor to (manually) change either the
 call sign (so you can schedule recordings for one or the other channel,
 specifically, using the "this channel" filter on recording rules), or the
 channel number (so you can tell MythTV which one to tune during Live TV),
 or both.  Once you do so, both channels will become available/listed
 separately in the guide/independently-selectable for use in MythTV.

 So, the only thing remaining is to see why MythTV is choosing to use the
 same channel number for both channels, which I'll look into.  I'm guessing
 it's doing so because the lineup data tells it to, but I'll verify there's
 no uninitialized data type problem or insufficiently-specific data
 retrieval problem in our code causing us to reuse one channel's number for
 the other.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/11509#comment:9>
MythTV <http://www.mythtv.org>
MythTV Media Center