Mailing List Archive: PVR-150 Tinny audio

PVR-150 Tinny audio

Mar 2, 2006, 9:03 PM

Post #1 of 20 (10485 views)

Hello,
I wanted to post that I am also having the tinny audio as mentioned on the
development list. I want to try to get this fixed or figure out a good work around
idea. Let me know what I can do to help remedy this. Here is my relevant information.
I am using the packages as installed by yum from atrpms. It seems to be hit or miss
as to whether the audio will be tinny.

Thanks,
Gil

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.3 (tagged release) loading
ivtv: Linux version: 2.6.15-1.1831_FC4 686 REGPARM 4KSTACKS gcc-4.0
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 WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tveeprom 2-0050: Hauppauge model 26032, rev C199, serial# 7936570
tveeprom 2-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 2-0050: audio processor is CX25841 (idx 35)
tveeprom 2-0050: decoder processor is CX25841 (idx 28)
tveeprom 2-0050: has no radio, has IR remote
cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 2-0044: loaded v4l-cx25840.fw firmware (13353 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02040024
ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011 or 0x02050032.
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)
tuner 2-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================

[root@mythserver ~]# lsmod
Module Size Used by
parport_pc 27909 1
lp 12937 0
parport 35593 2 parport_pc,lp
autofs4 19653 1
rfcomm 37461 0
l2cap 25153 5 rfcomm
bluetooth 47781 4 rfcomm,l2cap
sunrpc 146045 1
xfs 549257 1
exportfs 6337 1 xfs
dm_mod 57177 0
video 16197 0
button 6737 0
battery 9541 0
ac 4933 0
nvidia 3694120 12
ipv6 252577 18
uhci_hcd 32721 0
ehci_hcd 33485 0
tda9887 15953 0
wm8775 5965 0
cx25840 23633 0
ivtv 205972 0
bt878 10553 0
tuner 43505 0
tvaudio 23517 0
bttv 168881 1 bt878
video_buf 21957 1 bttv
i2c_algo_bit 9289 2 ivtv,bttv
v4l2_common 5953 1 bttv
btcx_risc 5065 1 bttv
tveeprom 15057 1 bttv
videodev 9665 2 ivtv,bttv
i2c_viapro 9045 0
i2c_core 21697 10
tda9887,wm8775,cx25840,ivtv,tuner,tvaudio,bttv,i2c_algo_bit,tveeprom,i2c_viapro
snd_via82xx 25112 1
gameport 15689 1 snd_via82xx
snd_ac97_codec 86944 1 snd_via82xx
snd_ac97_bus 2048 1 snd_ac97_codec
snd_seq_dummy 3204 0
snd_seq_oss 31488 0
snd_seq_midi_event 6528 1 snd_seq_oss
snd_seq 46864 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss 47776 0
snd_mixer_oss 16768 1 snd_pcm_oss
snd_pcm 83204 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss
snd_timer 22148 2 snd_seq,snd_pcm
snd_page_alloc 8584 2 snd_via82xx,snd_pcm
snd_mpu401_uart 6656 1 snd_via82xx
snd_rawmidi 22176 1 snd_mpu401_uart
snd_seq_device 8332 4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
snd 49892 14
snd_via82xx,snd_ac97_codec,snd_seq_dummy,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_os
s,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore 9889 1 snd
r8169 28745 0
via_rhine 24133 0
mii 5697 1 via_rhine
floppy 62085 0
ext3 129993 2
jbd 57941 1 ext3

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

ggmorton at pobox

Mar 7, 2006, 8:18 PM

Post #2 of 20 (10298 views)

Permalink

-----Original Message-----
From: ivtv-users-bounces@ivtvdriver.org [mailto:ivtv-users-bounces@ivtvdriver.org] On
Behalf Of Gilbert Morton
Sent: Thursday, March 02, 2006 11:03 PM
To: ivtv-users@ivtvdriver.org
Subject: [ivtv-users] PVR-150 Tinny audio

Hello,
I wanted to post that I am also having the tinny audio as mentioned on the
development list. I want to try to get this fixed or figure out a good work around
idea. Let me know what I can do to help remedy this. Here is my relevant information.
I am using the packages as installed by yum from atrpms. It seems to be hit or miss
as to whether the audio will be tinny.

