# Volume control via mpc / ncmpc sometimes is ignored

**URL:** <https://discourse.mopidy.com/t/volume-control-via-mpc-ncmpc-sometimes-is-ignored/3298>\
**Category:** Misc\
**Created:** [June 9, 2019, 7:50am UTC](https://discourse.mopidy.com/t/volume-control-via-mpc-ncmpc-sometimes-is-ignored/3298 "2019-06-09T07:50:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![retrofreak83](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/retrofreak83/32/1261_2.png) [@retrofreak83](https://discourse.mopidy.com/u/retrofreak83)\
**Post date:** [June 9, 2019, 7:50am UTC](https://discourse.mopidy.com/t/volume-control-via-mpc-ncmpc-sometimes-is-ignored/3298/1 "2019-06-09T07:50:35Z")

</div>

I installed mopidy as a replacement for mpd. Installed versions are:  
mopidy/stable,now 2.2.2-1 all  
mopidy-alsamixer/stable 1.0.3-3 all

I use volume control via mpc from remote machines. I always send commands “volume -5” and “volume +5”. But sometimes, these commands seem to be ignored.  
Even when I log in to the mopidy machine and try to control the volume via local ncmpc, volume control commands sometimes are ignored (I have alsamixer open in parallel to see if there are changes).  
Also, what from my point of view really should’nt happen, is a misalignment between alsamixer’s volume and the volume reported by ncmpc. For example,  
alsamixer says 76%, ncmpc says 84%.  
I push the right cursor key for “louder” in ncmpc -\> nothing happens.  
I push it again -\> nothing happens.  
I push it a third time: the sound card as reported by alsamixer is spontaneously set to 80%, volume in ncmpc is reported to be 87%.  
Iset the alsamixer min\_/max\_ volume values to 0 and 100, scale to linear, so there shouldn’t be problems.

To conclude, I see the following pattern:  
For example, when repeatedly issuing “vol +”-commands, I see that a volume change is only applied every second/third time and then with 2 - 3% mostly.

Nevertheless, there is a discrepance between the volume percentage reported to mpd-clients (mpc / ncmpc) and the volume which is indeed set in alsamixer.

From my point of view, I consider this a bug. However, no error messages or warnings are logged in the mopidy log when controlling the volume.  
Any hints?

---

<div class="post-metadata">

**Author:** ![retrofreak83](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/retrofreak83/32/1261_2.png) [@retrofreak83](https://discourse.mopidy.com/u/retrofreak83)\
**Post date:** [August 23, 2019, 5:36am UTC](https://discourse.mopidy.com/t/volume-control-via-mpc-ncmpc-sometimes-is-ignored/3298/2 "2019-08-23T05:36:40Z")

</div>

No one? Really? This is a really annoying problem :-/

---

<div class="post-metadata">

**Author:** ![shanwa](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/shanwa/32/1348_2.png) [@shanwa](https://discourse.mopidy.com/u/shanwa)\
**Post date:** [November 25, 2019, 2:52am UTC](https://discourse.mopidy.com/t/volume-control-via-mpc-ncmpc-sometimes-is-ignored/3298/3 "2019-11-25T02:52:08Z")

</div>

Does the same thing happen when you do the following

Show the current volume number

> mpc volume

If it’s say 50% then just changing it to say 55% by

> mpc volume 55

I’ve always done it this way and never had any issues except it saving that volume if I were to reboot. The only method to saving the volume was to edit /etc/mopidy/mopidy.conf or through the settings webpage.

---

<div class="post-metadata">

**Author:** ![retrofreak83](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/retrofreak83/32/1261_2.png) [@retrofreak83](https://discourse.mopidy.com/u/retrofreak83)\
**Post date:** [November 25, 2019, 1:39pm UTC](https://discourse.mopidy.com/t/volume-control-via-mpc-ncmpc-sometimes-is-ignored/3298/4 "2019-11-25T13:39:44Z")

</div>

Yes, it at least does some weird things also. E.g., oftentimes, the volume actually set differs 1-2% from the submitted value.  
Example:  
mpc volume 3  
sets the volume to 2%.