[GH-ISSUE #718] Save/restore brightness value in software mode #470

Closed
opened 2026-05-05 06:04:57 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @xand3r40r93 on GitHub (Oct 16, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/718

Originally assigned to: @waydabber on GitHub.

Before opening the issue, have you...?

  • Searched for existing issues

I using my monitor on full brightness and controlling brightness in software mode. For my monitor, it's like 'flicker free' mode. After system restart brightness value always is 100%.

Describe the solution you'd like

Just save/restore brightness value in software mode at startup or closing program.

Describe alternatives you've considered

...

Anything else?

No response

Originally created by @xand3r40r93 on GitHub (Oct 16, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/718 Originally assigned to: @waydabber on GitHub. ### Before opening the issue, have you...? - [X] Searched for existing issues ### Is your feature request related to a problem? Please describe I using my monitor on full brightness and controlling brightness in software mode. For my monitor, it's like 'flicker free' mode. After system restart brightness value always is 100%. ### Describe the solution you'd like Just save/restore brightness value in software mode at startup or closing program. ### Describe alternatives you've considered ... ### Anything else? _No response_
gitea-mirror 2026-05-05 06:04:57 -06:00
Author
Owner

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

The app actually saves software brightness but to avoid behavior that might be puzzling to some users, the saved software dimming values are restored only upon wake or display configuration change and not during application startup (it is intentional, most people probably don't restart their macs or the app very often anyway but use sleep instead). The Upon startup or wake/Apply last saved values are relevant only for the DDC component of the brightness, not the software component (when waking from sleep, software dimming is reapplied regardless of this setting but on startup it is never reapplied). It might be reasonable to change how this works (we should clarify that the Upon startup or wake option is only for DDC only and there could be a setting about reapplying software dimming upon app startup).

<!-- gh-comment-id:945010204 --> @waydabber commented on GitHub (Oct 16, 2021): The app actually saves software brightness but to avoid behavior that might be puzzling to some users, the saved software dimming values are restored only upon wake or display configuration change and not during application startup (it is intentional, most people probably don't restart their macs or the app very often anyway but use sleep instead). The `Upon startup or wake`/`Apply last saved values` are relevant only for the DDC component of the brightness, not the software component (when waking from sleep, software dimming is reapplied regardless of this setting but on startup it is never reapplied). It might be reasonable to change how this works (we should clarify that the `Upon startup or wake` option is only for DDC only and there could be a setting about reapplying software dimming upon app startup).
Author
Owner

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

I did some tweaks here and there + changed the behavior. Now if Upon startup or wake/Apply last saved values is selected, then software and combined brightness will be restored upon app start. Since this is not a default startup option and also there is a separate option for allowing zero brightness with a proper warning, this seems to be acceptable.

<!-- gh-comment-id:945078554 --> @waydabber commented on GitHub (Oct 17, 2021): I did some tweaks here and there + changed the behavior. Now if `Upon startup or wake`/`Apply last saved values` is selected, then software and combined brightness will be restored upon app start. Since this is not a default startup option and also there is a separate option for allowing zero brightness with a proper warning, this seems to be acceptable.
Author
Owner

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

Screen Shot 2021-10-17 at 11 23 46
<!-- gh-comment-id:945079619 --> @waydabber commented on GitHub (Oct 17, 2021): <img width="842" alt="Screen Shot 2021-10-17 at 11 23 46" src="https://user-images.githubusercontent.com/37590873/137620936-f40a0420-0eec-43de-9d53-afdfac166c85.png">
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#470
No description provided.