well i tryed the lattest bleeding edge driver as of 8pm last night and it does not fix the issue i still get the bad audio. below is the dmesg info when the driver is loaded.
Linux video capture interface: v2.00 ivtv: Start initialization, version 1.3.0 ivtv0: Initializing card #0 ivtv0: Autodetected Hauppauge card (cx23416 based) ACPI: PCI Interrupt 0000:05:09.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17 PCI: Enabling bus mastering for device 0000:05:09.0 tveeprom 2-0050: Hauppauge model 26552, rev F0A3, serial# 10413145 tveeprom 2-0050: tuner model is TCL MFNM05-4 (idx 103, type 43) tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 2-0050: audio processor is CX25843 (idx 37) tveeprom 2-0050: decoder processor is CX25843 (idx 30) tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter ivtv0: Autodetected Hauppauge WinTV PVR-150 cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0) tda9887 2-0043: creating new instance tda9887 2-0043: tda988[5/6/7] found tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) tuner-simple 2-0061: creating new instance tuner-simple 2-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F)) cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes) ivtv0: Registered device video0 for encoder MPG (4096 kB) ivtv0: Registered device video32 for encoder YUV (2048 kB) ivtv0: Registered device vbi0 for encoder VBI (1024 kB) ivtv0: Registered device video24 for encoder PCM (320 kB) ivtv0: Registered device radio0 for encoder radio ivtv0: Initialized card #0: Hauppauge WinTV PVR-150 ivtv: End initialization ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) ivtv0: Encoder revision: 0x02060039 also as a side note, i did change system boards for other reasons so its a different brand/model but simmiler system board. Thanks for any help Kevin > Hi, > well i have had my system online, and i finaly have time to get back to > trying to fix this, i have bin using the set audio input fix as noted > before and it still gives me the bad audio, altho not nearly as often, i > did try the bleeding edge drivers with no success still same issue and no > changes, although that was a month ago, i will try again with the current > bleeding edge driver and see if it works, other wise in my free time i can > work with anyone who knows more about this to try and debug this since it > seems like its an unresoveled issue that some people are having and just > arnt speaking up. i currently am traviling, however i have a second slave > mythbox that does tuning, since i have bin working on fixing it on the > master im not sure if the slave is doing the same, if it is then for any > dev that would like to examin the issue with root access give me a week or > so, and ill be able to secure remote access to the system. > > if anyone has found a fix or work around already and i didnt see the > message please let me know. > > thanks > > Kevin > > >> well im not sure now, i have just had a major systemboard failure, i >> have yet to fully test what has failed but the entire usb system has >> failed, so it may have bin a bad system board causing the issues for me, >> ill know for sure when i get a new replacement. >> >> Kevin >> >> Scott Harris wrote: >>> >>> Hans Verkuil wrote: >>> >>> >>>> Hi Mike, >>>> >>>> The tinny audio problem plagued a lot of people in the past, but I >>>> haven't heard about this for quite some time now. Please make sure you >>>> are using the latest version (preferably the 'bleeding edge' code from >>>> http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver). >>>> >>>> It seems that this problem only hits NTSC cards and it seems to be >>>> related to some interaction between the audio chip and the cx23416. >>>> After I made some changes in the way this is handled the problem >>>> disappeared, although I never quite understood what was going on >>>> internally. And I think that in one or two cases it was actually a bad >>>> card, so I wonder if you could get hold of another PVR500 to test >>>> with. >>>> >>>> Regards, >>>> >>>> Hans >>>> >>> >>> I know it doesn't help throwing in the "me too" emails, but I've never >>> been able to shake this problem from a pvr-250. It happens about 85% >>> of the time. >>> >>> I just run this from cron once a minute to fix it. >>> /usr/bin/v4l2-ctl -d /dev/video1 --set-audio-input=1 >>> >>> Scott >>> >>> >>> Linux mythtv 2.6.24.5-85.fc8 #1 SMP Sat Apr 19 11:18:09 EDT 2008 x86_64 >>> x86_64 x86_64 GNU/Linux >>> >>> >>> ivtv-kmdl-2.6.24.5-85.fc8-1.0.3-136.fc8 >>> ivtv_xdriver-1.0.0-9.fc8 >>> ivtv-firmware-20070217-17 >>> ivtv-1.0.3-136.fc8 >>> perl-Video-ivtv-0.13-8.fc8 >>> >>> _______________________________________________ >>> 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 >> >> > > > > _______________________________________________ > 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
