hi, Once the time will come, I expect HAL to give you the ALSA "virtual device name" with the right arguments directly. That would also help bluez, and ffado. Do you see the need for the configuration file in this case? I pastbin'ed some time ago a diff for HAL spec. http://pastebin.ca/519493 regards, PS: The UI that will offer you the ALSA device will probably never come, for many reasons! -- Marc-Andr? Lureau, GSmartMix On 7/13/07, Jon Smirl <jonsmirl at gmail.com> wrote: > > Most apps don't have a UI for setting their pulse source/sink but they > do have a UI for picking an ALSA device. Could pulse automatically > create ALSA entries for the pulse devices using the HAL info.product > attribute? This would be a transition tool while we wait for more apps > to get a pulse UI. > > Dynamically create the equivalent of these entries so that when I plug > in new USB device a new ALSA device gets created. > > pcm.philips_usb { <= use HAL pretty name > type pulse > device alsa_output.usb_device_471_155_noserial_if0_alsa_playback_0 > } > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20070714/d631a55b/attachment.htm>
