[GH-ISSUE #1679] Settings not saved after startup #935

New issue

Closed

opened 2026-05-05 06:54:51 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

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

Owner

Originally created by @stano-vittorio on GitHub (Nov 16, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1679

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

Hello everyone! I would like to note that the settings in the monitor --> advanced settings section do not remain saved after macOS starts up after restarting or shutdown. In particular, the value I set in the Max DDC is not saved. Is there anything that can be done?

Steps to reproduce

Set advanced settings parameters.
Restart macOS.
Check previous settings or adjust the brightness with the keyboard and you will see that it goes beyond the previously set threshold.

Expected behavior

Advanced settings should remain saved. In particular, I set a maximum brightness limit of 80 and beyond that value should not go (the brightness is adjusted with the keyboard).

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 15.1 (24B83)
- Mac model: Mac mini M1
- MonitorControl version: 4.3.3 Build 7123
- Monitor(s): LG HDR WQHD
- Apple Silicon/M1 (yes or no): yes

Originally created by @stano-vittorio on GitHub (Nov 16, 2024). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1679 ![Screenshot 2024-11-16 alle 19 28 50](https://github.com/user-attachments/assets/1abd239d-f06e-40cf-95b0-7c46aa3851c4) ### 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 Hello everyone! I would like to note that the settings in the monitor --> advanced settings section do not remain saved after macOS starts up after restarting or shutdown. In particular, the value I set in the Max DDC is not saved. Is there anything that can be done? ### Steps to reproduce 1. Set advanced settings parameters. 2. Restart macOS. 3. Check previous settings or adjust the brightness with the keyboard and you will see that it goes beyond the previously set threshold. ### Expected behavior Advanced settings should remain saved. In particular, I set a maximum brightness limit of 80 and beyond that value should not go (the brightness is adjusted with the keyboard). ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 15.1 (24B83) - Mac model: Mac mini M1 - MonitorControl version: 4.3.3 Build 7123 - Monitor(s): LG HDR WQHD - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror closed this issue

2026-05-05 06:54:53 -06:00

gitea-mirror commented

2026-05-05 06:54:55 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 18, 2024):

Sorry for not responding to this. I assume the issue was resolved then.

@waydabber commented on GitHub (Nov 18, 2024): Sorry for not responding to this. I assume the issue was resolved then.

gitea-mirror commented

2026-05-05 06:54:56 -06:00

Author

Owner

@stano-vittorio commented on GitHub (Nov 18, 2024):

Thanks for the answer. After a few restarts I checked and the settings remain saved. A question, if I use the app on a macbook and I want the app to control only the external monitor and the internal one to control it directly from the physical buttons, is it possible to separate the two things?

@stano-vittorio commented on GitHub (Nov 18, 2024): Thanks for the answer. After a few restarts I checked and the settings remain saved. A question, if I use the app on a macbook and I want the app to control only the external monitor and the internal one to control it directly from the physical buttons, is it possible to separate the two things?

gitea-mirror commented

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

Author

Owner

@waydabber commented on GitHub (Nov 19, 2024):

No, because if you want to control the external display using the keyboard, the app must assume control over the native keys thus it needs to control the internal display as well.

@waydabber commented on GitHub (Nov 19, 2024): No, because if you want to control the external display using the keyboard, the app must assume control over the native keys thus it needs to control the internal display as well.

gitea-mirror referenced this issue

2026-05-05 07:08:03 -06:00

[PR #935] [MERGED] German translation update #1216