[GH-ISSUE #666] Contrast currently defaults to 100% and it gets applied upon wake when 'Apply last saved values to the display' is selected #458

New issue

Closed

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

gitea-mirror commented

2026-05-05 06:03:04 -06:00

Owner

Originally created by @waydabber on GitHub (Oct 4, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/666

Originally assigned to: @waydabber on GitHub.

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

If contrast is not read from the display it currently defaults to 100% if the user does not override it manually - which might not happen since contrast control is not enabled by default. When 'Apply last saved values to the display' is selected, this 100% is being written to the display upon startup or wake. This is confusing.

Steps to reproduce

See description.

Expected behavior

If contrast is undefined, it should be left undefined and should not be written on wake/startup - the best would be a neutral behavior in general if reading is not enabled - until the user does not attempt to change contrast intentionally, it should not be initialized or applied ever - if the user enables the slider or attempts to change contrast via keyboard, then a default of 75% should be implied if no contrast data is read from the display.

Alternatively, simply a common 75% contrast default should be applied instead of 100%. Current defaults for brightness 100% and volume 12,5% should remain as they are.

Anything else?

n/a

Environment Information (please complete the following information)

- macOS version: Monterey
- Mac model: MBA M1
- MonitorControl version: 4.0.0-beta1
- Monitor(s): any
- Apple Silicon/M1 (yes or no): yes

Originally created by @waydabber on GitHub (Oct 4, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/666 Originally assigned to: @waydabber on GitHub. ### 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 If contrast is not read from the display it currently defaults to 100% if the user does not override it manually - which might not happen since contrast control is not enabled by default. When 'Apply last saved values to the display' is selected, this 100% is being written to the display upon startup or wake. This is confusing. ### Steps to reproduce See description. ### Expected behavior If contrast is undefined, it should be left undefined and should not be written on wake/startup - the best would be a neutral behavior in general if reading is not enabled - until the user does not attempt to change contrast intentionally, it should not be initialized or applied ever - if the user enables the slider or attempts to change contrast via keyboard, then a default of 75% should be implied if no contrast data is read from the display. Alternatively, simply a common 75% contrast default should be applied instead of 100%. Current defaults for brightness 100% and volume 12,5% should remain as they are. ### Anything else? n/a ### Environment Information (please complete the following information) ```markdown - macOS version: Monterey - Mac model: MBA M1 - MonitorControl version: 4.0.0-beta1 - Monitor(s): any - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror

2026-05-05 06:03:04 -06:00

closed this issue
added the
bug

done

beta
labels

gitea-mirror commented

2026-05-05 06:03:12 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 4, 2021):

I changed the default to 75% in the latest PR but a better approach is to make the app register if contrast is actually ever touched and act accordingly. This still needs some work.

@waydabber commented on GitHub (Oct 4, 2021): I changed the default to 75% in the latest PR but a better approach is to make the app register if contrast is actually ever touched and act accordingly. This still needs some work.

gitea-mirror commented

2026-05-05 06:03:13 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 5, 2021):

The app now registers if a DDC setting is ever changed by the user (isTouched) and writes only touched values when Apply last saved values to the display is enabled. If a command is touched, it can only be untouched with a preferences reset.

@waydabber commented on GitHub (Oct 5, 2021): The app now registers if a DDC setting is ever changed by the user (`isTouched`) and writes only touched values when `Apply last saved values to the display` is enabled. If a command is touched, it can only be untouched with a preferences reset.

gitea-mirror referenced this issue

2026-05-05 07:04:34 -06:00

[PR #458] [CLOSED] Change Chinese(simplified) to Chinese(traditional)(tw) and change some words #1098