On Tue, Feb 14, 2012 at 08:20:50AM +0100, David Henningsson wrote:
Please delete irrelevant context from mails, it makes it much easier to find what you've added,
On 02/13/2012 06:40 PM, Takashi Iwai wrote:
Mark Brown wrote:
C. kctls contain unique names ([location] base [direction] [channel]) optionally with TLVs
I would vote for "C2", although I would probably prefer "[location] base [channel]" over "[location] base [direction] [channel]", as direction is superfluous given "base". This is also what the current implementation offers, and what I've based my PulseAudio patches on.
If we're going to do stuff like this Takashi's suggestion of splitting direction from the channel seems like a really good idea, it both makes things read naturallly and means applications are more likely to be able to cope usefully with base types they've never heard of before.
Also; as this graph exposing thing is unlikely to be implemented in all layers of the audio stack any time soon, maybe C2 is also the one that gives the most obvious matching between mixer kcontrols and jack kcontrols? I'd like to move in this direction; not only because we currently do not have the graph, but also because that even if we have it, userspace apps choosing not to implement it will have a good option.
The naming stuff gets really painful for anything that isn't a basic PC audio card - the whole model used for the standard ALSA controls is very much fixed to an extremely basic model of what the hardware might look like.