I had this issue with a PVR500 (With Samsung Tuners) on version 4.X of 
the IVTV driver. I'm currently running version 1.0.0 on a stock Ubuntu 
kernel (2.6.22-14-generic). I've only run it for a day so far, but I 
haven't encountered the issue since then.

One thing that would >always< fix this issue for me was running 
"/usr/local/bin/ivtvctl -d /dev/video1 -q 0" (Assuming Tuner 1 was 
recording). I eventually ended up writing a script that would run this 
command for the tuner about 5 seconds after the program started working. 
You might try it and see if it will fix your issue every time.

Jonathan

Michael Ellis wrote:
> Hi Karl.
>
> For what it's worth, I have a PVR500 and I have been fighting this  
> problem for over 18 months.
>
> I keep reading that cards with the Samsung tuners have all kinds of  
> problems, but I am fortunate enough to have the Phillips tuners in  
> mine.  Despite, that, I keep encountering the issue.
>
> I tried the 0.10.x drivers, but I was unable to get them working  
> properly with 2.6.22r5 (I was only able to get unintelligible static  
> with that combination).   In the end, I had the best luck with:
> 1) kernel = 2.6.16r13 (gentoo)
> 2) ivtv = 0.6.7
> That said, I still get the static from time to time.  I've had a bunch  
> of theories about what brings it on (PVR500 overheating, unamplified  
> cable signal,  old kernel, old drivers, etc.) but I have yet to find  
> the answer.  I have noticed that, for me, this problem seems to occur  
> more frequently on the lower channels (US-cable 7-10) vs. higher  
> ones.  Still, I have seen this on the higher channels now and then.
>
> One thing we have in common is that a PVR500 (my card) is essentially  
> two PVR150s (your cards).  Also worth mentioning is my other hardware:
> 1) CPU = AMD Sempron (AMD64) @ 1GHz
> 2) RAM = 1GB
> 3) Chipset = nVidia nForce (disabled onboard GPU = nVidia 6100)
> 4) Active Video Card = nVidia 6200 (64MB, PCI Express 16x)
>
> And here's the obligatory dmesg output:
>
> Linux video capture interface: v1.00
> ivtv:  ==================== START INIT IVTV ====================
> ivtv:  version 0.6.7 (tagged release) loading
> ivtv:  Linux version: 2.6.16-gentoo-r13 SMP gcc-3.4
> ivtv:  In case of problems please include the debug info between
> ivtv:  the START INIT IVTV and END INIT IVTV lines, along with
> ivtv:  any module options, when mailing the ivtv-users mailinglist.
> ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
> ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> GSI 20 sharing vector 0x32 and IRQ 20
> ACPI: PCI Interrupt 0000:05:08.0[A] -> Link [APC1] -> GSI 16 (level,  
> low) -> IRQ 50
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tveeprom 0-0050: Hauppauge model 23552, rev E587, serial# 8382698
> tveeprom 0-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
> tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx  
> 101, type 62)
> tveeprom 0-0050: audio processor is CX25843 (idx 37)
> tveeprom 0-0050: decoder processor is CX25843 (idx 30)
> tveeprom 0-0050: has radio, has no IR remote
> ivtv0: This is the first unit of a PVR500
> tuner 0-0060: TEA5767 detected.
> tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio)
> tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv0: Encoder revision: 0x02060039
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB  
> total)
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB  
> total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB  
> total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers  
> (2048KB total)
> ivtv0: Create encoder radio stream
> tuner 0-0061: type set to 70 (Samsung TCPN 2121P30A)
> ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
> ivtv:  ======================  NEXT CARD  ======================
> ivtv1: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
> ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
> GSI 21 sharing vector 0x3A and IRQ 21
> ACPI: PCI Interrupt 0000:05:09.0[A] -> Link [APC2] -> GSI 17 (level,  
> low) -> IRQ 58
> ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
> cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
> tveeprom 1-0050: Hauppauge model 23552, rev E587, serial# 8382698
> tveeprom 1-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 70)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx  
> 101, type 62)
> tveeprom 1-0050: audio processor is CX25843 (idx 37)
> tveeprom 1-0050: decoder processor is CX25843 (idx 30)
> tveeprom 1-0050: has radio, has no IR remote
> ivtv1: This is the second unit of a PVR500
> ivtv1: Correcting tveeprom data: no radio present on second unit
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv1: Encoder revision: 0x02060039
> ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB  
> total)
> ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB  
> total)
> ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB  
> total)
> ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers  
> (2048KB total)
> tuner 1-0061: type set to 70 (Samsung TCPN 2121P30A)
> ivtv1: Initialized WinTV PVR 500 (unit #2), card #1
> ivtv:  ====================  END INIT IVTV  ====================
>
>
>
> On Feb 3, 2008, at 6:00 AM, [EMAIL PROTECTED] wrote:
>
>   
>> Message: 3
>> Date: Sat, 02 Feb 2008 16:00:53 -0500
>> From: Karl Grindley <[EMAIL PROTECTED]>
>> Subject: [ivtv-users] Tinny audio on  0.10.6 with pvr150s
>> To: User discussion about IVTV <[email protected]>
>> Message-ID: <[EMAIL PROTECTED]>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>> Greetings,
>>
>> I've got two pvr150s and a pvr350 all running on 2.6.18 with 0.10.6.
>> Tinny audio occasionally occurs with about 20% of recordings.  Does
>> anyone have any suggestions?
>>
>> Thanks,
>> Karl
>>     
>
> =========================
> Michael F. Ellis
> President
> Ellis Softworks Inc.
> ----------
> Phone:  (941) 713-0361
> Email: [EMAIL PROTECTED]
> Web: http://www.ellissoftworks.com
>
>
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>   


_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to