On Mon, 2008-12-15 at 11:06 -0800, Mike Oliver wrote: > Sebastien Roy wrote: > > It sounds to me more like the SunRay audio architecture is inadequate to > > support 3rd party tools. Perhaps that should be fixed rather than > > require audio software developers to have to add Sun-specific code to > > support SunRay. > > $AUDIODEV is not a Sun Ray invention. $AUDIODEV is part of the regular > Solaris audio infrastructure. See 'man audio'. Any audio app on > Solaris should support the designation of an alternative audio device > via $AUDIODEV. (And, in case anyone decides to do the right thing and > make this change, note that $AUDIODEV implies alternative data *and* > control devices.)
Granted that it's not a SunRay invention, its architecture is broken as it relates to code portability, virtualization, and modern technology (see Bart's comment regarding switching output devices on the fly, which other OSs such as MacOS X seem to handle just fine). Anyway, that's not necessarily this case. If it's trivial to handle AUDIODEV in the app being introduced by this case, then there's no reason not to patch the code to support it. My comment was a more general, in coming to a realization that $AUDIODEV isn't portable (and has other problems), and the fact that SunRay relies on it is a problem. Perhaps this discussion should be continued in the context of the 2008/318 Boomer case. -Seb