Thanks,
Gil

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.3 (tagged release) loading
ivtv: Linux version: 2.6.15-1.1831_FC4 686 REGPARM 4KSTACKS gcc-4.0
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 WinTV PVR 150 card (cx23416 based)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
tveeprom 2-0050: Hauppauge model 26032, rev C199, serial# 7936570
tveeprom 2-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 2-0050: audio processor is CX25841 (idx 35)
tveeprom 2-0050: decoder processor is CX25841 (idx 28)
tveeprom 2-0050: has no radio, has IR remote
cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 2-0044: loaded v4l-cx25840.fw firmware (13353 bytes)
ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02040024
ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011 or 0x02050032.
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)
tuner 2-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================

Any ideas on this problem? Is anyone else having this problem?

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

mclark4386 at charter

Mar 9, 2006, 5:00 AM

Post #3 of 20 (10291 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gilbert Morton wrote:
>
> -----Original Message-----
> From: ivtv-users-bounces@ivtvdriver.org [mailto:ivtv-users-bounces@ivtvdriver.org] On
> Behalf Of Gilbert Morton
> Sent: Thursday, March 02, 2006 11:03 PM
> To: ivtv-users@ivtvdriver.org
> Subject: [ivtv-users] PVR-150 Tinny audio
>
> Hello,
> I wanted to post that I am also having the tinny audio as mentioned on the
> development list. I want to try to get this fixed or figure out a good work around
> idea. Let me know what I can do to help remedy this. Here is my relevant information.
> I am using the packages as installed by yum from atrpms. It seems to be hit or miss
> as to whether the audio will be tinny.
>
> Thanks,
> Gil
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.4.3 (tagged release) loading
> ivtv: Linux version: 2.6.15-1.1831_FC4 686 REGPARM 4KSTACKS gcc-4.0
> 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 WinTV PVR 150 card (cx23416 based)
> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
> PCI: setting IRQ 5 as level-triggered
> ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
> tveeprom 2-0050: Hauppauge model 26032, rev C199, serial# 7936570
> tveeprom 2-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
> tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 2-0050: audio processor is CX25841 (idx 35)
> tveeprom 2-0050: decoder processor is CX25841 (idx 28)
> tveeprom 2-0050: has no radio, has IR remote
> cx25840 2-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 2-0044: loaded v4l-cx25840.fw firmware (13353 bytes)
> ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
> wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02040024
> ivtv0 warning: Encoder Firmware can be buggy, use version 0x02040011 or 0x02050032.
> 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)
> tuner 2-0061: type set to 50 (TCL 2002N)
> ivtv0: Initialized WinTV PVR 150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
>
> Any ideas on this problem? Is anyone else having this problem?
>
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
ivtvctl -cstream_type=2 to change the stream type to MPEG always works
for me when this happens... if it works and then you have the same
problem after a reboot you may want to add it to your local.start
- -Matt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEECbT0ybjZxByS4URAleUAJ0WswibxoUwgf1flzLtXanJyNKL4wCgpVg+
pPWcAFAeIjT518msJ4cmPc0=
=HuyD
-----END PGP SIGNATURE-----

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

ivtv at webhounds

Mar 10, 2006, 12:52 PM

Post #4 of 20 (10300 views)

Permalink

>
ivtvctl -cstream_type=2 to change the stream type to MPEG always works for
me when this happens... if it works and then you have the same problem after
a reboot you may want to add it to your local.start
- -Matt

I have the same problem with tinny audio but only on my 250, the
350 is just fine. The funny thing is if you check the settings:

ivtvctl -d /dev/video1 -Q

ioctl VIDIOC_G_AUDIO ok
Audio input = 1: Audio Line 1

Then issue this command:

ivtvctl -d /dev/video1 -q 1

The audio gets fixed.
I also tried your suggestion, and it fixed the audio as well.

The problem is the fix doesn't remain if I switch tuners or
exit out of live TV and then re-enter. I have to enter the
command each time for the fix.

Scott

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

johnbiundo at sbcglobal

Mar 13, 2006, 2:00 PM

Post #5 of 20 (10290 views)

Permalink

> ivtvctl -cstream_type=2
>
> ivtvctl -d /dev/video1 -q 1
>

I'm having the same problem with a pvr-150. This only happened after I
added a second pvr-150 to my system.

