Hi Bill,
>>> But I can't work out how to make a stream loop back so that it enters and
>>> leaves
>>> on the same "side" of ALSA. For example, if I have some software playing
>>> music
>>> from a file, I can route that down to hardware OK. But I can't seem to
>>> route it
>>> back to software
On Fri, 18 May 2007, Benjamin van den Hout wrote:
>>
>> Hi,
>>
>> I may be completely wrong, but my current understanding of ALSA is that it
>> manages streams of data. ALSA seems to sit between software and hardware,
>> with
>> streams passing through ("down" to hardware if playing sound, "up"
Hello again,
[Sorry, I missed a bit of sentence]
I've read about the snd-aloop driver. I've tried to build it, created a
.deb file (I'm running Debian testing) and upgraded my alsa-modules. I
can play just fine to the aloop device but recording from it gives me a
very nasty kernel OOPS message
>
> Hi,
>
> I may be completely wrong, but my current understanding of ALSA is that it
> manages streams of data. ALSA seems to sit between software and hardware,
> with
> streams passing through ("down" to hardware if playing sound, "up" from
> hardware
> if listening, for example). I can use
Hi,
I may be completely wrong, but my current understanding of ALSA is that it
manages streams of data. ALSA seems to sit between software and hardware, with
streams passing through ("down" to hardware if playing sound, "up" from hardware
if listening, for example). I can use dmix to merge stre