On Thu Jul 10 11:35 -0400, David Walser wrote: > Levi Ramsey wrote: > > On Thu Jul 10 13:40 +0200, Guillaume Cottenceau wrote: > >> We don't use soundwrapper for cpu-intensive applications because > >> it has an important cpu overhead. > >> > >> Moreover, FB uses SDL and SDL can use (theoretically) arts. > > > > O if every app would just use ao... ;o) > > I agree, that would be nice. Unfortunately that means they'd all be crashing right > now in some circumstances (aRts has the device open). Correct?
No, ao (you can check my xmmsao output plugin for a demo of this) tries (by default, this can be configured in /etc/ao.conf, IIRC) to open ALSA, if that fails, then it tries OSS, and if that fails, then it tries ESD or aRts. To test this out, start xmms, set the output plugin to ao output, then play something. If you're running aRts or ESD, kill that, then move xmms to the next song (or alternatively hit "Play" again in xmms). If you're running just ALSA (on a card that doesn't do hardware mixing) or OSS, then play something, press stop, start ESD or aRtsd, and move to another song as above. Regardless, xmmsao (through the ao library) will adapt. I've actually toyed with hacking aRts and/or ESD to use ao for audio output, which would allow both of them to be loaded at the same time... -- Levi Ramsey [EMAIL PROTECTED] [EMAIL PROTECTED] Take due notice and govern yourselves accordingly. Currently playing: Rush - Vapor Trails - Freeze Linux 2.4.21-0.15mdk 13:28:00 up 3:52, 8 users, load average: 0.46, 0.52, 0.41
