On 03-Dec-02, Giles Constant wrote: > I've got an sbawe 64, and I'm trying to get multple streams working. > It only shows one subdevice available, but I thought alsa could mix > into that stuff.
[...] > ALSA lib pcm_hw.c:866:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: > Device or resource busy > aplay: main:462: audio open error: Device or resource busy > > Surely the -N switch shouldn't be blocking like that? Well, I guess that isn't /blocking/ as such - it's failing. ALSA doesn't do mixing itself unless the hardware of the particular card supports it (I believe emu10k1 does). The standard reason given for this is that imposing a soft mixer layer on all ALSA access would add a huge chunk of latency to every application, even those which don't need to use it, thus making all sorts of real-time applications difficult or impossible to write. The best way (by posts here) to mix multiple streams seems to be to use Jack (a low-latency audio mixing daemon/library) if you're writing a new ALSA application, or something like esd or artsd if you don't care about latency issues. -- Adam Jones ([EMAIL PROTECTED])(http://www.yggdrasl.demon.co.uk/) .oO("So before you start calling me dirty...." ) PGP public key: http://www.yggdrasl.demon.co.uk/pubkey.asc ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
