[mythtv] [mythtv-commits] Ticket #6600: Apparent design flaw in handling changes on channel structure in DVB transmisions.

[Stuart Auchterlonie]

On Wed, Jun 03, 2009 at 11:20:42AM -0000, MythTV wrote:
> #6600: Apparent design flaw in handling changes on channel structure in DVB
> transmisions.
> --------------------------------------+-------------------------------------
>  Reporter:  barberio at lineone.net      |       Owner:  danielk   
>      Type:  defect                    |      Status:  new       
>  Priority:  major                     |   Milestone:  unknown   
> Component:  MythTV - Channel Scanner  |     Version:  0.21-fixes
>  Severity:  high                      |     Mlocked:  0         
> --------------------------------------+-------------------------------------
>  Attention needs to be drawn to the bad user experience of
>  http://www.gossamer-threads.com/lists/mythtv/users/383253
>  which is something that hit all UK users of MythTV with the lineup changes
>  that happen regularly on DVB-T here.

Having read that entire thread there were clearly 2 issues.
1. no signal on the mux holding the new channel
2. they did incorrectly signal that there wasn't EIT data available
on the new virgin1 channel

> 
>  This is a pretty major design flaw, that Myth can't handle lineup changes,
>  and keeps storing the old channel data even when it's wrong, and the

This is just wrong. It doesn't "keep storing" channel data. It's stored
once at setup time. If you were using mythfilldatabase to populate your
channels then it's quite likely that the source was slack in adding the
new virgin1 changes.

We used to dynamically adjust the channels based on the signalling info.
This worked fine in the UK, but in other countries, when their channels
go "off-air" they are removed from the signalling tables.

The consequence of this is the channels would constantly be added and
removed, which plays havoc with recording schedules. So mythtv was changed
to not automatically update the channel listing.


Stuart