[GH-ISSUE #715] Further Lowering Brightness via Software Dimming Auto resets #471

Closed
opened 2026-05-05 06:04:58 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @shamal on GitHub (Oct 14, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/715

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

I have enabled Further lower brightness via software dimming.

When I 'Further' lower the brightness after normal brightness reaches 0 screen dims, and after around 1 - 2 seconds brightness returns to normal brightness 0 level.

Steps to reproduce

  1. Enable Further lower brightness via software dimming on preferences → general.
  2. Further, lower the brightness using either keyboard or menu bar slider
  3. Observe the brightness return to normal brightness 0 (software dimming resets)

Expected behavior

Expected behavior is for the software dimming to retain at dimmed state rather than resetting.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: Catalina 10.15.7 (19H1419)
- Mac model: MacBook Pro (16-inch, 2019)
- MonitorControl version: Version 3.1.1. Build 3096 - Intel
- Monitor(s): LG 34WN80C 34” 
- Apple Silicon/M1 (yes or no): no
Originally created by @shamal on GitHub (Oct 14, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/715 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 I have enabled `Further lower brightness via software dimming`. When I 'Further' lower the brightness after normal brightness reaches 0 screen dims, and after around 1 - 2 seconds brightness returns to normal brightness 0 level. ### Steps to reproduce 1. Enable `Further lower brightness via software dimming` on preferences → general. 2. Further, lower the brightness using either keyboard or menu bar slider 3. Observe the brightness return to normal brightness 0 (software dimming resets) ### Expected behavior Expected behavior is for the software dimming to retain at dimmed state rather than resetting. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: Catalina 10.15.7 (19H1419) - Mac model: MacBook Pro (16-inch, 2019) - MonitorControl version: Version 3.1.1. Build 3096 - Intel - Monitor(s): LG 34WN80C 34” - Apple Silicon/M1 (yes or no): no ```
Author
Owner

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

Hi, you should try the latest version v4.0.0. After a few tries it will inform you if the app detects interference from an other apps (main culprit is usually f.lux). In v4.0.0 you can also change the software dimming method from gamma to shade in order for MonitorControl to coexist with f.lux by activating Avoid gamma table manipulation under Displays.

Screen Shot 2021-10-14 at 23 28 49

(please note that the current 4.0.0-rc1 build has the Show advanced settings in Preferences/General - you need to activate that in order to see the above-mentioned option).

Please let me know if this helps. Thank you!

<!-- gh-comment-id:943750053 --> @waydabber commented on GitHub (Oct 14, 2021): Hi, you should try [the latest version v4.0.0](https://github.com/MonitorControl/MonitorControl/releases/tag/v4.0.0-rc1). After a few tries it will inform you if the app detects interference from an other apps (main culprit is usually f.lux). In v4.0.0 you can also change the software dimming method from gamma to shade in order for MonitorControl to coexist with f.lux by activating `Avoid gamma table manipulation` under Displays. <img width="842" alt="Screen Shot 2021-10-14 at 23 28 49" src="https://user-images.githubusercontent.com/37590873/137398238-3362dd55-6df3-41b8-94fd-198b183968ac.png"> (please note that the current 4.0.0-rc1 build has the `Show advanced settings` in Preferences/General - you need to activate that in order to see the above-mentioned option). Please let me know if this helps. Thank you!
Author
Owner

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

Hi @shamal , I hope the info above helped. I'll close this issue but let me know if you have results. Thank you!

<!-- gh-comment-id:944073089 --> @waydabber commented on GitHub (Oct 15, 2021): Hi @shamal , I hope the info above helped. I'll close this issue but let me know if you have results. Thank you!
Author
Owner

@shamal commented on GitHub (Oct 15, 2021):

Hi @waydabber, yes issue resolved. And the culprit was indeed f.lux. Thank you.

<!-- gh-comment-id:944076446 --> @shamal commented on GitHub (Oct 15, 2021): Hi @waydabber, yes issue resolved. And the culprit was indeed f.lux. Thank you.
Author
Owner

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

Great, thanks for the feedback!

<!-- gh-comment-id:944115342 --> @waydabber commented on GitHub (Oct 15, 2021): Great, thanks for the feedback!
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#471
No description provided.