[mythtvnz] Python error in mhegepgsnoop

[Stephen Worthington]

On Sat, 23 May 2015 23:18:57 +1200, you wrote:

>On 23/05/15 22:28, Robin Gilks wrote:
>>> Well it was such a crap weather day today I decided to rip into it. I
>>> have uploaded version 0.6.1 to sourceforge. I believe I have fixed the
>>> bugs with cleaning titles and tuning but I have not done a lot of
>>> testing. I also added a '-T' option as an alternative to the '-t' tuning
>>> option. Use '-T <chanid>' to tune to a channel id instead of channel
>>> number. For example '-T 1003' would tune my system to channel 3 (TV3).
>>> Hope this works for you.
>> Hi David
>>
>> Thanks for the fixes, I'll test them when the crap weather gets here
>> tomorrow!! Not sure where the channel ID comes from - 1003 seems a pretty
>> obscure number to be sure. I would have expected either a frequency or
>> channel number of the multiplex i.e. for the Sugar Loaf in Christchurch
>> either one of
>> 562000000, 578000000 or 594000000
>> or
>> 32, 34 or 36
>>
>> Individual stations (eg. TV3) don't really enter into it do they?
>>
>> Like I say, I'll get into it tomorrow as I have to switch all the aerials
>> over from the old PC to the new one whilst I fiddle and I'm trying not to
>> miss any scheduled programs!
>>
>> Cheers
>>
>The chanid is created automatically by mythtv I believe. I think it's 
>arbitrary, i.e., you could choose any number so long as it's unique. You 
>could tune by the frequency in the dtv_multiplex table but the original 
>idea was to use a number the user could easily remember. There is a 
>mplexid field in the dtv_multiplex table but again how do you know what 
>frequency it means unless you look in the table? So, yes, you are right 
>that it's the RF frequency that matters, not the individual channel, but 
>how easy is it remember xxx MHz vs channel number x for the average person?

Yes, the chanid is just an arbitrary number that is automatically
created to use as a unique identifier for one row in the channel
table.  So 1003 is probably the third row created in the channel
table, since chanid values seem to start from 1001.  I normally
manually create my channel table entries for new or changed channels,
so my chanid values usually have some useful information in them (I
use 4xxx for my Sky DVB-S channels and 1xxx for my Freeview DVB-T
ones).  The uniqueness of the chanid values is required for the
database to work.  If you are messing around with them, make very sure
not to duplicate chanid values.  They are not normally visible to
MythTV users, except in log files and the filenames of recordings -
they are intended for internal use only and are used in other tables
to reference the channel table.