hi, <br><br>Once the time will come, I expect HAL to give you the ALSA "virtual device name" with the right arguments directly. <br>That would also help bluez, and ffado.<br>Do you see the need for the configuration file in this case?
<br><br>I pastbin'ed some time ago a diff for HAL spec.<br><a href="http://pastebin.ca/519493">http://pastebin.ca/519493</a><br><br>regards,<br><br>PS: The UI that will offer you the ALSA device will probably never come, for many reasons!
<br>
<br>-- <br>Marc-André Lureau, GSmartMix
<br><br><div><span class="gmail_quote">On 7/13/07, <b class="gmail_sendername">Jon Smirl</b> <<a href="mailto:jonsmirl@gmail.com">jonsmirl@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Most apps don't have a UI for setting their pulse source/sink but they<br>do have a UI for picking an ALSA device. Could pulse automatically<br>create ALSA entries for the pulse devices using the HAL info.product<br>attribute? This would be a transition tool while we wait for more apps
<br>to get a pulse UI.<br><br>Dynamically create the equivalent of these entries so that when I plug<br>in new USB device a new ALSA device gets created.<br><br>pcm.philips_usb { <= use HAL pretty name<br> type pulse
<br> device alsa_output.usb_device_471_155_noserial_if0_alsa_playback_0<br>}<br></blockquote></div>