Both of the above ivtvctl commands *often* fix the problem (actually I
use -q 0, not -q 1). As someone else noted, though, the fix is only
temporary, and it doesn't work 100% of the time.

Another (possibly bigger) complication is that sometimes, if the audio
is good, issuing either of these commands will trigger the tinny audio.
This is too bad because it prevents me from invoking a simple script
on each channel change (or just brute forcing running it in a cron job
every 5 seconds or so). The big issue, for me, is recording things on
this troublesome card in Mythtv, then not finding out that the audio is
bad until later when we watch the recorded show.

So I'm wondering if anyone has found a way to detect the tinny audio
problem without actually having to listen to it? If there was something
I could query that would indicate that the audio is in this bad state,
then I could just issue the ivtvctl commands and test to see if it was
fixed.

Grasping at straws, and hoping someone else has some ideas!

Cheers,
john

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

keehan.dowd at shaw

Mar 14, 2006, 4:02 PM

Post #6 of 20 (10259 views)

Permalink

> Date: Thu, 09 Mar 2006 07:00:03 -0600
> From: Matthew Clark <mclark4386@charter.net>
> Subject: Re: [ivtv-users] PVR-150 Tinny audio
> To: ggmorton@pobox.com, User discussion about IVTV
> <ivtv-users@ivtvdriver.org>
> Message-ID: <441026D3.8050306@charter.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Gilbert Morton wrote:
> >> -----Original Message-----
> >> From: ivtv-users-bounces@ivtvdriver.org
> [mailto:ivtv-users-bounces@ivtvdriver.org] On
> >> Behalf Of Gilbert Morton
> >> Sent: Thursday, March 02, 2006 11:03 PM
> >> To: ivtv-users@ivtvdriver.org
> >> Subject: [ivtv-users] PVR-150 Tinny audio
> >>
> >> Hello,
> >> I wanted to post that I am also having the tinny audio as mentioned
> on the
> >> development list. I want to try to get this fixed or figure out a
> good work around
> >> idea. Let me know what I can do to help remedy this. Here is my
> relevant information.
> >> I am using the packages as installed by yum from atrpms. It seems
> to be hit or miss
> >> as to whether the audio will be tinny.
> >>
> >> Thanks,
> >> Gil
<SNIP>
> ivtvctl -cstream_type=2 to change the stream type to MPEG always works
> for me when this happens... if it works and then you have the same
> problem after a reboot you may want to add it to your local.start
> -Matt
>
> ------------------------------

Hello,
I don't know if this will be of any help to other sufferers of the
PVR-150 tinny audio problem, but I was also having the same problem. My
initial ivtv installation was 0.4.3, but I found that dropping back to
0.4.0 solved my tinny audio problem for good. I've been running for
almost two weeks now and have not had the problem since.

Regards to all.

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

ivtv at webhounds

Mar 14, 2006, 8:59 PM

Post #7 of 20 (10257 views)

Permalink

-----------------
>
> Hello,
> I don't know if this will be of any help to other sufferers
> of the PVR-150 tinny audio problem, but I was also having the
> same problem. My initial ivtv installation was 0.4.3, but I
> found that dropping back to 0.4.0 solved my tinny audio
> problem for good. I've been running for almost two weeks now
> and have not had the problem since.
>

Worked for me!

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

ivtv at webhounds

Mar 14, 2006, 9:35 PM

Post #8 of 20 (10275 views)

Permalink

> > Hello,
> > I don't know if this will be of any help to other sufferers of the
> > PVR-150 tinny audio problem, but I was also having the same
> problem.
> > My initial ivtv installation was 0.4.3, but I found that
> dropping back
> > to 0.4.0 solved my tinny audio problem for good. I've been running
> > for almost two weeks now and have not had the problem since.
> >
>
> Worked for me!
>
>

Replying to myself. While doing some more work on my system I noticed
I used ivtv-0.4.1 and not 0.4.0.

Just FYI, but my bad audio on 2nd tuner is gone.

Scott

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

johnbiundo at sbcglobal

Mar 15, 2006, 4:32 PM

Post #9 of 20 (10263 views)

Permalink

Keehan Dowd wrote:
>
> Hello,
> I don't know if this will be of any help to other sufferers of the
> PVR-150 tinny audio problem, but I was also having the same problem. My
> initial ivtv installation was 0.4.3, but I found that dropping back to
> 0.4.0 solved my tinny audio problem for good. I've been running for
> almost two weeks now and have not had the problem since.

