[GH-ISSUE #533] brightness jumps back to original #410

New issue

Closed

opened 2026-05-05 05:57:05 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:57:05 -06:00

Owner

Originally created by @saar120 on GitHub (Aug 23, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/533

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 changing brightness of external display - the brightness jumps back to the original setting.
tried using the app or the keyboard buttons.

Steps to reproduce

change brightness

Expected behavior

change brightness

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 11.5.2
- Mac model: MacBook air M1
- MonitorControl version:v3.0.0 rc1
- Monitor(s): msi optix g27cq4
- Apple Silicon/M1 (yes or no): yes

Originally created by @saar120 on GitHub (Aug 23, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/533 ### 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 changing brightness of external display - the brightness jumps back to the original setting. tried using the app or the keyboard buttons. ### Steps to reproduce change brightness ### Expected behavior change brightness ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 11.5.2 - Mac model: MacBook air M1 - MonitorControl version:v3.0.0 rc1 - Monitor(s): msi optix g27cq4 - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror

2026-05-05 05:57:05 -06:00

closed this issue
added the
monitor Issue

feedback needed from reporter
labels

gitea-mirror commented

2026-05-05 05:57:11 -06:00

Author

Owner

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

Hi, there are some displays with problematic firmwares that do this (for example some older LG UHD displays). Some do this only if a certain feature is enabled in the Display's own menu system (like automatic brightness, automatic power saving, intelligent contrast, test/game/web etc. view mode, or some other screen management feature with some vendor specific marketing name).

You should try m1ddc (see the monitor troubleshooting wiki page) to see if the behavior is the same or maybe try to reset the display to see if it helps.

If nothing helps, you can turn off "Use hardware DDC control" in the Displays tab for brightness control using gamma table manipulation.

Please let me know if you have any luck! Thank you!

@waydabber commented on GitHub (Aug 23, 2021): Hi, there are some displays with problematic firmwares that do this (for example some older LG UHD displays). Some do this only if a certain feature is enabled in the Display's own menu system (like automatic brightness, automatic power saving, intelligent contrast, test/game/web etc. view mode, or some other screen management feature with some vendor specific marketing name). You should try m1ddc (see the monitor troubleshooting wiki page) to see if the behavior is the same or maybe try to reset the display to see if it helps. If nothing helps, you can turn off "Use hardware DDC control" in the Displays tab for brightness control using gamma table manipulation. Please let me know if you have any luck! Thank you!

gitea-mirror commented

2026-05-05 05:57:13 -06:00

Author

Owner

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

Hi there, I'll close this issue but please feel free to comment and let me know it if I can assist fixing this problem in any way! Thank you!

@waydabber commented on GitHub (Aug 25, 2021): Hi there, I'll close this issue but please feel free to comment and let me know it if I can assist fixing this problem in any way! Thank you!