2012-03-22 15:20, Tanu Kaskinen skrev: > On Thu, 2012-03-22 at 14:33 +0100, David Henningsson wrote: >> Ideally, I would like an algorithm that on path_select, took the new >> mute and volume state into account, and did the following: >> >> 1) Calculated which alsa-kcontrols that needed to change, taking into >> account the new mute as well as volume state. >> >> 2) For every kcontrol that needs to mute, mute it. >> 3) For every kcontrol that needs its volume lowered, lower it. > > I guess "the rest" (like enumerations) would go here between 3 and 4. Yes, good point. >> 4) For every kcontrol that needs its volume raised, raise it. >> 5) For every kcontrol that needs to unmute, unmute it. >> >> Note that the order of 2 - 5 is specifically meant to avoid volume bumps. >> >> I was loosely thinking (i e, this is not a promise!) to do something >> like this for PulseAudio 3.0. If I get around to do that, would such an >> algorithm also remove your N9 clicking problem, without the need for a >> mute-during-activation option? > > Quite likely. Ok, hopefully I get around to actually do this, if so, are you okay with me removing mute-during-activation at that point? -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic
