[mythtv-users] Data Direct Error, Rogers Cable Toronto or Internal Mythtv Table Error???

Jim O'Neill oneillji at gmail.com
Sat Aug 19 01:52:31 UTC 2006


R. G. Newbury wrote:
> Jim O'Neill wrote:
>   
>> R. G. Newbury wrote:
>>     
>>> I'm getting an error with recordings which at first glance looks like it 
>>> might originate with the Data Direct data. But that makes no sense.
>>> This is analog cable recorded using a PVR-500.
>>> Here is the channel table data:
>>>       
> <SNIP>>>
>   
>>> mysql> select * from channel where channum = '17' or channum = '61';
>>> +--------+---------+--------+----------+----------+------+------+----------+--------------+---------+-------------+----------+------------+--------+-------+----------+----------+---------+---------------+---------------+---------+-----------+-----------+----------+-----------------+-----------------+
>>> | chanid | channum | freqid | sourceid | callsign | name | icon | 
>>> finetune | videofilters | xmltvid | recpriority | contrast | brightness 
>>> | colour | hue   | tvformat | commfree | visible | outputfilters | 
>>> useonairguide | mplexid | serviceid | atscsrcid | tmoffset | 
>>> atsc_major_chan | atsc_minor_chan |
>>> +--------+---------+--------+----------+----------+------+------+----------+--------------+---------+-------------+----------+------------+--------+-------+----------+----------+---------+---------------+---------------+---------+-----------+-----------+----------+-----------------+-----------------+
>>> |   1017 | 17      | 17     |        1 | WGRZ     | WGRZ | none | 
>>> NULL |              | 11484   |           0 |    32768 |      32768 | 
>>> 32768 | 32768 | Default  |        0 |       1 |               | 
>>>      0 |    NULL |      NULL |      4352 |        0 |              17 | 
>>>                0 |
>>> |   1061 | 61      | 61     |        1 | WNED     | WNED |      | 
>>> NULL |              | 11709   |           0 |    32768 |      32768 | 
>>> 32768 | 32768 | Default  |        0 |       1 |               | 
>>>      0 |   32767 |         0 |     15616 |        0 |              61 | 
>>>                0 |
>>> <SNIP>
>>>       
>
>   
>>> All WAG's gratefully accepted.
>>>
>>> Geoff
>>>   
>>>       
>> Geoff, i doubt i can help but could you confirm something?  Do you have 
>> two capture cards configured in myth as is implied by "if I set 2 
>> simultaneous recordings"?  If yes, shouldn't channel 17 at minimum have 
>> shown up twice as output from your select statement?   Jim
>>     
>
> I have 2 analog tuners in a PVR500 card.
>
> No I would not get channel 17 listed twice. This is the channel table, 
> which lists the information relating to a single channel.
> Each capturecard has certain information, relating to its physical 
> characteristics. One of its characteristics is the sourceid which it 
> receives. Multiple cards can 'see' the same sourceid, but no card should 
> 'see' on a sourceid any channel which it cannot actually receive. 
> Following usual relational database standards, information is only 
> entered once. So I get one listing for channel 17.
>
> SOLVED
> The listing given above was from the copy of the mythconverg database on 
> this computer, my desktop at work. This database was set up as a copy of 
> the one at home, with only the IP address of the mysql server changed. I 
> use this end to download listings and transfer them home on a usb key 
> using a limited mysqldump.
>
> The database at home became corrupted somehow and both the freqid and 
> the  atsc_major_chan entry for channel 61 had '17' as their value. 
> Obviously the freqid id of '17' caused myth to tune to the actual wrong 
> channel, even though all of the other information correctly related to 
> channel 61 and the program I wanted to record. No wonder I was dazed and 
> confused!
>
> So how this happened, I have no idea, but it is now solved.
>
> Geoff
>   
Geoff, i won't belabour this as i only have one tuner and clearly with 
two you would know better.  I had thought that a source could have 
channum with a value and another source could also have a channum with 
the same value and that these are identified uniquely by the chanid 
which is a concatenation of the source and channum fields in most 
cases.  If this were true than you could have two rows with a channum of 
17 or any other number.  Apologies for the noise.   Jim


More information about the mythtv-users mailing list