2011/1/22 Liam Girdwood lrg@slimlogic.co.uk
On Fri, 2011-01-21 at 14:53 -0600, pl bossart wrote:
I am fine with a system-specific configuration file for each use case, but if I have to change the defines in alsa-lib it's a bit of a pain. It'll imply branches and specific packages just for a stupid include file.
If the define isn't there you should just be able to use a string - no need to update the header file unless the thing being added is sufficiently general that it seems like a good idea.
I think I am missing something here. First I believe there's only one application (PulseAudio or resource management of some sort) that will talk to UCM. Player applications shouldn't know anything about UCM, right? You would end-up making conflicting decisions.
Yes, it's intended only Pulseaudio (or similar) will directly control the use case.
Do you mean that I cannot use my desktop to act as a karaoke by playing music to default device and singing to the mic with "Mic Playback Volume" of HDA codec until pulseaudio or Sound preference implement "Mic Playback Volume" ?