Le Mardi 27 Novembre 2001 18:36, Jaroslav Kysela a écrit :
> On Tue, 27 Nov 2001, Nicolas DEVERGE wrote:
> > Hi,
> > I tried to use the current CVS version of the alsa lib and aserver tool.
> > I would like to use two instances of aplay in the same time.
> >
> > First, I tried with this configuration :
> >
> > server.local {
> > host localhost
> > socket /tmp/alsa
> > port 8888
> > }
> >
> > pcm.shared_left {
> > type share
> > slave.pcm "plughw:0,0,0"
> > bindings {
> > 0 0
> > }
> > }
> >
> > pcm.shared_right {
> > type share
> > slave.pcm "plughw:0,0,0"
> > bindings {
> > 0 1
> > }
> > }
> >
> > pcm.remote_left {
> > type shm
> > server local
> > pcm "plug:shared_left"
> > }
> >
> > pcm.remote_right {
> > type shm
> > server local
> > pcm "plug:shared_right"
> > }
> >
> > I started my aserver in a terminal, it works, but when I start aplay in
> > another terminal, overruns always occur (messages like "xrun!!! (at least
> > 0.083 ms long)" ).
>
> Try 'aplay -R 0'. It should improve buffering when stream starts.
I tried this option, but the problem is still here. I always get overruns,
and the file that I play seems to be played very quickly (the file lasts
about 3mn, and it is played in 20s).
>
> > I also tried aserver with another configuration :
> >
> > server.other {
> > host 127.0.0.1
> > socket /tmp/alsa
> > }
> >
> > pcm.test {
> > type shm
> > server other
> > pcm 0_6_7
> > }
> >
> > pcm.test2 {
> > type shm
> > server toto
> > pcm 0_0_1
> > }
> >
> > pcm.0_6_7 {
> > type plug
> > ttable.0.6 1
> > ttable.1.7 1
> > slave.pcm {
> > type hw
> > card 0
> > }
> > }
> >
> > pcm.0_0_1 {
> > type plug
> > ttable.0.0 1
> > ttable.1.1 1
> > slave.pcm {
> > type hw
> > card 0
> > }
> > }
> >
> > When I start aserver and only one aplay (aplay -D test file.wav) process,
> > it works, but when I start a second instance of aplay (aplay -D test2
> > file.wav), aserver tells that the ressource is busy whereas I saw that
> > aserver open the device in SND_PCM_NONBLOCK mode.
>
> It's obvious. When one aserver use the PCM device, then second aserver is
> blocked.
I use one asever, and two instances of aplay, it is when I start the second
aplay process that I get the message from my aserver process.
Regards,
Nico
>
> Jaroslav
>
> -----
> Jaroslav Kysela <[EMAIL PROTECTED]>
> SuSE Linux http://www.suse.com
> ALSA Project http://www.alsa-project.org
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