Interesting. I'm running 0.4.2 and have the tinny audio problem.
Someone else reported dropping back to 0.4.1 and solving the problem.

Has anyone else had the problem with 0.4.2?

How about 0.4.1 or earlier?

This might indicate a problem from a change introduced between 0.4.1 and
0.4.2.

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: [ivtv-devel] PVR-150 Tinny audio [ In reply to ]

johnbiundo at sbcglobal

Mar 15, 2006, 5:07 PM

Post #10 of 20 (10284 views)

Permalink

John Biundo wrote:
> Interesting. I'm running 0.4.2 and have the tinny audio problem.
> Someone else reported dropping back to 0.4.1 and solving the problem.
>
> Has anyone else had the problem with 0.4.2?
>
> How about 0.4.1 or earlier?
>
> This might indicate a problem from a change introduced between 0.4.1 and
> 0.4.2.
>

Nix that theory.

I just downgraded to 0.4.1 and I'm still able to trigger the tinny audio
by issuing ivtctl -q 0.

I run it in a loop, once every 5 seconds. It seems, subjectively, like
0.4.1 might be somewhat less susceptible to triggering a good->bad state
change, but I can still trigger the change (and therefore, I assume that
whatever environmental factor that occassionally produces it while
recording can still trigger it).

I'm unable to downgrade to 0.4.0 to continue testing. I get compile
errors. Is 0.4.0 incompatible with kernel 2.6.15?

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

johnbiundo at sbcglobal

Mar 17, 2006, 10:06 AM

Post #11 of 20 (10270 views)

Permalink

Anyone following the tinny audio thread on this list should probably
also monitor a thread by the same name on the developers list. A few
folks have captured clips with the problem and it might be helpful to
the developers if more people compared these clips to the problems
they're having. It appears there might be more than one "tinny audio"
problem.

Hans is also looking for a system to dial into. I'm going to try to
make mine available, but if there's someone experiencing this problem
who's also network security savvy and is comfortable providing an ssh
login to their box, this might go faster. It'll probably take me a few
days to get comfortable with setting that up.

john

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

ivtv at pierro

Mar 21, 2006, 11:03 PM

Post #12 of 20 (10198 views)

Permalink

On Thu March 16 2006 01:32, John Biundo wrote:
> Keehan Dowd wrote:
> > Hello,
> > I don't know if this will be of any help to other sufferers of the
> > PVR-150 tinny audio problem, but I was also having the same problem. My
[...]
> Interesting. I'm running 0.4.2 and have the tinny audio problem.
> Someone else reported dropping back to 0.4.1 and solving the problem.
>
> Has anyone else had the problem with 0.4.2?

Sure. I have used 0.4.0 and 0.4.1 and 0.4.3, and in both cases there was the
problem, on kernels 2.6.14 and 2.6.15.1

Here is a reply from Hans Verkuil to me on this mailing list:

> Re: [ivtv-users] MCE 150 gargling sound
> (Hans Verkuil, Wed Jan 4 08:02:19 2006)
> It's a known problem (http://ivtvdriver.org/trac/ticket/49). The ticket
> contains a description of a workaround (a small change in the code). I
> simply did not have the time to really look into it but I know it
> always happens after a DMA error: something goes wrong in the recovery
> of that error.

The aforementioned description of a workaround helped the tinny audio, though
you have to pay high CPU usage for that (looks it is going to be a problem to
use 2 cards onj a 1-core system). I did not try this fix on 0.4.3 driver.

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

ivtv at pierro

Mar 21, 2006, 11:08 PM

Post #13 of 20 (10230 views)

Permalink

Replying to myself:
forget it,
I meant to answer to another message about a different audio problem!

On Wed March 22 2006 08:03, Mila Boldareva wrote:

