[mythtv-users] Ideas to diagnose one faulty DVB-T adapter (on a dual adapter USB stick)

[John Pilkington]

On 30/10/12 18:48, Mike Perkins wrote:
> On 30/10/12 18:12, John Pilkington wrote:
>> On 30/10/12 17:19, Dan Gravell wrote:
>>> I first set up my MythTV backend a few months ago. I got it all
>>> working with
>>> one WinTV Duet stick. Both adapters were working at this stage; I
>>> could record
>>> two channels at once.
>>>
>>> Now I've come back to it and it seems like the first adapter does not
>>> work. I
>>> guess Myth defaults to the first as I cannot get a lock in Live TV and
>>> recordings all fail.
>>>
>>> Any ideas to diagnose why one of the tuners on my WinTV Duet works
>>> and the
>>> other doesn't? Scanning the second adapter brings back channels, e.g:
>>>
>>> sudo scan /usr/share/dvb/dvb-t/uk-CrystalPalace -a 1 -o zap
>>>
>>> But scanning the first finds nothing but gives lots of 'WARNING: filter
>>> timeout pid 0x0000' messages:
>>>
>>> gravelld at bordeaux:~$ sudo scan /usr/share/dvb/dvb-t/uk-CrystalPalace
>>> -o zap
>>> scanning /usr/share/dvb/dvb-t/uk-CrystalPalace
>>>
>>> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>> initial transponder 506000000 0 3 9 3 1 0 0
>>> initial transponder 482000000 0 3 9 3 1 0 0
>>> initial transponder 490000000 0 2 9 3 1 0 0
>>> initial transponder 514000000 0 2 9 3 1 0 0
>>> initial transponder 529833000 0 3 9 3 1 0 0
>>>>>> tune to:
>>>>>> 506000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>>>>
>>>>>>
>>> WARNING: filter timeout pid 0x0011
>>> WARNING: filter timeout pid 0x0000
>>> WARNING: filter timeout pid 0x0010
>>>>>> tune to:
>>>>>> 482000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>>>>
>>>>>>
>>> WARNING: filter timeout pid 0x0011
>>> WARNING: filter timeout pid 0x0000
>>> WARNING: filter timeout pid 0x0010
>>>>>> tune to:
>>>>>> 490000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
>>>>>>
>>>>>>
>>> [and so on...]
>>>
>>> Dan
>>
>> Why not use the tools in MythTV?  If you know you should use Crystal
>> Palace it
>> ought to be easy - unless, of course, there *is* something wrong, or
>> Myth won't
>> recognise the device.  There have been lots of posts about this sort
>> of thing.
>> Here' a recent one that should get you going in a few minutes.
>>
>> http://www.gossamer-threads.com/lists/mythtv/users/531976#531976
>>
> Did you even read his problem? How is that supposed to diagnose a dead
> tuner? He can get Crystal Palace perfectly well using tuner 1; for tuner
> 0 he just gets errors.
>

Ok, maybe slightly inappropriate.  If it wasn't helpful I'm sorry. 
People do get into unnecessary difficulties with DVB tuning and the 
choice of tool looked perhaps a little old-school.  Do you have a more 
useful suggestion?

If one section is dead it should perhaps be disabled.  If it has  a 
faulty PID filter, or, more likely, one with a numerically small 
hardware limit, it's unlikely to be fully satisfactory today.  Perhaps 
consult the linuxtv list of devices to see if it does have a known 
hardware limit, quite likely on an oldish device.  I doubt that tools 
would be available to cure the problem, and new near-equivalents aren't 
expensive.

HTH

John P