[pvrusb2] audio pops and cracks in the recordings

Mike Isely isely at isely.net
Tue Jan 23 20:23:10 CST 2007


First, before getting into the responses below, send me the response to 
all this privately; we're not really adding much here to help everyone 
else out.  And if people are interested I promise I'll post a summary 
if/when this problem is understood.


On Mon, 22 Jan 2007, devsk wrote:

> some craziness:
> 
> I don't have tda9887 module anymore in 2.6.19.2 version, but it existed in 2.6.17:
> 
> /lib64/modules/2.6.17-reiser4-r7/kernel/drivers/media/video/tda9887.ko
> 
> Is it not needed anymore? Although I am not sure it was used earlier because I don't a working lsmod from that time. I do see some messages for it though:

A long while back, tda9887 and tuner were separate modules.  In the 
v4l-dvb tree there has been an effort to merge them together.  Right now 
in 2.6.18.1 I still see separate entities attaching to the driver, but 
it's very plausible that the merge is complete now so in 2.6.19.2 you're 
not seeing tda9887 any longer.  That would explain _that_ difference.


> 
> # dmesg|grep tda9887
> tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tda9887 2-0043: Data bytes: b=0x14 c=0x30 e=0x44
> tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tda9887 2-0043: Data bytes: b=0x14 c=0x30 e=0x44
> tda9887 2-0043: Data bytes: b=0x14 c=0x30 e=0x44
> 
> If this module is not present, where are these messages coming from?

It's possible that even though tuner and tda9887 are the same module, 
that different blocks of logic within the module are acting 
independently.  I can dig into the code to find our for certain, but 
honestly I've had far bigger fish to fry lately :-(

Try modprobe -r tuner, then do the "cat ..../debuginfo" command again 
and see if tda9887 messages still appear.  (And of course afterwards 
don't forget to modprobe tuner back into the kernel.)


> 
> Another thing I notice is that I don't see messages similar to the one you posted in another thread:
> 
> Jan 22 23:42:06 londo kernel: [77899.335744] tuner 1-0061: Signal strength: 32768
> Jan 22 23:42:06 londo kernel: [77899.336368] tuner 1-0061: Stereo:          yes
> 
> I see:
> 
> pvrusb2: =================  START STATUS CARD #0  =================
> cx25840 2-0044: Video signal:              present
> cx25840 2-0044: Detected format:           NTSC-M
> cx25840 2-0044: Specified standard:        NTSC-M
> cx25840 2-0044: Specified video input:     Composite 7
> cx25840 2-0044: Specified audioclock freq: 48000 Hz
> cx25840 2-0044: Detected audio mode:       stereo with SAP
> cx25840 2-0044: Detected audio standard:   BTSC
> cx25840 2-0044: Audio muted:               no
> cx25840 2-0044: Audio microcontroller:     running
> cx25840 2-0044: Configured audio standard: automatic detection
> cx25840 2-0044: Configured audio system:   BTSC
> cx25840 2-0044: Specified audio input:     Tuner (In8)
> cx25840 2-0044: Preferred audio mode:      stereo

You have these messages (and I didn't in what I posted) because you are 
running a 24xxx series device.  The output I pasted was from a 29xxx 
series device.  Were I to have posted 24xxx output, it would have looked 
similar to above.  But I didn't at that time because I was trying to 
match up with what Rick was seeing (he has a 29xxx device).

I remember you said you had experimented with different cx25840 firmware 
files.  Is that correct?  Can you send me md5sum values for each so I 
can verify we're comparing the same firmware?


> tda9887 2-0043: Data bytes: b=0x14 c=0x30 e=0x44
> tuner 2-0061: Tuner mode:      analog TV
> tuner 2-0061: Frequency:       55.25 MHz
> tuner 2-0061: Standard:        0x0000b000

I suspect this might be due to module differences or possibly that your 
device is using a slightly different tuner type (Hauppauge likes 
changing out the "tin can" inside the device without warning).


> wm8775 2-001b: Input: 2
> pvrusb2: cx2341x config:
> pvrusb2: Stream: MPEG-2 Program Stream
> pvrusb2: VBI Format: No VBI
> pvrusb2: Video:  720x480, 30 fps
> pvrusb2: Video:  MPEG-2, 4x3, Variable Bitrate, 6000000, Peak 8000000
> pvrusb2: Video:  GOP Size 12, 2 B-Frames, GOP Closure, No 3:2 Pulldown
> pvrusb2: Audio:  48 kHz, Layer II, 224 kbps, Stereo, No Emphasis, No CRC
> pvrusb2: Spatial Filter:  Manual, Luma 1D Horizontal, Chroma 1D Horizontal, 0
> pvrusb2: Temporal Filter: Manual, 8
> pvrusb2: Median Filter:   Off, Luma [0, 255], Chroma [0, 255]
> pvrusb2: ==================  END STATUS CARD #0  ==================
> 
> Does it look clean?

Yes, this does look clean.  I will run my 24xxx device again and compare 
the output just to be sure, as soon as I get a chance (which may be 
another day away).

  -Mike


-- 
                        |         Mike Isely          |     PGP fingerprint
     Spammers Die!!     |                             | 03 54 43 4D 75 E5 CC 92
                        |   isely @ pobox (dot) com   | 71 16 01 E2 B5 F5 C1 E8
                        |                             |


More information about the pvrusb2 mailing list