[GH-ISSUE #646] Software brightness gets reset to max brightness when also using flux #456

Closed
opened 2026-05-05 06:02:04 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @thedeagler on GitHub (Oct 1, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/646

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

The software brightness seems to work for a second before getting reset to max brightness. I've noticed that if I disable flux, the problem goes away. Not sure if it's possible to have two apps controlling monitor brightness, but my guess is that flux is updating the colors every second, and perhaps it's not possible to override.

Steps to reproduce

  1. Enable flux
  2. Change brightness using software dimming
  3. Observe momentary dimming ~1s before the monitor returns to original brightness.

Expected behavior

Dimming stays at the set level.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 11.6 big sur
- Mac model: imac pro
- MonitorControl version: 3.1.1 b3096
- Monitor(s): Lenovo Y27q-20
- Apple Silicon/M1 (yes or no): no
Originally created by @thedeagler on GitHub (Oct 1, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/646 ### 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 The software brightness seems to work for a second before getting reset to max brightness. I've noticed that if I disable flux, the problem goes away. Not sure if it's possible to have two apps controlling monitor brightness, but my guess is that flux is updating the colors every second, and perhaps it's not possible to override. ### Steps to reproduce 1. Enable flux 2. Change brightness using software dimming 3. Observe momentary dimming ~1s before the monitor returns to original brightness. ### Expected behavior Dimming stays at the set level. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 11.6 big sur - Mac model: imac pro - MonitorControl version: 3.1.1 b3096 - Monitor(s): Lenovo Y27q-20 - Apple Silicon/M1 (yes or no): no ```
Author
Owner

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

Yes, this is a problem, MonitorControl and f.lux can't work together as both are trying to manipulate the gamma tables and cancel each other out, f.lux being the more aggressive one. I recommend using Night Shift instead. For use cases when Night Shift is not an option (for example Night Shift is disabled on 'TV as a monitor' scenarios), we can add a feature for color temperature presets + a timer when to change presets - replicating Night Shift functionality. If the other devs approve this as scope, we can make it happen.

<!-- gh-comment-id:932463240 --> @waydabber commented on GitHub (Oct 1, 2021): Yes, this is a problem, MonitorControl and f.lux can't work together as both are trying to manipulate the gamma tables and cancel each other out, f.lux being the more aggressive one. I recommend using Night Shift instead. For use cases when Night Shift is not an option (for example Night Shift is disabled on 'TV as a monitor' scenarios), we can add a feature for color temperature presets + a timer when to change presets - replicating Night Shift functionality. If the other devs approve this as scope, we can make it happen.
Author
Owner

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

I'll this move over to discussion as this f.lux issue comes up from time to time and it is educational.

<!-- gh-comment-id:932464541 --> @waydabber commented on GitHub (Oct 1, 2021): I'll this move over to discussion as this f.lux issue comes up from time to time and it is educational.
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#456
No description provided.