> Sure. I have used 0.4.0 and 0.4.1 and 0.4.3, and in both cases there was
> the problem, on kernels 2.6.14 and 2.6.15.1
>
> Here is a reply from Hans Verkuil to me on this mailing list:
> > Re: [ivtv-users] MCE 150 gargling sound
> > (Hans Verkuil, Wed Jan 4 08:02:19 2006)
> > It's a known problem (http://ivtvdriver.org/trac/ticket/49). The ticket
> > contains a description of a workaround (a small change in the code). I
> > simply did not have the time to really look into it but I know it
> > always happens after a DMA error: something goes wrong in the recovery
> > of that error.
>
> The aforementioned description of a workaround helped the tinny audio,
> though you have to pay high CPU usage for that (looks it is going to be a
> problem to use 2 cards onj a 1-core system). I did not try this fix on
> 0.4.3 driver.
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny audio [ In reply to ]

hverkuil at xs4all

Mar 21, 2006, 11:10 PM

Post #14 of 20 (10216 views)

Permalink

On Wednesday 22 March 2006 08:03, Mila Boldareva wrote:
> On Thu March 16 2006 01:32, John Biundo wrote:
> > Keehan Dowd wrote:
> > > Hello,
> > > I don't know if this will be of any help to other sufferers of
> > > the PVR-150 tinny audio problem, but I was also having the same
> > > problem. My
>
> [...]
>
> > Interesting. I'm running 0.4.2 and have the tinny audio problem.
> > Someone else reported dropping back to 0.4.1 and solving the
> > problem.
> >
> > Has anyone else had the problem with 0.4.2?
>
> Sure. I have used 0.4.0 and 0.4.1 and 0.4.3, and in both cases there
> was the problem, on kernels 2.6.14 and 2.6.15.1
>
> Here is a reply from Hans Verkuil to me on this mailing list:
> > Re: [ivtv-users] MCE 150 gargling sound
> > (Hans Verkuil, Wed Jan 4 08:02:19 2006)
> > It's a known problem (http://ivtvdriver.org/trac/ticket/49). The
> > ticket contains a description of a workaround (a small change in
> > the code). I simply did not have the time to really look into it
> > but I know it always happens after a DMA error: something goes
> > wrong in the recovery of that error.
>
> The aforementioned description of a workaround helped the tinny
> audio, though you have to pay high CPU usage for that (looks it is
> going to be a problem to use 2 cards onj a 1-core system). I did not
> try this fix on 0.4.3 driver.

That ticket addresses a different audio problem. Unrelated to the tinny
audio problem.

Hans

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny Audio [ In reply to ]

martin.dauskardt at gmx

Jan 17, 2010, 3:05 PM

Post #15 of 20 (8738 views)

Permalink

> Then as a second step, if you can normally reliably reproduce the tinny
> audio, look to reduce the delays in this part of the patch:
>
> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/rev/7753cdcebd28#l2.11
>
> I would appreciate it. I was thinking 10 msec for the first msleep()
> and 140 to 100 msec for the second msleep.

no, that's not enough.
We need altogether 300ms (see my test results from 3rd January:
http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14332)

Greets,

Martin

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny Audio [ In reply to ]

awalls at radix

Jan 17, 2010, 3:53 PM

Post #16 of 20 (8732 views)

Permalink

On Mon, 2010-01-18 at 00:05 +0100, Martin Dauskardt wrote:
> > Then as a second step, if you can normally reliably reproduce the tinny
> > audio, look to reduce the delays in this part of the patch:
> >
> > http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/rev/7753cdcebd28#l2.11
> >
> > I would appreciate it. I was thinking 10 msec for the first msleep()
> > and 140 to 100 msec for the second msleep.
>
> no, that's not enough.
> We need altogether 300ms (see my test results from 3rd January:
> http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14332)

Ah excellent work! Thank you!

I didn't get it in my Inbox apparently, otherwise, I would have already
fixed it and asked for it to be pulled. (Not that Mauro has pulled
anything for the past 3 weeks or so until a few days ago).

According to your table the 50 ms/250 ms case works. Is that one OK for
you?

Regards,
Andy

> Greets,
>
> Martin

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny Audio [ In reply to ]

awalls at radix

Jan 17, 2010, 4:02 PM

Post #17 of 20 (8730 views)

Permalink

