[NTLUG:Discuss] Re: Fedora Audio CLI Options

[Bryan J. Smith]

On Mon, 2004-11-29 at 12:18, Paul Ingendorf wrote:
> Ok I have a setup I have run for years now to record a radio program I like
> to listen to late at night.  It has worked great with various distributions
> and I have never had any problems.  Through FC2 it worked great, I never ran
> FC1.  Now enter FC3 and now when I reboot all I get is silence from the mic.
> I have an aumix file I load to get the appropriate audio settings for the
> mic level etc...  for some reason however every time the machine boots all
> audio settings are reset to defaults.  I have to open something like kmix
> and select capture before I will get audio.  The problem is every time I
> reboot the machine I have to do this now.  Needless to say this is a bit
> annoying.  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?

I've actually explained this solution on several lists now.  I'll just
post the "raw modifications" to make to /etc/modprobe.conf for kernel
2.6 distros:  

  alias snd-card-0 (your driver)
  remove snd-card-0 /bin/aumix -f /etc/aumixrc -S &&
      /sbin/modprobe -r snd-card-0
  install snd-card-0 /sbin/modprobe snd-card-0 &&
      snd-card-0 /bin/aumix -L

I'll explain what this does when I have more time.  But in a nutshell,
you're loading/saving the mixer settings when the driver is
loaded/unloaded -- and there is a further detail in whether or not the
user or system-wide rc file is loaded.

I'll also explain how you should modify /etc/modules.conf for kernel 2.4
distros when I have time.

-- 
Bryan J. Smith                                    b.j.smith at ieee.org 
-------------------------------------------------------------------- 
Subtotal Cost of Ownership (SCO) for Windows being less than Linux
Total Cost of Ownership (TCO) assumes experts for the former, costly
retraining for the latter, omitted "software assurance" costs in 
compatible desktop OS/apps for the former, no free/legacy reuse for
latter, and no basic security, patch or downtime comparison at all.