Volume mixer ramp is too shallow

@Ashok Sidipotu, I'm seeing a bit of odd behavior with the mixer volume controls.  I've been scratching my head a bit about the master volume not getting set to 0.5 when agl-service-audiomixer starts (as it does an explicit set), and then when checking with audio-mixer-test, I was seeing no changes to the volume mixer value when poking it via VSS.  The aha moment was when I started playing some audio, changes started becoming visible (in both audio-mixer-test and "wpctl status" output).  From some experimenting, the same is not true of the equalizer gain values or the mute setting of the mixers, those can be changed before any playback happens. 

I have seen this issue as well. I will take a look at it, I hope this is not a show stopper for the CES, please let us know if it is.

Another problem that I'm not entirely sure is related is that trying to set a mixer volume with audio-mixer-test (e.g. "audio-mixer-test v 0.5" or "audio-mixer-test -i 0 -v 0.5") hangs for me here...

I can see this issue as well but it is like the first issue that you talked about. I mean I see this issue when I boot up but when I play something on that control, this issue cannot be seen further.

The reason why we see the issue in first place is that the test app waits for the volume change to be published, only then it is sure that the volume change is applied. for some reason the volume change wouldn't go through and the callback will not be fired till the time some playback happens on that endpoint/device. Test app is waiting for eternity for the callback causing it to hang.

@Ashok Sidipotu, I'm seeing a bit of odd behavior with the mixer volume controls.  I've been scratching my head a bit about the master volume not getting set to 0.5 when agl-service-audiomixer starts (as it does an explicit set), and then when checking with audio-mixer-test, I was seeing no changes to the volume mixer value when poking it via VSS.  The aha moment was when I started playing some audio, changes started becoming visible (in both audio-mixer-test and "wpctl status" output).  From some experimenting, the same is not true of the equalizer gain values or the mute setting of the mixers, those can be changed before any playback happens.  Another problem that I'm not entirely sure is related is that trying to set a mixer volume with audio-mixer-test (e.g. "audio-mixer-test v 0.5" or "audio-mixer-test -i 0 -v 0.5") hangs for me here...

@Scott Murray pls use "audio-mixer-test -p" to get all the controls and their values. This is is made available with https://gerrit.automotivelinux.org/gerrit/c/apps/agl-service-audiomixer/+/29512

Another question, is there a CLI command to see the status of the added controls, I don't see anything in the "wpctl status" or an "wpctl inspect" of the default output?

@George Kiagiadakis, after experimenting with my USB Jabra speaker that I have used in the past just now, I'd still say the behavior is different than it used to be.  I have to crank the Jabra to pretty much max volume to even get any discernible output at a setting of 10-20%, and that ends up with 50-60% being quite loud and 100% seems likely to be getting into clipping territory on some content.  I do not remember having this problem previously.