Hi, At Fri, 16 Nov 2001 11:45:56 +0100, Sebastián González wrote: > > Hi Takashi, thanks for answering. > I think I have correct modules.conf and devfsd.conf files, as the > necesary modules get loaded when an attempt to access /dev/dsp occurs. > Now my ALSA system works (I can use alsamixer, aplay, etc). > > The thing that still not works is that I cannot play simultaneous sound, > for instance if I execute: > > guajira:~> aplay /usr/share/sounds/KDE_Startup.wav & aplay > /usr/share/sounds/startup3.wav > > they don't sound at the same time, KDE_Startup.wav plays first and only > after it has finished does startup3.wav play; what I expect is to hear > the simultaneous sound of both sound files (mixed in real time), but the > second instance of aplay waits for the first to finish, and then begins > to play. The same happens if I play two .mp3 files, or, in general, if I > use simultaneously any two programs that play sound. As I wrote in the previous mail, on cmipci you cannot play multiple streams simultaneously. It's hardware limit. For mixing, you need to use esound or arts.
> I added the line "options snd-pcm-oss snd_nonblock_open=1" to > modules.conf but didn't work (I also tried loading snd-pcm-oss > manually and passing snd_nonblock_open=1 as a parameter to modprobe). The snd_nonblock_open option is valid only for OSS PCM emuluation. For ALSA native applications, this doesn't work - thus aplay is blocked as you've seen. And, the meaning of this option is that the open syscall returns immediately with error when the device is busy. It has nothing to do with multiple playback.. ciao, Takashi _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
