Levi Ramsey wrote: > On Thu Jul 10 15:44 -0400, David Walser wrote: >> Levi Ramsey wrote: >> >> > 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. >> >> Looking at the code, the order it tries them depends on the directory entry for the >> plugins directory. > > Interesting... the documentation indicates a hierarchy of preferred > output devices...
Well there is that also. Each plugin has a priority value. What it does is this. The order it tries them is based on the directory entry for the plugins directory. It tests them until it finds one that works. Then as it goes through the rest of them, it only tests them if they have a higher priority. So ultimately, the one that gets picked is the one with the highest priority, out of all the ones that work. OSS and ALSA have the highest priority, ESD and ARTS have the lowest.
