Hi Matthias, On Mon, 6 May 2002, Matthias Dahl wrote: > Hey there... <( http://www.matthew2k.de.vu )>-=-<( powered by linux )> > > I have just tried the snapshot of the saa7134 module. First of all, as far as > I can tell, there is a tuner type 5 on board... :) > > Now to the problem(s). I will start with the thing that drives me nuts -- it's > that high tone in the background of the TV audio. I just figured that this > does *only* occur when amux is set to TV instead of LINE2. Setting it to TV > will also enable some kind of amplifying because the audio gets slowly > amplified to a specific mark - with that high tone there from the beginning. > Unfortunately if amux is set to LINE2, TV audio will *never* be anything else > but mono --- with amux=TV, saa7134 will properably switch audio modes with > that high tone though in the background. :( Also with LINE2 audio is activated > as soon as the module is loaded and there is no way to switch it off except > for muting the aux in the soundcard mixer itself, which shouldn't be necessary > (again, this works fine with amux=TV: audio is only on if radio/tv is used). 1. Do you have an external analog mux (e.g., HEF4052) on your board? 2. I think there's some interaction between the TV audio signal and some other signal. This probably needs some fiddling with the audio switching logic. Unfortunately I can only speak from my experience with the FlyVideo2000 which uses the external analog mux to select between different inputs, (see the gpio settings in saa7134-cards.c for FlyVideo2000), which I discovered by trial and error.... > > Nevertheless, the radio part always works fine in stereo in top quality > without the annoying high tone... which is strange because TV and radio use > same chip and the same tuner - so actually the tone should be here too. > > I have also talked to the Tevio support line to figure out if this high tone > problem is known - and I was told they haven't heard of a thing like that yet, > so probably this is caused by the saa7134 module somehow. > I believe that audio should work fine once the proper audio channel settings are determined. The trick question is what/how? By the way, your dmesg output looks 'normal'. The issue with audio being unmuted after quitting xawtv when LINE2 is used for TV audio is a saa7134 module audio configuration cleanup issue. I suspect the audio signal is always present on LINE2 from your description. So to mute, it has to be deselected. (This needs some work on the module to figure out what's going on). As for TV input used for TV audio, it sounds like some configuration/ cleanup problems in saa7134. Do you still get the same problem if you 'rmmod saa7134 tuner; modprobe tuner saa7134'? > Also the grabdisplay doesn't work yet. I get the following message: > > This is xawtv-3.73, running on Linux/i686 (2.4.19-pre8) > v4l2: framebuffer info > cap: clipping > flags: extern > base: 0xec000000 (nil) (nil) > format: 1152x864, RGBP, 1990656 byte > ioctl:VIDIOC_QBUF(0,type=1,off=0,len=221184,used=0,flags=0x0,ts=0,seq=0): Bad address > ioctl: VIDIOC_QBUF(0,type=1,off=0,len=221184,used=0,flags=0x0,ts=0,seq=0): Bad address > ioctl: VIDIOC_DQBUF(0,type=1,off=0,len=0,used=0,flags=0x0,ts=0,seq=0): Invalid argument > That's Gerd's department. > What's also quite strange is that watching TV will destroy the text console, > and I don't mean the problem when switching to the console while the overlay > is still on - I mean start xawtv (either with or without Xv, makes no > difference in this case), wait for the overlay, quit xawtv and take a look at > the console - it's visually destroyed and stays that way until a program uses > Xv for example... that will restore the text console. > My RH7.1 system (kernel 2.4.19-pre) with Riva TNT2 and NVidia's driver splatters video pixels all over the screen when I enable/disable xawtv's dialog box, etc. I think Xv support is still rather premature. > Also scaling with Xv doesn't work well too. The image looks like this... > > +++++++++++++++++++ > + | N + > + VIDEO | O + > + OVERLAY | I + > + | S + > + | E + > +++++++++++++++++++ > > With noise I mean just static garbage from the video memory. The picture is > complete though... it's just not fully scaled in width. Well, I have a 2" border all around the overlay window, and some residual overscan lines (grey static?) at the bottom of the video overlay. I think it's an Xv issue? T.C. ---- Wan Tat Chee (Lecturer) School of Computer Science, Univ. Science Malaysia, 11800 Minden, Penang, Malaysia. Ofc Ph: +604 657-7888 x 3617 Internet: tcwan@xxxxxxxxx Web: http://nrg.cs.usm.my/~tcwan GPG Key : http://nrg.cs.usm.my/~tcwan/tcw_gpg.asc F'print : FB0F CED7 85A5 ECF9 DEF0 50E8 A550 A0D2 8638 B1EB
