Thank you for this. I have not investigated ALSA beyond establishing
that I don't have it installed. Slightly surprised, given I'm running
Debian unstable, which I thought would give me pretty up to date stuff,
but there you go.
Not actually going to bother too much as the problem only occurs : (all
could be irrelevant but but but...)
1. with a minidisk recording where the mike battery was dying, so the
volume slowly reduced to almost nothing.
2. when the recording volume was very low anyway.
3. when I set it going and then switched to a different desktop and
carried on doing something else (ie audacity no longer in focus).
The process is being killed by some watchdog process, which, if I can
find it, I'll damn well kill it myself!
This evening I copied several tracks from a different minidisk (much
higher recording volume) without problem. Of course, I kept the
audacity window in focus all the time and kept interacting with it, so I
suspect that's the problem. And that makes it much less of a problem
for me, since 99% of my work is done like that.
Er..it's late, so if any of the above doesn't make sense, please say so
and I'll try to clarify it.
Richard Ash wrote:
>On Thu, 2004-05-06 at 00:21, Rob Clack wrote:
>>Never heard of ALSA. Tried ALSA and alsa at the command prompt, but got
>>"command not found" both times. What is it?
>ALSA stands for Advanced Linux Sound Architechure, and is the sound
>driver and API subsystem for all new linux systems, replacing the old
>OSS drivers in the kernel as of version 2.6, and available externally
>for 2.4 kernel systems. It's homepage is at http://www.alsa-project.org/
>$ alsamixer -h
>to get the version of the package installed on your system. If this
>isn't found then you may have an old OSS installation. Audacity should
>work with this as well. In either case you will need the headers (devel
>package) to compile audacity.