On Sun, 2010-01-17 at 18:53 -0500, Andy Walls wrote:
> On Mon, 2010-01-18 at 00:05 +0100, Martin Dauskardt wrote:
> > > Then as a second step, if you can normally reliably reproduce the tinny
> > > audio, look to reduce the delays in this part of the patch:
> > >
> > > http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/rev/7753cdcebd28#l2.11
> > >
> > > I would appreciate it. I was thinking 10 msec for the first msleep()
> > > and 140 to 100 msec for the second msleep.
> >
> > no, that's not enough.
> > We need altogether 300ms (see my test results from 3rd January:
> > http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/14332)
>
> Ah excellent work! Thank you!
>
> I didn't get it in my Inbox apparently, otherwise, I would have already
> fixed it and asked for it to be pulled. (Not that Mauro has pulled
> anything for the past 3 weeks or so until a few days ago).
>
> According to your table the 50 ms/250 ms case works. Is that one OK for
> you?

Oh, nevermind, I see you're OK with the 150/150 case. I'll do that.

Regards,
Andy

> Regards,
> Andy
>
> > Greets,
> >
> > Martin
>
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny Audio [ In reply to ]

derek at accesscomm

Jan 18, 2010, 2:31 PM

Post #18 of 20 (8726 views)

Permalink

On Mon, 2010-01-18 at 12:00 +0100, ivtv-users-request@ivtvdriver.org
wrote:
> Message: 1
> Date: Sun, 17 Jan 2010 14:08:36 -0500
> From: Andy Walls <awalls@radix.net>
> To: robert@osburn-sharp.ath.cx, User discussion about IVTV
> <ivtv-users@ivtvdriver.org>
> Subject: Re: [ivtv-users] PVR-150 Tinny Audio
> Message-ID: <1263755316.3067.79.camel@palomino.walls.org>
> Content-Type: text/plain
>
> On Sun, 2010-01-17 at 09:05 +0000, Robert Sharp wrote:
> > I recently upgraded a PC with the PVR-150 to 2.6.31 and am suffering
> > from the return of the tinniness problem. There is an interesting
> > discussion in the dev list but no clear resolution. Can someone explain
> > either when the fix discussed will be available to ordinary users or how
> > we can apply the patch to fix this.
>
> Robert,
>
> I have a fix that Martin is (rightly) not happy with here:
>
> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/
>
> if you could test it out and let me know if it make the problem go away,
> that would be great.

It sounds like this fix is working for people. I'm not intimately
familiar with kernel/ivtv development or the associated schedules -
assuming this fix works, would it make it into a future kernel release?
If so, which one?

Thanks!

Derek

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny Audio [ In reply to ]

awalls at radix

Jan 20, 2010, 5:45 PM

Post #19 of 20 (8709 views)

Permalink

On Wed, 2010-01-20 at 11:53 +0000, Robert Sharp wrote:
> Andy,
>
> Thanks for the help. I have followed your instructions but I cannot load
> the ivtv module. It fails, complaining about:
>
> [252187.201342] ivtv: Unknown symbol ir_codes_hauppauge_new_table
> [252187.204061] ivtv: Unknown symbol ir_codes_rc5_tv_table
> [252187.205281] ivtv: Unknown symbol ir_codes_avermedia_cardbus_table
>
> Any ideas? I have double-checked the installed modules and there are
> none relating to ivtv. Can't see why this should be a problem when the
> vanilla ivtv driver
> installs fine.
>
> Best regards
> Robert

Hi Robert,

First, you may find posting to the list more expedient: others may be
able to help you; and others may benefit from the answer. (For example,
in this particular case I think Devin already knows the answer and could
have helped you sooner if your mail went to the list.)

The latest ivtv module now knows about some bundled remotes with various
cards. For those remotes to "work out of the box", the ivtv driver
needs the remote keypress mapping tables. Those tables are included in
the new version of the ir-common module you should have built and
installed along with the ivtv module. (Maybe I need to fix a Kconfig
file dependency...)

$ find v4l-dvb/linux/ -name "ir*c"
v4l-dvb/linux/drivers/media/IR/ir-keytable.c
v4l-dvb/linux/drivers/media/IR/ir-functions.c
v4l-dvb/linux/drivers/media/IR/ir-sysfs.c
v4l-dvb/linux/drivers/media/IR/ir-keymaps.c
v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c

Note, that Mauro recently shuffled the position of these files in the
source tree to the IR directorty. That means where the ir-*.ko kernel
modules get installed has also moved:

$ find /lib/modules/`uname -r`/ -name "ir*ko"
/lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/video/ir-kbd-i2c.ko
/lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/IR/ir-common.ko
/lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/IR/ir-core.ko
....

So:

