Subject: Re: Athlon + VIA
To: None <port-i386@netbsd.org>
From: Richard Rauch <rauch@eecs.ukans.edu>
List: port-i386
Date: 05/10/2001 02:05:32
> What sort of trouble do you have with auvia recording? [...]

This is from memory.  I don't actually record anything useful, but was
just playing around with it.  The problems went something like this:

I hooked up one of those cheap microphones that ship with a lot of
computers, plugging it into the mic jack.  I can't remember if I ever got
the audiorecord(1) command to produce anything useful.

After a little frustration with that, I browsed pkgsrc, and ended up
building .../audio/dap.  As I recall, to get ANYTHING usable with dap's
recording, I had to do one of two things:

 (a) Practically put the microphone in my mouth.  This recorded reasonably
     clearly, but it isn't a practical way to use it.  It would never do
     for picking up most other sound sources, nor would it be acceptable
     if I wanted to use capture casual voice.

 (b) Record at high frequency and resolution.  Then, with some effort and
     distortion, I can use dap's signal processing passes to ramp up the
     volume (and filter out some hiss, I think) to get passable playback
     of casual speech.


Like I said, I don't use recording that much, so I can't be 100% sure of
anything, save that it didn't work terribly well for me.

I've tried each of two of these wand-on-a-stand microphones; one shipped
with my old Gateway 2000 machine (and is known to have worked quite well
with MS-WINDOWS and the Ensoniq PCI soundcard).  The other shipped new
with my Athlon system last August and I can only presum that it works
well.

I also have checked to make sure that the recording-level gain is cranked
up (dap defaults to about 75% or 80%, I think).

What I definitely have NOT tried to do is to hook up any kind of sound
source to the internal input.  (I believe that there's a spot on the
motherboard for CD audio output.)


I rarely use sound at all on my Athlon system, actually, but it would be
nice if the problem (be it software bug, or pilot-error) could be
corrected.  (^&


  "I probably don't know what I'm talking about." --rauch@eecs.ukans.edu