Gianluca Sforna wrote:
> <quote>
> 6. If you have an application that uses ALSA, please make sure that it
>    doesn't hardcode ALSA driver names (i.e. something like "hw:0"), it
>    should use  "default" instead, which is now being redirected to
>    "pulse", our plugin for libasound. Hardcoding ALSA device names
>    (besides "default") is a bug in your application anyway, so here
>    you have yet another reason to fix that!
> </quote>


Yes, sounds more than reasonable.
Using "hw" or "plughw" we bypass the user configuration in .asoundrc,
and this is not nice. Moreover it should be not a task of the
application to select the audio configuration, which can be quite complex.

See this message and the other s from the thread:
http://lalists.stanford.edu/lad/2002/05/0111.html

Applications should allow to choose between *virtual* PCM devices (like
"default" is). However, using the ALSA API which is mostly used (1.0.13)
it is not possible (as far as I could understand: I am not an expert, I
spent some time gathering info); it is possible only starting from API
1.0.14.

In the meanwhile, I think the best choice would be do as mstute
suggested: use the "default" PCM device by default (this would not break
compatibility with PulseAudio, etc), but allow the user to choose a
specific audio card (i.e. if they want to use a USB headset).

Regards,
Ludovico

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to