1. Did "make" appear to make all the new v4l-dvb modules, including the
ivtv and ir-* modules? Did "make install" appear to install them all?

2. Do you have duplicate ir-common.ko and ir-core.ko modules
under /lib/modules/`uname -r` ? If so move, backup or delete the
duplicates that are not in the IR directory. Are ir-*ko objects in the
IR directory? Did "make install" appear to perform a depmod -a?

If building the latest source modules is too much to deal with, then
please don't knock yourself out. Waiting is always an option; although
maybe not a staisfying one at times. (I don't expect ordinary users and
subscribers to the ivtv-users list to think they need to put herculean
efforts into trying to test bleeding edge code.) The fix will get into
the main v4l-dvb repository soon. Propagation to 2.6.33 may take some
time. Propagation of 2.6.33 to distributions will take more time.
However, the change will eventually make it to the end user that way.

Thanks again.

Regards,
Andy

> Andy Walls wrote:
> > On Sun, 2010-01-17 at 09:05 +0000, Robert Sharp wrote:
> >
> >> I recently upgraded a PC with the PVR-150 to 2.6.31 and am suffering
> >> from the return of the tinniness problem. There is an interesting
> >> discussion in the dev list but no clear resolution. Can someone explain
> >> either when the fix discussed will be available to ordinary users or how
> >> we can apply the patch to fix this.
> >>
> >
> > Robert,
> >
> > I have a fix that Martin is (rightly) not happy with here:
> >
> > http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/
> >
> > if you could test it out and let me know if it make the problem go away,
> > that would be great.
> >
> > Then as a second step, if you can normally reliably reproduce the tinny
> > audio, look to reduce the delays in this part of the patch:
> >
> > http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/rev/7753cdcebd28#l2.11
> >
> > I would appreciate it. I was thinking 10 msec for the first msleep()
> > and 140 to 100 msec for the second msleep.
> >
> > The easiest way to test it is:
> >
> > 1. Download:
> > http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/archive/tip.tar.gz
> >
> > 2. untar
> > 3. Change into the directory and build:
> >
> > cd v4l-dvb-bugfix-blahblah/
> > make
> >
> > 4. Back up your current modules in /linux/`uname -r`/kernel/media
> > if you want to roll back.
> >
> > 5. Then install the modules as root,unload any running modules, and load
> > the new ivtv module:
> >
> > cd v4l-dvb-bugfix-blahblah/
> > make install
> > (kill the mythbackend or anything else that has the devices open)
> > make unload
> > make unload
> > modprobe ivtv
> >
> > And you're ready to test.
> >
> >
> > Thanks,
> > Andy

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR-150 Tinny Audio [ In reply to ]

robert at osburn-sharp

Jan 21, 2010, 6:45 AM

Post #20 of 20 (8681 views)

Permalink

Thanks Andy, and apologies for forgetting conventions.

OK, I got it to work but only after installing 2.6.32-r2 (I was on
2.6.31-r6) so this may have been the problem. Followed your instructions
exactly as before with the new kernel and everything worked first time.
I have run 40 test recordings (1 min long!) and none of them had audio
problems. My first proper recording has also just completed with no
problems. So far, no signs of any other instability issues either.

Incidentally, I then had problems not being able to send commands to my
IR blaster, but that may have had nothing to do with ivtv and just
something in the new kernel. Fixed the problem by compiling the serial
driver as a module, as recommended by LIRC. Strange that it always
worked OK before.

Now I must remember to recompile nvidia...

