>Garrett D'Amore wrote: >> >> By the way, use of $AUDIODEV has been a standard technique since at >> least Sun Ray first shipped. Its not new on Solaris. >> >> In situations where there is more than one audio device, /dev/audio >> won't necessarily point to the right device anyway. The fact that the >> 3rd party app can't use a different audio device is a severe shortcoming >> in the app. >> >> -- Garrett >> > >Picking output device selection at open time seems quaint, given our >in-kernel mixer architecture. For example, how does virtual terminal >support work with /dev/audio? If I plug in a USB headset, do I need to >restart all applications using audio to redirect the sound to the >headset? > >Why not just think of /dev/audio as a virtual I/O device, and map >it to real hardware, network connections, dynamically?
As long as we don't have a "session" which can be nicely grouped, it makes sense to make all $AUDIODEVs virtual, but they should not be all called /dev/audio. If we want to virtualize /dev/audio (the device itself), then I would like to see some mechanism which allows a device to distinguish between different "sessions". Casper
