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.
D
Dynamically create the equivalent of these entries so that when I plug
in new USB device a new ALSA device gets created.
You could do it with some clever scripting :). It really shouldn't be too
hard, just set up a daemon that listens for hal events and then modifies
your asound.conf file on t
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
r
On Fri, 13.07.07 09:45, Jon Smirl ([EMAIL PROTECTED]) 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
