By Date: <-- -->
By Thread: <-- -->

saa7134 TV Tuner card audio problems

Hi Noel,

Am Freitag, den 10.03.2006, 16:18 -0800 schrieb Noel Smith:
> Thanks, as soon as I read your post, I realized what i
> think I did.  I think my problem was that I had
> installed the v4l-dvb from www.linuxtv.org, and I
> think that's when I got the sound working that one
> time, but I didn't know exactly what got it working
> right.  Since then I had done and update to the system
> using yum, and I'm guessing that actually brought me
> back a step.  I've now installed v4l-dvb again, and
> now I'm able to modprobe saa7134-oss and in dmesg it
> shows that it's loaded DMA sound and registered dsp1
> and mixer1.  So, I'm a step closer, at least I think I
> am.  I still am not getting audio from the tuner card.
>  When I run MythTV and select watch TV I still just
> get a click from the speakers and then quiet noise.

there is a general problem with mythtv and all v4l1 only apps and the
v4l2 saa7134 driver.
Mythtv uses v4l1 mute calls and such go through the v4l1-compat layer to
talk with the v4l2 saa7134 driver and there is an undiscovered bug.
Because of this, people were using some "v4lctl volume mute off" command
from xawtv-3.9x all the time. We know the bit meanwhile that makes
digital audio always available, which could help on this issue, but it
is set to mute again since many new cards, especially cardbus types,
don't have any analog audio out anymore and to keep the digital audio
always open disables also automute on channel switching and they get
some annoying noise burst all the time then.

> At this point, I'm not really sure if I need to get a
> better mixer program that can getting the audio from
> one to the other or if I need to find a command that
> works to transer the audio from dsp1 to dsp.  I've
> tried:
> sox -t al -r 32000 -b -c 2 /dev/dsp1 -t al /dev/dsp
> 
> but, when type that and press <enter>, it just sits
> there and seems like it locks up the audio, and I end
> up having to close the konsole window as it seems to
> never finish the command and bring me back to a
> prompt.  Anyone have any suggestions as to my next
> step?

Install mercurial as this happily still should work with Fedora kernels.
The new alsa stuff had several minor issues, quite normal when starting
such major projects, and they are still mirrored in the recent Fedora
kernels. The oss=1 option doesn't work anymore and to get saa7134-oss
and saa7134-alsa you have to enable it in Kbuild. Even some few days old
2.6.16-rc5-git11 only supports one saa7134 alsa device, but mercurial
has no problems with four.

Something like this works for me.
/usr/local/bin/mencoder -v tv:// -tv
driver=v4l2:device=/dev/video0:width=640:height=480:chanlist=europe-
west:alsa:adevice=hw.1,0:audiorate=32000:amode=1:forceaudio:volume=70:immediatemode=0:norm=PAL -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=3600 -vf pp=lb -oac mp3lame -lameopts cbr:br=128:mode=0 -o test.avi

And with alsa oss compat enabled this should still do as well.
"sox -c 2 -s -w -r 32000 -t ossdsp /dev/dsp1 -t ossdsp -w -r 32000 /dev/dsp"

Others tested sox already with genuine alsa devices too.
(guess we still might have some SECAM-L audio bug too)

Cheers,
Hermann


> 
> --- hermann pitton <v4l (at) arcor.de> wrote:
> 
> > Am Donnerstag, den 09.03.2006, 17:54 -0800 schrieb
> > Noel Smith:
> > > Well, at this point I'm wondering if my best bet
> > is to
> > > start fresh by completely reinstalling Fedora Core
> > 4. 
> > 
> > Don't do.
> > 
> > The transient period of still working saa7134 oss=1
> > and out factored
> > saa7134-oss and saa7134-alsa modules is missing.
> > 
> > The Fedora guys have simply enough to do always and
> > kicked this out for
> > now. Either you try to get a recent mercurial
> > compiled on your stuff or
> > a recent 2.6.16.x-git.x.
> > 
> > It is not much related to Fedora Core 4 at all.
> > 


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list