Sebastien Roy wrote: > On Mon, 2008-12-15 at 10:30 -0800, Garrett D'Amore wrote: >> Chris Liu wrote: >>> Let me explain respectively. >>> >>> OSS - libsndfile has not much to do with OSS. It mainly focused on >>> processing data from one format to others. It does not like to deal >>> much with hardware or operating systems. The only exception may be >>> sndfile-play. Sndfile-play is one of three tiny utilities it provides, >>> which only writes audio data directly to /dev/audio (on Solaris), >>> which is standard audio device on Solaris. On SunRay sndfile-play wont >>> work properly because SunRay client uses another audio device >>> specified by $AUDIODEV. However, it is not a main purpose of libsndfile. >> If this is the case, can we skip integrating sndfile-play, at least >> until it honors Sun Ray? > > 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.) Mike. -- mike.oliver at sun.com
