[mythtv-users] Problems tuning a specific channel (but works in Windows)

[Damien Dusha]

Hello all,
 
I am struggling setting up MythTV, 0.19, installed from source.   I have
been limping along, and have a basic setup, getting **most** of the
channels.
(more info below)
 
Location:
Brisbane (Clayfield), Queensland Australia.
 
The important bits:
[root at localhost ~]# uname -r
2.6.17-1.2139_FC5
 
Hardware: 
DVICO Dual DVB-T Tuner card,
P4-4.2GHz, 
Nvidia 6200 graphics with proprietary drivers.
 
I can get most of the channels, and it seems like I am in a good signal
area:
 
I am getting good signal with most channels, except for channel 9.  For
example, with the ABC, I get:
 
[root at localhost ~]# tzap -a  0 "ABC HDTV"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 226500000 Hz
video pid 0x0904, audio pid 0x0000
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 1f | signal 0000 | snr fafa | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr fafa | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr fcfc | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr fcfc | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr fafa | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
 
However, Channel 9 seems to be no good:
 
[root at localhost ~]# tzap -a  0 "Nine High Definition"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 191625000 Hz
video pid 0x0200, audio pid 0x0000
status 00 | signal 0000 | snr 7c7c | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 5353 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 4b4b | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 4e4e | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 4d4d | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 1f1f | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 2626 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 2c2c | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr e2e2 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr e2e2 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr e2e2 | ber 00000000 | unc 00000000 | 
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 0000 | snr e4e4 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 07 | signal 0000 | snr e4e4 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr e2e2 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 07 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 05 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 05 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 | 
 
In desperation, I have even tried a separate Windows install, with the
supplied drivers.  Channel 9 (the one above having problems) performs
flawlessly, with the software reporting:
Channel 8 [which is the RF channel for "Channel 9], 31.8dB, 100% signal.
 
Channel 9 is NOT auto-detected by MythTV, and I am using the channels.conf
file supplied by Chris Pascoe
(http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/)
 
As you can see, it appears to briefly lock on above.   I have no idea what
is going on.  Does anyone else?
 
Cheers
Damien.
 
p.s And a side note, HDTV appears jerky, like it is dropping every second
frame.  SDTV is perfect. I am using the graphics card, and have about a 40%
CPU load when operating.  For reference, HDTV on windows is flawless, and
operates at 30% CPU usage, and presumably uses the graphics card in the
background.  Feel free to start another thread/comment/email on this.
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20060716/74dbc2ef/attachment-0001.htm