[mythtv] IPTV with an external channel changer

Lincoln lincoln at performaplus.co.nz
Tue Oct 29 09:33:57 UTC 2013

On 29/10/2013 7:19 p.m., Jean-Yves Avenard wrote:
> On 29 October 2013 14:42, Lincoln <lincoln at performaplus.co.nz> wrote:
>> Hi George. Thanks for the tip about using system events - I had wasted a lot
>> of time trying to figure out what was going on as the user is not notified
>> at all.
>> Can we please disable the iptv class support for the external changer, or at
>> least warn the user that having one specified means myth won't connect to
>> the socket (since it won't tune the channel).
> IPTV channel changer addition was added so some people could use their
> own IPTV services as it requires special tuning sequences.
> So the idea is not to remove that feature; it's not a bug
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-dev

Are you referring to tickets #10879 or #11365 - because those don't 
refer to mythtv 0.27, and in 0.26 with an external tuner script my 
backend still  connected to the iptv source.

I image I am one of those people you refer to as I did previously use a 
channel changer but now call it with system events rather than the 
'external changer' as suggested on this list - please see 

When an external tuner is specified in 0.27 mythbackend no longer 
connects to the network socket so in what situation can it actually be 
used with iptv?

That aside, can we have a statement in the log to at least explain that 
the reason mythbackend is not connecting to the network socket is 
because an external tuner has been specified?
Without this users end up with no way of diagnosing why its not 
connecting to the iptv source and it is difficult to diagnose.
For example, I had this issue at the start of October I posted 
mythavtest and mythbackend logs to mythtv-users and nobody identified 
that it was due to the channel changer.


More information about the mythtv-dev mailing list