[mythtv] [mythtv-commits] Ticket #8211: Incorrect channel change with a channel group and multiple sources

[Markus Schulz]

Am Donnerstag, 2. Juni 2011 schrieb MythTV:
> #8211: Incorrect channel change with a channel group and multiple
> sources
> ---------------------------------+----------------------------
> Reporter:  scottadmi@…          |          Owner:  danielk
>      Type:  defect               |         Status:  infoneeded
>  Priority:  minor                |      Milestone:  0.25
> Component:  MythTV - General     |        Version:  head
>  Severity:  medium               |     Resolution:
>  Keywords:                       |  Ticket locked:  0
> ---------------------------------+----------------------------
> 
> Comment (by Markus Schulz <msc@…>):
> 
>  yes, if you have enabled BrowseAllTuners=1 and BrowseChannelGroup=1
> you still got the first channelgroup entry after start browse-mode.
> if you disable one of the options, it works as expected.

but it looks like a problem with building the channel groups.
if you build a channel group, you select a "channel", but it reflects 
only the channel from one (first?) source (not the same channel from 
another source with same name and number).

Therefore if you are on the other (second?) source and start browse mode 
(inside a channel group) with enabled BrowseChannelGroup=1 it can't find 
the current channel in the current channel group (only channels from the 
other source are inside the group) and you start from the first channel 
(possibly not part of the group).

i know that dev's currently suggest to give the same channel from a 
second/third/.. source a different number to avoid this. But thats 
really a pain from user perspective ("Record on this channel" is fixed 
to single source, memorize more channel numbers, longer epg/browse 
listings, ...).

has someone thought about a refactoring of the channel framework to 
something like this:

[Channel] : (ChannNr, ChannName, ChannNetworkName{currently not parsed 
but needed}, Icon, ...)
   ^
   |
[ChannelSource] : (ChannID, ChannNr, SourceID, ServiceID, MPlexID, ...)
   ^
   |
[Multiplex] : (MplexID, SourceID, ...)


all EPG informations are assigned to [Channel] and can come from 
different sources. Each Source can have a "quality" value to allow 
preferred recording of "better" sources (i.e. DVB-S > DVB-T > analog, 
..).

what other aspects should be minded? 
Are there any showstopper issues, i.e. important things currently 
possible but not afterwards?

i know such a refactoring would be very punishing but with a high reward 
in my opinion.

regards,
msc