Es schrieb Jason Miller: > > Dave, > Ah your message is both good to see and also bad. Just for > curiousity's sake, how long have you been dealing with this problem? Is > a driver for the SAA7133 being actively worked on? > > I for one am angered becuase when I bought the FV3K I was under the > impression that I was getting a card with an SAA7134, not an SAA7133... > > Ah well... > Jason > Hi, that one is completly my fault Jason, because I was blind to abroard. Thought, there should be a lot of crys, if there is something on NTSC "FV3Ks", whatever those are ... What Dave got told didn't indicate audio problems, but here is someone patient, who reported the mess beyond my times on the list in November last year. Bill sorry again. There is work on that and the chip is state of the art, guess Gerd has the audio on his Proteus-reference-saa7133 with an fm1216 Pal tuner? (See bttv-gallery). No idea in userland, if this is a special stereo-ntsc-audio problem with that chip! Otherwise I saw, how the saa7130 users solved their problem after a period of weirdness. What you get for this "dsp access wait time out [bit=WRR]", when the tuner is loaded? On known cards should be a audiocarrier detected and if not a default value for it is set, but that saa7133 card has no PCI_ID and no other defaults. You must found them first. Guess the FV tuners are black boxes and the FV2K settings for tuner=39 seem not to work on a first attempt (very good picture :). So if that is not senseless in that case (no stereo-ntsc-audio works at all yet) "add-new-cards.txt" says shuffle around the settings. Compare the eeprom outputs and isolate the tuner(s) and so on ... The infos are needed anyhow for a setup. Jason, if you plug the audio from the vcr in the soundcard no sound? > On Tue, 2003-08-19 at 01:12, DMW wrote: > > Jason wrote: > > > > <snip> > > > The main chip on the card is an "SAA7133HL/101". > > <snip> > > > > Hi Jason, > > > > It looks like we have the same problem right down to the "buzzing" sound you > > sometimes hear. I wish I could tell you the solution, but I haven't found it > > myself. I do know the FV3000 is supposed to be the stereo version, so that > > may be related. If you look in the saa7134 code you'll see that the saa7133 > > (note the 3) is dealt with quite differently for audio (although this may > > have changed in more recent snapshots). Given this plus I've been unable to > > find anyone, yet, with working audio with a saa7133 chip my current > > suspicion is that code just isn't as complete as the code for the saa7134 > > chip and is the culprit - but I'm sure Hermann or Gerd can speak much more > > intelligently about whether this could be true. > > Gerd for sure. It is the stereo version and has dma-audio and more intresting ... (4 channel?) http://www.semiconductors.philips.com/pip/SAA7133.html > > I've put this on hold for now, but I'll see if I can dig up what I've tried > > to date and hopefully one of us can finally get to the bottom of this. > > Do it together, if told on audio should be tested. (diff -ur clean-old-driver-dir new-driver-dir) Greetings Hermann
