>> 2. How is device selection designed to work with ALSA? My experience >> with ALSA has been very confusing in this regard. I recall reading at >> least once that ALSA is not designed to have applications enumerate all >> the devices; that the correct way is to use ~/.asoundrc to define a >> hardware device and then supply that name to applications. But is there >> anything more sophisticated an application can do than to just present >> the user with a text box? > >the pcm name really depends on the driver implementation. >usually, device #0 is provided for general use. but, for example, the >implementation of 4-channel sound is driver speicific. >some driver implements using a control switch and other combines >multiple pcm streams, etc. > >however, there are standard names, too: >default, front, rear, center_lfe, surround40, surround51, spdif and >iec958 (identical with spdif). >it would be nice if users can choose one of them from a list, and >additionally have an input text field (well, not sophisticated, >though).
but there's no straightforward method of determining which names actually exist. the code in aplay that handles the -L request, for example, is baroque to the point of extremity. an application could not just use those standard names, because the audio interface they have may not support them. in addition this also doesn't deal with the issue of users with more than one soundcard installed. --p ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
