[GH-ISSUE #978] Shift Brightness Curve for Each Display #594

New issue

Closed

opened 2026-05-05 06:19:27 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:19:27 -06:00

Owner

Originally created by @waydabber on GitHub (Mar 15, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/978

Discussed in https://github.com/MonitorControl/MonitorControl/discussions/977

^{Originally posted by dhrchan March 15, 2022}
Hi,

The issue I'm having is that the maximum brightness on my MacBook is higher than the maximum brightness on my external display. I've tuned the "scale mapping curve" and "combined dimming switchover point" to sync the brightness between my MacBook and external display, but it is impossible to match the brightness at higher brightness settings due to the difference in maximum brightness for each display.

I would like to be able to shift the brightness curve for my external display. For example, if I shift the brightness curve of my external display by + 10%, it will be at maximum brightness when the brightness slider is at 90%, and it will be at 10% brightness when the brightness slider is at 0%, and so on.

That way, I can use a combined brightness slider for all displays, and the brightness of all my monitors will be synced. (Obviously, the external display won't be able to match the maximum brightness of my MacBook, but it will at least be at its maximum brightness.)

Originally created by @waydabber on GitHub (Mar 15, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/978 ### Discussed in https://github.com/MonitorControl/MonitorControl/discussions/977 <div type='discussions-op-text'> <sup>Originally posted by **dhrchan** March 15, 2022</sup> Hi, The issue I'm having is that the maximum brightness on my MacBook is higher than the maximum brightness on my external display. I've tuned the "scale mapping curve" and "combined dimming switchover point" to sync the brightness between my MacBook and external display, but it is impossible to match the brightness at higher brightness settings due to the difference in maximum brightness for each display. I would like to be able to shift the brightness curve for my external display. For example, if I shift the brightness curve of my external display by + 10%, it will be at maximum brightness when the brightness slider is at 90%, and it will be at 10% brightness when the brightness slider is at 0%, and so on. ![brightness](https://user-images.githubusercontent.com/22087718/158439190-072d0403-57c1-4483-a792-1e3bd28ad73a.png) That way, I can use a combined brightness slider for all displays, and the brightness of all my monitors will be synced. (Obviously, the external display won't be able to match the maximum brightness of my MacBook, but it will at least be at its maximum brightness.)</div>

gitea-mirror

2026-05-05 06:19:27 -06:00

closed this issue
added the
Status: Abandoned

enhancement
labels

gitea-mirror commented

2026-05-05 06:19:34 -06:00

Author

Owner

@waydabber commented on GitHub (Mar 15, 2022):

This is related to advanced absolute syncing (with calibration involved) in general. There are some other items that should go under this umbrella - see https://github.com/MonitorControl/MonitorControl/issues/943 fro example.

@waydabber commented on GitHub (Mar 15, 2022): This is related to advanced absolute syncing (with calibration involved) in general. There are some other items that should go under this umbrella - see https://github.com/MonitorControl/MonitorControl/issues/943 fro example.

gitea-mirror commented

2026-05-05 06:19:35 -06:00

Author

Owner

@stale[bot] commented on GitHub (Mar 16, 2023):

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 16, 2023): Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.