[GH-ISSUE #1816] Volume control reverts to non-fine scale steps #1001

New issue

Open

opened 2026-05-05 07:01:13 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 07:01:13 -06:00

Owner

Originally created by @zackatap on GitHub (Nov 6, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1816

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

When I change the volume, it will use large steps each time I press the keyboard buttons. Once I open the app, change any random dropdown setting and go back, it then goes back to fine scale volume control.

Steps to reproduce

Expected behavior

Stay on fine tune

Anything else?

No response

Environment Information (please complete the following information)

- macOS version:
- Mac model:
- MonitorControl version:
- Monitor(s):
- Apple Silicon/M1 (yes or no): no

Originally created by @zackatap on GitHub (Nov 6, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1816 ### Before opening the issue, have you...? - [x] Searched for existing issues - [x] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [x] Updated MonitorControl to the latest version (if applicable) ### Describe the bug When I change the volume, it will use large steps each time I press the keyboard buttons. Once I open the app, change any random dropdown setting and go back, it then goes back to fine scale volume control. ### Steps to reproduce When I change the volume, it will use large steps each time I press the keyboard buttons. Once I open the app, change any random dropdown setting and go back, it then goes back to fine scale volume control. ### Expected behavior Stay on fine tune ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: - Mac model: - MonitorControl version: - Monitor(s): - Apple Silicon/M1 (yes or no): no ```

gitea-mirror added the

bug

unable to reproduce

labels 2026-05-05 07:01:13 -06:00

gitea-mirror commented

2026-05-05 07:01:16 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 16, 2025):

I don't fully understand the issue. There should be a setting to force fine scale in the app (works only if the keyboard events are handled by the app). Doesn't this work?

@waydabber commented on GitHub (Nov 16, 2025): I don't fully understand the issue. There should be a setting to force fine scale in the app (works only if the keyboard events are handled by the app). Doesn't this work?

gitea-mirror commented

2026-05-05 07:01:18 -06:00

Author

Owner

@zackatap commented on GitHub (Jan 5, 2026):

I don't fully understand the issue. There should be a setting to force fine scale in the app (works only if the keyboard events are handled by the app). Doesn't this work?

It works, but often times will not be fine scale, for example my monitor will jump by +4 each time I increase the volume. I have to go into MonitorControl settings, then do something like change any dropdown setting, and change it back, then it refreshes and I can increase by 1 now again.

@zackatap commented on GitHub (Jan 5, 2026): > I don't fully understand the issue. There should be a setting to force fine scale in the app (works only if the keyboard events are handled by the app). Doesn't this work? It works, but often times will not be fine scale, for example my monitor will jump by +4 each time I increase the volume. I have to go into MonitorControl settings, then do something like change any dropdown setting, and change it back, then it refreshes and I can increase by 1 now again.

gitea-mirror commented

2026-05-05 07:01:20 -06:00

Author

Owner

@waydabber commented on GitHub (Feb 9, 2026):

I see. This might be a bug then, although not entirely sure why this happens or how to reproduce it.

If you generally want the monitor to have finer control on the lower range, a better solution might be to limit the DDC range in advanced settings.

@waydabber commented on GitHub (Feb 9, 2026): I see. This might be a bug then, although not entirely sure why this happens or how to reproduce it. If you generally want the monitor to have finer control on the lower range, a better solution might be to limit the DDC range in advanced settings.