On Aug 29, richardwoelk at yahoo.ca wrote:
> Hi,
>     I searched the lists and google for about month off and on trying to 
> fix this
> When I upgrade to ivtv 0.7.0 and kernel 2.6.17 the record audio from the 
> 1/8" jack on my pvr-250 is mono.
> it seems to duplicate the right channel to both recorded tracks.
> I hooked up rabbit ears to check, the RF input is stereo

I have almost the identical problem with my PVR-350 (except it is the
left channel being duplicated...). This is the first (only) similar
report I have been able to find, and unfortunately there don't appear to
be any follow-up messages.

Differences: I am running KnoppMyth R5D1, but kernel 2.16.17 as well.
My PVR-150 is working fine, but of course doesn't use all of the same
driver modules.

I will paste below the info I posted to the KnoppMyth forum on Oct 18,
which contains more details.

Any suggestions?  Would re-compiling the kernel with some specific
options be a possible fix? (I'd rather stick with 2.16.17 rather than go
to 2.16.18, as the kernel source is rather large to swallow on dialup...)

Note: I've tried the various "ivtvctl -c [audio|stream_type]=x"
suggestions posted for other sound problems, but they don't help with
this one.

Thanks,
Ken

Message posted Oct 18, 2006 to KnoppMyth forum (at http://mysettopbox.tv):
> About a week after upgrading from R5B7 to R5D1 (which went very 
> smoothly indeed), I discovered that all of the recordings I had made 
> since the upgrade using my PVR350 had a problem with the audio. The 
> BT878 recordings were fine.
>
> Problem description: the PVR350 is recording non-stereo audio which 
> sounds somewhat like the old "simulated stereo" records from the 
> 1960s. Turns out that only the left line-input signal is being used, 
> and it is being recorded to both the left and right channels (probably 
> with a phase shift, generating the "simulated stereo" effect). But 
> recordings from the PVR350's tuner give good stereo; the problem is 
> only when using S-video / line input mode.
>
> I first noticed the problem when replacing my BT878 with a new PVR150. 
> The PVR150 is working great: good stereo audio. (It is also using 
> S-video and line-input audio.)
>
> I've spent a lot of time Google-ing and searching the forums for any 
> information that might relate to this problem, but nothing has turned 
> up that looks related. (Painfully slow process on my dial-up 
> connection...)
>
> Yes, I know about the steps identified in the "CompileIvtv" wiki 
> Howto, and have multiply-checked my config files against this. (Also, 
> the 350 worked fine in R5B7, to which these instructions also apply, I 
> believe.)
>
> Swapping cables between the 150 and 350: the problem remains on the 350.
>
> I've tried re-booting to a backup of R5B7: the PVR350 worked fine 
> again. So, not a hardware or cabling problem.
>
> I've tried re-installing R5D1 as an install (not upgrade). Same problem.
>
> I've tried upgrading the ivtv driver to 0.7.1. Same problem.
>
> I've tried replacing the firmware from R5D1 with that from R5B7. No 
> help. (Actually, it appears that they are the same except for padding 
> according to some posts.)
>
> [Edit 2006Oct19 01:08, ashtonp]: Forgot to mention, stopping 
> mythbackend and using "cat /dev/video0 > test.mpg" gives the same 
> audio problem.
>
> So, now I'm at the point of suspecting a problem with the R5D1 kernel 
> versions of the ivtv support modules (tuner.ko, tda9887.ko, 
> saa7127.ko, msp3400.ko, tveeprom.ko, cx25840/cx25840.ko). From what I 
> have been able to determine, the ivtv versions of these modules have 
> been merged into the 2.6.17 kernel, so ivtv 0.7.x now uses the 
> kernel-provided versions of these modules and no longer generates its 
> own custom variants. (No longer any need to rename the kernel versions 
> *.orig)
>
> From all of my searching, no-one else has reported this problem!!!??? 
> Is the PVR350 working properly for everyone else under R5D1?
>
> Anyone have any ideas? I'm sure I must have missed something simple.
>
> Unless someone can point me to a fix, I think my next step may have to 
> be to upgrade to the 2.6.18 kernel and ivtv 0.8.
>
> --------------------------
>
> For completeness, here is the snippet from the /var/log/messages file 
> regarding the initialization of the PVR350 and PVR150 cards:
>
> Oct 16 17:41:07 avpc kernel: ivtv: ==================== START INIT 
> IVTV ====================
> Oct 16 17:41:07 avpc kernel: ivtv: version 0.7.1 (tagged release) loading
> Oct 16 17:41:07 avpc kernel: ivtv: Linux version: 2.6.17-chw-8 SMP 
> preempt mod_unload 586 gcc-3.4
> Oct 16 17:41:07 avpc kernel: ivtv: In case of problems please include 
> the debug info between
> Oct 16 17:41:07 avpc kernel: ivtv: the START INIT IVTV and END INIT 
> IVTV lines, along with
> Oct 16 17:41:07 avpc kernel: ivtv: any module options, when mailing 
> the ivtv-users mailinglist.
> Oct 16 17:41:07 avpc kernel: ivtv0: Autodetected Hauppauge WinTV 
> PVR-350 card (cx23415 based)
> Oct 16 17:41:07 avpc kernel: ACPI: PCI Interrupt 0000:01:08.0[A] -> 
> Link [APC3] -> GSI 18 (level, high) -> IRQ 17
> Oct 16 17:41:07 avpc kernel: ivtv0: Unreasonably low latency timer, 
> setting to 64 (was 32)
> Oct 16 17:41:07 avpc kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c 
> driver #0)
> Oct 16 17:41:07 avpc kernel: saa7115 2-0021: saa7115 found @ 0x42 
> (ivtv i2c driver #0)
> Oct 16 17:41:07 avpc kernel: saa7127 2-0044: saa7127 found @ 0x88 
> (ivtv i2c driver #0)
> Oct 16 17:41:07 avpc kernel: msp3400 2-0040: MSP4448G-A2 found @ 0x80 
> (ivtv i2c driver #0)
> Oct 16 17:41:07 avpc kernel: msp3400 2-0040: MSP4448G-A2 supports 
> radio, mode is autodetect and autoselect
> Oct 16 17:41:08 avpc kernel: tveeprom 2-0050: Hauppauge model 48132, 
> rev J323, serial# 7113662
> Oct 16 17:41:08 avpc kernel: tveeprom 2-0050: tuner model is Philips 
> FM1236 (idx 23, type 2)
> Oct 16 17:41:08 avpc kernel: tveeprom 2-0050: TV standards NTSC(M) 
> (eeprom 0x08)
> Oct 16 17:41:08 avpc kernel: tveeprom 2-0050: audio processor is 
> MSP4448 (idx 27)
> Oct 16 17:41:08 avpc kernel: tveeprom 2-0050: decoder processor is 
> SAA7115 (idx 19)
> Oct 16 17:41:08 avpc kernel: tveeprom 2-0050: has radio, has IR remote
> Oct 16 17:41:08 avpc kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware 
> (262144 bytes)
> Oct 16 17:41:08 avpc kernel: ivtv0: loaded v4l-cx2341x-dec.fw firmware 
> (262144 bytes)
> Oct 16 17:41:09 avpc kernel: ivtv0: Encoder revision: 0x02050032
> Oct 16 17:41:09 avpc kernel: ivtv0: Decoder revision: 0x02020023
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA encoder MPEG stream: 
> 128 x 32768 buffers (4096KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA encoder YUV stream: 
> 194 x 10800 buffers (2048KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA encoder VBI stream: 
> 120 x 17472 buffers (2048KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA encoder PCM audio 
> stream: 455 x 4608 buffers (2048KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: Create encoder radio stream
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA decoder MPEG stream: 
> 16 x 65536 buffers (1024KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA decoder VBI stream: 
> 512 x 2048 buffers (1024KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: Create decoder VOUT stream
> Oct 16 17:41:09 avpc kernel: ivtv0: Allocate DMA decoder YUV stream: 
> 24 x 43200 buffers (1024KB total)
> Oct 16 17:41:09 avpc kernel: ivtv0: loaded v4l-cx2341x-init.mpg 
> firmware (155648 bytes)
> Oct 16 17:41:09 avpc kernel: tuner 2-0061: type set to 2 (Philips NTSC 
> (FI1236,FM1236 and compatibles))
> Oct 16 17:41:09 avpc kernel: ivtv0: Initialized Hauppauge WinTV 
> PVR-350, card #0
> Oct 16 17:41:09 avpc kernel: ivtv: ====================== NEXT CARD 
> ======================
> Oct 16 17:41:09 avpc kernel: ivtv1: Autodetected Hauppauge WinTV 
> PVR-150 card (cx23416 based)
> Oct 16 17:41:09 avpc kernel: ACPI: PCI Interrupt Link [APC1] enabled 
> at IRQ 16
> Oct 16 17:41:09 avpc kernel: ACPI: PCI Interrupt 0000:01:0a.0[A] -> 
> Link [APC1] -> GSI 16 (level, high) -> IRQ 20
> Oct 16 17:41:09 avpc kernel: ivtv1: Unreasonably low latency timer, 
> setting to 64 (was 32)
> Oct 16 17:41:09 avpc kernel: tuner 3-0061: chip found @ 0xc2 (ivtv i2c 
> driver #1)
> Oct 16 17:41:10 avpc kernel: tda9887 3-0043: chip found @ 0x86 (ivtv 
> i2c driver #1)
> Oct 16 17:41:10 avpc kernel: tveeprom 3-0050: Hauppauge model 26552, 
> rev G168, serial# 8880509
> Oct 16 17:41:10 avpc kernel: tveeprom 3-0050: tuner model is LG TAPE 
> H001F MK3 (idx 68, type 47)
> Oct 16 17:41:10 avpc kernel: tveeprom 3-0050: TV standards NTSC(M) 
> (eeprom 0x08)
> Oct 16 17:41:10 avpc kernel: tveeprom 3-0050: audio processor is 
> CX25843 (idx 37)
> Oct 16 17:41:10 avpc kernel: tveeprom 3-0050: decoder processor is 
> CX25843 (idx 30)
> Oct 16 17:41:10 avpc kernel: tveeprom 3-0050: has radio, has no IR remote
> Oct 16 17:41:10 avpc kernel: cx25840 3-0044: cx25843-23 found @ 0x88 
> (ivtv i2c driver #1)
> Oct 16 17:41:14 avpc kernel: cx25840 3-0044: loaded v4l-cx25840.fw 
> firmware (16382 bytes)
> Oct 16 17:41:14 avpc kernel: wm8775 3-001b: chip found @ 0x36 (ivtv 
> i2c driver #1)
> Oct 16 17:41:15 avpc kernel: ivtv1: loaded v4l-cx2341x-enc.fw firmware 
> (262144 bytes)
> Oct 16 17:41:15 avpc kernel: ivtv1: Encoder revision: 0x02050032
> Oct 16 17:41:15 avpc kernel: ivtv1: Allocate DMA encoder MPEG stream: 
> 128 x 32768 buffers (4096KB total)
> Oct 16 17:41:15 avpc kernel: ivtv1: Allocate DMA encoder YUV stream: 
> 194 x 10800 buffers (2048KB total)
> Oct 16 17:41:15 avpc kernel: ivtv1: Allocate DMA encoder VBI stream: 
> 120 x 17472 buffers (2048KB total)
> Oct 16 17:41:15 avpc kernel: ivtv1: Allocate DMA encoder PCM audio 
> stream: 455 x 4608 buffers (2048KB total)
> Oct 16 17:41:15 avpc kernel: ivtv1: Create encoder radio stream
> Oct 16 17:41:15 avpc kernel: tuner 3-0061: type set to 47 (LG NTSC 
> (TAPE series))
> Oct 16 17:41:15 avpc kernel: ivtv1: Initialized Hauppauge WinTV 
> PVR-150, card #1
> Oct 16 17:41:15 avpc kernel: ivtv: ==================== END INIT IVTV 
> ====================




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

Reply via email to