[mythtv-users] TBS2603 HDMI to Ethernet Questions (IPTV)
stephen_agent at jsw.gen.nz
Wed Dec 12 15:53:24 UTC 2018
On Wed, 12 Dec 2018 09:05:07 -0600, you wrote:
>On 2018-12-12 8:16 a.m., Gerald Brandt wrote:
>> I have a TBS2603, and it seems to be working fine, generating video
>> with good quality.
>> The mythtv IPTV encoder page has scripts for using the encoder with
>> mythtv, but those scripts look fairly complex. They power up and down
>> the cable box, etc. I have a (partially) working system by having only
>> a start recording script that does nothing more than change the
>> channel using 6200ch. Am I missing something? Should it be more
>> complex than what I have in place?
>> I did need a lock file in the start recording script, since mythtv 28
>> seemed to call the script twice, which messed up with channel changing.
>> The problem I am having is with LiveTV. I use Kodi for my frontends,
>> and it gets a channel unavailable a lot with the TBS2603, but not with
>> my HDPVR. Can anyone imagine a reason for this? I'll be testing the
>> mythfrontend today.
>Just upgraded to 29.1, and channel changing/livetv all works fantastic.
>If I go to channel 227, my script gets sent channel 888, which is
>non-existant. What is going on? I pass %CHANID% into the script. It
>looks like %CHANID% is not the actual channel number to change to.
The chanid is an internal index value used by MythTV to index its
database channel table. If you created your channels with a late
enough version of MythTV, it will normally be the same as the channel
number, but that is not guaranteed if you have an old database and
have never deleted all the sources and channels and rescanned them.
And any rescans done later w2ithout a full delete may make some
channels have a different chanid from their channel number. If you
want the channel number (the one you use to go to the channel from the
remote or keyboard in mythfrontend), then you need the channum field.
Which should be available using %CHANNUM%.
Note that while chanid values must be unique, channum values do not.
If you have several ways of receiving the same channel (eg via DVB-T
and DVB-S or via ATSC and cable), the database is often set up so that
they will use the same channel number, and mythbackend can then use
any of those different sources to get that channel. In situations
like that, the first source scanned will likely get matching chanid
and channum, and later sources will have a different chanid for the
More information about the mythtv-users