[mythtv] Re: Ticket #802: DiSEqC confuses channel changing with LiveTV

Luis Ochoa luis.m.ochoa at gmail.com
Thu Dec 15 11:51:41 EST 2005

Could this be why, while in LiveTV, if I try to change to a channel in
a different port (I have a Tone Switch, which by the way doesn't
switch anything, I had to play with the LNB LOF switch value to get it
working, 0 for 22khz ON port and 99999999 for 22khz OFF port...but
that's a different issue) say from a channel in 119 to a channel in
110 I get a message to the effect that all the cards  are in use, that
I need to stop a recording (although nothing is being recorded) ??

This is with the newer code, the older 0.18.x code switches ports fine.

On 12/15/05, MythTV <mythtv at cvs.mythtv.org> wrote:
> #802: DiSEqC confuses channel changing with LiveTV
> -------------------------------------+--------------------------------------
>  Reporter:  nooneimprt4nt at gmail.com  |        Owner:  ijr
>      Type:  defect                   |       Status:  new
>  Priority:  minor                    |    Milestone:
> Component:  mythtv                   |      Version:  head
>  Severity:  medium                   |   Resolution:
> -------------------------------------+--------------------------------------
> Changes (by nooneimprt4nt at gmail.com):
>   * milestone:  0.20 =>
>   * component:  dvb => mythtv
>   * owner:  danielk => ijr
> Comment:
>  I am including a patch which fixes this in a more appropriate manner.  It
>  still does not use the channelnames[] map the way it was originally
>  intended, but I'm not sure it makes sense with respect to a diseqc switch.
>  Basically, to use the map as expected, the dvbchannel struct would need to
>  include cardinputid somewhere, which would be used as the index into
>  channelnames[].  However, if you need to do that, you might as well just
>  get the actual inputname and use that directly (which is what I've done).
>  It all comes down to the fact that there is no way to gaurantee a 1:1
>  mapping between a switch <port,pos> pair and its inputname (though in
>  theory they would be unique).
>  If you'd prefer a different manner, let me know, but everything else I
>  tried got pretty complex.  I suppose it would make sense to index off of
>  cardinputid if we wanted to support external channel changes, and that
>  would be easy enough to do, but the method I chose resulted in the minimal
>  amount of code changes.
> --
> Ticket URL: <http://svn.mythtv.org/trac/ticket/802>
> MythTV <http://www.mythtv.org/>
> MythTV

More information about the mythtv-dev mailing list