[mythtv-users] Static on all channels -- PVR-350

[Michael T. Dean]

On 07/23/06 19:28, Marc Barrett wrote:

>On Sun Jul 23 22:51:46 UTC 2006  Michael T. Dean wrote:
>
>>On 07/23/2006 04:12 PM, Marc Barrett wrote:
>>    
>>
>>>I can't get anything but static on all the channels.
>>>I don't totally understand the various frequency table options in the mythtv-setup utility.  There is >us-cable, us-cable-irc, and us-cable-hrc. ... I do know that I used us-cable-hrc under KnoppMyth, and it >worked, and also had to use us-cable-hrc to get a Windows application to work. 
>>>      
>>>
>>use us-cable-hrc
>>    
>>
>>>ivtv0: Autodetected Hauppauge WinTV PVR-350 card (cx23415 based)
>>>
>>>  
>>>ivtv0: Failed to load module saa7115
>>>ivtv0: Failed to load module saa7127
>>>
>>Bad install of ivtv.
>>    
>>
>
>   Those saa modules aren't even used by a PVR-350.  They're for AGP graphics cards. 
>  
>

Funny how my PVR-350 uses both of them...

Jul 23 00:32:14 miranda kernel: ivtv: Autodetected WinTV PVR 350 card
...
Jul 23 00:32:15 miranda kernel: i2c-core.o: driver saa7115 registered.
Jul 23 00:32:15 miranda kernel: saa7115: starting probe for adapter ivtv 
i2c driver #0 (0x10005)
Jul 23 00:32:15 miranda kernel: saa7115: detecting saa7115 client on 
address 0x42
Jul 23 00:32:15 miranda kernel: saa7115: writing init values
Jul 23 00:32:15 miranda kernel: ivtv: i2c attach [client=saa7115[0],ok]
Jul 23 00:32:15 miranda kernel: i2c-core.o: client [saa7115[0]] 
registered to adapter [ivtv i2c driver #0](pos. 2).
Jul 23 00:32:15 miranda kernel: saa7115: status: (1E) 0x48, (1F) 0xc0
Jul 23 00:32:15 miranda kernel: saa7127: video encoder driver version V 
0.3 loaded
Jul 23 00:32:15 miranda kernel: i2c-core.o: driver saa7127 registered.
Jul 23 00:32:15 miranda kernel: saa7127: detecting saa7127 client on 
address 0x88
Jul 23 00:32:15 miranda kernel: saa7127: Selecting NTSC video Standard
Jul 23 00:32:15 miranda kernel: saa7127: Selecting S-Video+Composite
Jul 23 00:32:15 miranda kernel: saa7127: Turn WSS off
Jul 23 00:32:15 miranda kernel: saa7127: Widescreen Mode 4:3 Full Format
Jul 23 00:32:15 miranda kernel: saa7127: Selecting Normal Encoder Input
Jul 23 00:32:15 miranda kernel: saa7127: Enable Video Output
Jul 23 00:32:15 miranda kernel: ivtv: i2c attach [client=saa7127[0],ok]
Jul 23 00:32:15 miranda kernel: i2c-core.o: client [saa7127[0]] 
registered to adapter [ivtv i2c driver #0](pos. 3).
...
Jul 23 00:32:16 miranda kernel: saa7115: decoder set input (4)
Jul 23 00:32:16 miranda kernel: saa7115: now setting Composite input
...
Jul 23 00:32:17 miranda kernel: saa7115: decoder set norm NTSC
Jul 23 00:32:17 miranda kernel: saa7115: set audio: 0x01
Jul 23 00:32:17 miranda kernel: saa7127: Setting Encoder Video Standard
Jul 23 00:32:17 miranda kernel: saa7127: Set NTSC Video Mode
Jul 23 00:32:17 miranda kernel: saa7127: Selecting NTSC video Standard
Jul 23 00:32:17 miranda kernel: ivtv: Initialized WinTV PVR 350, card #0

And my logs don't say, "Failed to load module ..."

>   I think I've found my problem.  Here's what I did: I picked a channel that I like (History Channel, #60 on my cable), and found the HRC frequency by going to www.jneuhaus.com/fccindex/cablech.html.  I took the frequency, multiplied by 16, which go me 7008.  I then did this:
>
>ivtvctl -r 7008; DISPLAY=":0.0" mplayer /dev/video0
>
>   This worked fine -- I got to see the channel played in mplayer.  This proves my ivtv driver is installed fine.
>
>   I think the problem is with the frequency table data being supplied by DataDirect.  But I really have no idea where that data is stored and how to check it.  I hope someone can help?
>

MythTV provides the frequency tables, DataDirect provides the channel 
number (which is stored as a freqid in MythTV).  The MythTV frequency 
table is not exact (as Daniel and I are currently discussing in the 
thread http://www.gossamer-threads.com/lists/mythtv/dev/214338#214338 ), 
but for channel 60 (ntsc_hrc), for example, the value Myth provies is 
off by 21.9kHz (we have 438000kHz and the exact value is 438021.9kHz).  
The tuner module used by the PVR-350 uses "tuner steps" of 1MHz/16 = 
62.5kHz.  Therefore, the frequency Myth uses corresponds to 7008 "tuner 
steps" and the exact frequency corresponds to 7008 steps (once you've 
truncated--since it must be an integer value).

Therefore, it's not the frequency tables.  It's possible that the 
frequency ID's you have are incorrect (possibly because of an issue 
that's recently surfaced regarding DataDirect's reporting of channel 
numbers).  However, I still maintain that you need to fix your ivtv 
modules...

Mike