On Thu, Nov 06, 2014 at 04:11:12PM -0800, Kuninori Morimoto wrote:
Correct me if I'm wrong but I think what's confusing me here is that what I'd expect to happen is that setting the ramp rate would cause any volume change done by the user to ramp to the target volume (or mute) but it looks like what's actually happening is that the ramp control is providing an additional layer of volume control on top of the normal volume control.
Sorry for my poor explanation. Yes, you are correct. Volume Ramp chenges [ramp layer] (0% - 100%) [ramp layer] is always 100% if you don't use Volume Ramp.
[Normal Volume] x [ramp layer] = output
Please let me better/understandable naming.
OK, right. In that case what I'd expect is that the only control the user gets is of the ramp rate and then if that's configured any time the volume is changed the driver will ensure that the change is implemented with a ramp - that'd correspond to the normal implementation of this in other devices (usually the hardware just does this so we don't have to do anything special in software).