[NTLUG:Discuss] Fedora Audio CLI Options

[Paul Ingendorf]

The alsamix program looks to be exactly what I was looking for.  I don't
have a direct script for alsa, or any sound scripts for that mater, although
I'm sure it is buried in something else.  I checked out /etc/asound.state as
well and that looks like that would fix the after reboot problem but the
reason I was looking for a cli option was to ensure I don't have to do this
again after another update.  The script I run should setup the sound card
appropriately just in case I've messed with sounds settings and forgot to
set them back.  I thought I have this licked using aumix but that didn't
enable the capture option.  I can now do this using amixer which I had never
used before and appears to be a much better way of handling it as even
alsamixer would have enabled at least turning on capture while aumix did
not.

Thanks for the help.

-----Original Message-----
From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org]On
Behalf Of jpmiller at quorumhost.com
Sent: Monday, November 29, 2004 4:40 PM
To: pauldy at wantek.net; NTLUG Discussion List
Subject: Re: [NTLUG:Discuss] Fedora Audio CLI Options


To answer the question: "Does anyone know of a product I can use to
incorporate
into a script that will allow me to setup all audio options before I start
my
recording?" If your card is supported under alsa, amixer should do the
trick.

but I'd rather address the larger question of why are the setting getting
blown
away.

On my gentoo system, when alsa is started it looks for a file that defines
the
mixer settings, I belive called asound.state (sorry I can't be more accurate
about the file name and path - it's probably /etc/asound.state - , but I'm
not
at the box right now).  alsa throws a warning message if that file isn't
found,
you might try stopping and starting that service to see if that's the case.

iirc, my alsa init script has a save option that will write the current
setting
to that file, if that's true for your fc3 script that might be a quick and
easy
solution. i.e. run 'alsamixer' - make your changes; run '/etc/init.d/alsa
save';
'/etc/init.d/alsa restart' and see if it worked (alternatively, 'init 6' if
you
want to see a full reboot.)

but if you just want to script setting changes for your mixer, amixer is
probably the tool you want to use.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.