Andy Walls wrote:
> On Wed, 2010-01-20 at 11:53 +0000, Robert Sharp wrote:
>
>> Andy,
>>
>> Thanks for the help. I have followed your instructions but I cannot load
>> the ivtv module. It fails, complaining about:
>>
>> [252187.201342] ivtv: Unknown symbol ir_codes_hauppauge_new_table
>> [252187.204061] ivtv: Unknown symbol ir_codes_rc5_tv_table
>> [252187.205281] ivtv: Unknown symbol ir_codes_avermedia_cardbus_table
>>
>> Any ideas? I have double-checked the installed modules and there are
>> none relating to ivtv. Can't see why this should be a problem when the
>> vanilla ivtv driver
>> installs fine.
>>
>> Best regards
>> Robert
>>
>
> Hi Robert,
>
> First, you may find posting to the list more expedient: others may be
> able to help you; and others may benefit from the answer. (For example,
> in this particular case I think Devin already knows the answer and could
> have helped you sooner if your mail went to the list.)
>
>
> The latest ivtv module now knows about some bundled remotes with various
> cards. For those remotes to "work out of the box", the ivtv driver
> needs the remote keypress mapping tables. Those tables are included in
> the new version of the ir-common module you should have built and
> installed along with the ivtv module. (Maybe I need to fix a Kconfig
> file dependency...)
>
> $ find v4l-dvb/linux/ -name "ir*c"
> v4l-dvb/linux/drivers/media/IR/ir-keytable.c
> v4l-dvb/linux/drivers/media/IR/ir-functions.c
> v4l-dvb/linux/drivers/media/IR/ir-sysfs.c
> v4l-dvb/linux/drivers/media/IR/ir-keymaps.c
> v4l-dvb/linux/drivers/media/video/ir-kbd-i2c.c
>
>
> Note, that Mauro recently shuffled the position of these files in the
> source tree to the IR directorty. That means where the ir-*.ko kernel
> modules get installed has also moved:
>
> $ find /lib/modules/`uname -r`/ -name "ir*ko"
> /lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/video/ir-kbd-i2c.ko
> /lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/IR/ir-common.ko
> /lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/IR/ir-core.ko
> ....
>
>
> So:
>
> 1. Did "make" appear to make all the new v4l-dvb modules, including the
> ivtv and ir-* modules? Did "make install" appear to install them all?
>
> 2. Do you have duplicate ir-common.ko and ir-core.ko modules
> under /lib/modules/`uname -r` ? If so move, backup or delete the
> duplicates that are not in the IR directory. Are ir-*ko objects in the
> IR directory? Did "make install" appear to perform a depmod -a?
>
>
> If building the latest source modules is too much to deal with, then
> please don't knock yourself out. Waiting is always an option; although
> maybe not a staisfying one at times. (I don't expect ordinary users and
> subscribers to the ivtv-users list to think they need to put herculean
> efforts into trying to test bleeding edge code.) The fix will get into
> the main v4l-dvb repository soon. Propagation to 2.6.33 may take some
> time. Propagation of 2.6.33 to distributions will take more time.
> However, the change will eventually make it to the end user that way.
>
> Thanks again.
>
> Regards,
> Andy
>
>
>
>> Andy Walls wrote:
>>
>>> On Sun, 2010-01-17 at 09:05 +0000, Robert Sharp wrote:
>>>
>>>
>>>> I recently upgraded a PC with the PVR-150 to 2.6.31 and am suffering
>>>> from the return of the tinniness problem. There is an interesting
>>>> discussion in the dev list but no clear resolution. Can someone explain
>>>> either when the fix discussed will be available to ordinary users or how
>>>> we can apply the patch to fix this.
>>>>
>>>>
>>> Robert,
>>>
>>> I have a fix that Martin is (rightly) not happy with here:
>>>
>>> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/
>>>
>>> if you could test it out and let me know if it make the problem go away,
>>> that would be great.
>>>
>>> Then as a second step, if you can normally reliably reproduce the tinny
>>> audio, look to reduce the delays in this part of the patch:
>>>
>>> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/rev/7753cdcebd28#l2.11
>>>
>>> I would appreciate it. I was thinking 10 msec for the first msleep()
>>> and 140 to 100 msec for the second msleep.
>>>
>>> The easiest way to test it is:
>>>
>>> 1. Download:
>>> http://linuxtv.org/hg/~awalls/v4l-dvb-bugfix/archive/tip.tar.gz
>>>
>>> 2. untar
>>> 3. Change into the directory and build:
>>>
>>> cd v4l-dvb-bugfix-blahblah/
>>> make
>>>
>>> 4. Back up your current modules in /linux/`uname -r`/kernel/media
>>> if you want to roll back.
>>>
>>> 5. Then install the modules as root,unload any running modules, and load
>>> the new ivtv module:
>>>
>>> cd v4l-dvb-bugfix-blahblah/
>>> make install
>>> (kill the mythbackend or anything else that has the devices open)
>>> make unload
>>> make unload
>>> modprobe ivtv
>>>
>>> And you're ready to test.
>>>
>>>
>>> Thanks,
>>> Andy
>>>
>
>
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users