github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #468] No Volume nor Brightness control Via the Function Keys or Mouse #371

New issue

Closed

opened 2026-05-05 05:50:56 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 05:50:56 -06:00

Owner

Originally created by @hawkeyesutherland on GitHub (Jul 18, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/468

Originally assigned to: @waydabber on GitHub.

Checklist

I have searched for existing issues
I have looked through the Monitor Troubleshooting wiki
I have updated MonitorControl to the latest version

Describe the issue
A clear and concise description of the problem.

Expected behaviour
Based on my Dell U3421WE I would expect to be able to use the keyboard Function keys to change the volume and brightness of the monitor, on the Dell this works perfectly. My MSI Prestige PS341WU (which does not have built in Speakers) is recognised by Monitor Control yet the function keys activate the brightness up and down and volume up and down, only the brightness works, the volume does not change the external USB attached speakers.
I can only select the brightness via the menu bar and function keys. The sound volume slider does not work even though the slider is accessible and moveable.

Screenshots
https://drive.google.com/drive/folders/1dyw4MiDImxLf6_ei5MlIEo-u6_0WX1Et?usp=sharing

Additional context
Add any other context about the problem here.

Environment Information (please complete the following information):

macOS version: Big Sur 11.2.3
MonitorControl version: 2.1.0 (Build 721)
Monitor(s): Wacom Cintiq 20 WSX + MSI PS341WU + Dell U3421WE
Mac model: Mac Pro 5,1 - 12 core
Monitor Cable(s)/Connection(s): DisplayPort to USB C or Display Port to Display Port.
Apple Silicon/M1 (yes or no): No

Originally created by @hawkeyesutherland on GitHub (Jul 18, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/468 Originally assigned to: @waydabber on GitHub. **Checklist**   - [x] I have searched for existing issues - [x] I have looked through [the Monitor Troubleshooting wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [x] I have updated MonitorControl to the latest version **Describe the issue** A clear and concise description of the problem. **Expected behaviour** Based on my Dell U3421WE I would expect to be able to use the keyboard Function keys to change the volume and brightness of the monitor, on the Dell this works perfectly. My MSI Prestige PS341WU (which does not have built in Speakers) is recognised by Monitor Control yet the function keys activate the brightness up and down and volume up and down, only the brightness works, the volume does not change the external USB attached speakers. I can only select the brightness via the menu bar and function keys. The sound volume slider does not work even though the slider is accessible and moveable. **Screenshots** https://drive.google.com/drive/folders/1dyw4MiDImxLf6_ei5MlIEo-u6_0WX1Et?usp=sharing **Additional context** Add any other context about the problem here. **Environment Information (please complete the following information):** - macOS version: Big Sur 11.2.3 - MonitorControl version: 2.1.0 (Build 721) - Monitor(s): Wacom Cintiq 20 WSX + MSI PS341WU + Dell U3421WE - Mac model: Mac Pro 5,1 - 12 core - Monitor Cable(s)/Connection(s): DisplayPort to USB C or Display Port to Display Port. - Apple Silicon/M1 (yes or no): No

gitea-mirror

2026-05-05 05:50:56 -06:00

closed this issue
added the
done

monitor Issue

feedback needed from reporter
labels

gitea-mirror commented

2026-05-05 05:51:04 -06:00

Author

Owner

@hawkeyesutherland commented on GitHub (Jul 18, 2021):

So instead of routing the speakers through the monitor I have fed them through the machine and that works.
I have also been able to get the brightness to work by changing the Function key settings.

I have a new issue. I clicked on the Hide OSD and now I cannot get the OSD to appear on the monitor via the buttons on the back anymore.
I have tried putting new firmware on the monitor and unplugging it (turning it off and on again) but the OSD via the rear buttons is missing.
This is all via the Mac.
When I go into Windows 10 via bootcamp I can open the OSD program to access the OSD but there is no setting in windows to unhide the OSD.
Problem is I work on the Mac 99% of the time so need the OSD to control the colours, calibration, other settings.
Can you help me?

@hawkeyesutherland commented on GitHub (Jul 18, 2021): So instead of routing the speakers through the monitor I have fed them through the machine and that works. I have also been able to get the brightness to work by changing the Function key settings. I have a new issue. I clicked on the Hide OSD and now I cannot get the OSD to appear on the monitor via the buttons on the back anymore. I have tried putting new firmware on the monitor and unplugging it (turning it off and on again) but the OSD via the rear buttons is missing. This is all via the Mac. When I go into Windows 10 via bootcamp I can open the OSD program to access the OSD but there is no setting in windows to unhide the OSD. Problem is I work on the Mac 99% of the time so need the OSD to control the colours, calibration, other settings. Can you help me?

gitea-mirror commented

2026-05-05 05:51:05 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 20, 2021):

Hi. I don't fully understand the issue. You say that you clidked Hide OSD which made the display to hide the OSD permanently? Interesting, that's super rare (normally it should just hide the OSD once if it appeared).

The upcoming 3.0.0 release will get rid of the "Hide OSD" function as a DDC command (it will hide the macOS volume OSD instead) so this should be solved by that. The current 3.0.0 beta8 still does not have this, but a new beta9 or RC1 should be available very soon. Please let me know if that fixes the problem! Thank you!

@waydabber commented on GitHub (Aug 20, 2021): Hi. I don't fully understand the issue. You say that you clidked Hide OSD which made the display to hide the OSD permanently? Interesting, that's super rare (normally it should just hide the OSD once if it appeared). The upcoming 3.0.0 release will get rid of the "Hide OSD" function as a DDC command (it will hide the macOS volume OSD instead) so this should be solved by that. The current 3.0.0 beta8 still does not have this, but a new beta9 or RC1 should be available very soon. Please let me know if that fixes the problem! Thank you!

gitea-mirror commented

2026-05-05 05:51:06 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Hi, we have relased the 3.0.0 version. Could you please test if this issue is resolved and report back? Thank you!

@waydabber commented on GitHub (Aug 21, 2021): Hi, we have relased the [3.0.0 version](https://github.com/MonitorControl/MonitorControl/releases/tag/v3.0.0-rc1). Could you please test if this issue is resolved and report back? Thank you!

gitea-mirror commented

2026-05-05 05:51:07 -06:00

Author

Owner

@dserodio commented on GitHub (Aug 24, 2021):

I'm using 3.0.0 and the "keyboard" (Touchbar, actually) brightness settings only control the brightness for Macbook Pro's builtin display, not for the external monitors (Dell SE2216H and LG 29WK600-W).
"Enable keyboard control for display" is set for all 3 displays, as is "Change Brightness and Volume for all screens".

Should I file a new issue?

Thanks!

@dserodio commented on GitHub (Aug 24, 2021): I'm using 3.0.0 and the "keyboard" (Touchbar, actually) brightness settings only control the brightness for Macbook Pro's builtin display, not for the external monitors (Dell SE2216H and LG 29WK600-W). "Enable keyboard control for display" is set for all 3 displays, as is "Change Brightness and Volume for all screens". Should I file a new issue? Thanks!

gitea-mirror commented

2026-05-05 05:51:10 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 25, 2021):

Hi,

The brightness slider is not currently supported only the brightness keys. We plan supporting it in a way (full support is not possible since this is a locked part of the os):

https://github.com/MonitorControl/MonitorControl/issues/274

Is this what you had in mind?

Thanks!

@waydabber commented on GitHub (Aug 25, 2021): Hi, The brightness slider is not currently supported only the brightness keys. We plan supporting it in a way (full support is not possible since this is a locked part of the os): https://github.com/MonitorControl/MonitorControl/issues/274 Is this what you had in mind? Thanks!

gitea-mirror commented

2026-05-05 05:51:12 -06:00

Author

Owner

@dserodio commented on GitHub (Aug 26, 2021):

The brightness slider is not currently supported only the brightness keys. We plan supporting it in a way (full support is not possible since this is a locked part of the os):

#274

Is this what you had in mind?

Yes, that's what I was looking for. Thanks!

@dserodio commented on GitHub (Aug 26, 2021): > The brightness slider is not currently supported only the brightness keys. We plan supporting it in a way (full support is not possible since this is a locked part of the os): > > #274 > > Is this what you had in mind? Yes, that's what I was looking for. Thanks!

gitea-mirror commented

2026-05-05 05:51:14 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 26, 2021):

All right. I'll close this issue then and you can follow #274 to see if that is resolved. Thank you!

@waydabber commented on GitHub (Aug 26, 2021): All right. I'll close this issue then and you can follow #274 to see if that is resolved. Thank you!