Daniel, thank you for the information (I understand a little more now :-)). I
still have a few questions, however:
a) This "blocking" behaviour didn't happen with Warty (aplay works from within
gnome-terminal on the same machine when I boot into Warty), and I *didn't* set
up dmix on that machine.
b) When I install beep-media-player (0.9.7-1ubuntu1) on Hoary, it defaults to
using the "OSS Output Plugin and just locks up. (I suspect this lock-up is
related to aplay's blocking which you've explained is due esd exclusively
grabbing the audio device). When I change beep-media-player's output to use esd,
everything works perfectly! :-)
I might try to find out a little more about why aplay blocks with esd (or rather
why it didn't with Warty on the same machine)...
(In reply to comment #18)
Daniel, thank you for the information (I understand a little more now :-)). I
still have a few questions, however:
a) This "blocking" behaviour didn't happen with Warty (aplay works from within
gnome-terminal on the same machine when I boot into Warty), and I *didn't* set
up dmix on that machine.
b) When I install beep-media-player (0.9.7-1ubuntu1) on Hoary, it defaults to
using the "OSS Output Plugin and just locks up. (I suspect this lock-up is
related to aplay's blocking which you've explained is due esd exclusively
grabbing the audio device). When I change beep-media-player's output to use esd,
everything works perfectly! :-)
I might try to find out a little more about why aplay blocks with esd (or rather
why it didn't with Warty on the same machine)...
Thank you, Jaime