[GH-ISSUE #878] Min/max brightness for built-in display #548

New issue

Closed

opened 2026-05-05 06:13:14 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:13:14 -06:00

Owner

Originally created by @steo-ml on GitHub (Jan 7, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/878

Before opening the issue, have you...?

Searched for existing issues

I've came across issues #159, #310, #418, but they don't quite address the issue I have. My Macbook's built-in display has a brightness range that is bigger than the external monitor's, so when they're both perfectly synced, the Macbook display would be darker at low brightness, and then brighter at high brightness. If I could set min and max for the Macbook, then that would perfectly solve the problem, but it's not available:

I had somewhat of a workaround, which is to set a "DDC max" of the external monitor to a value higher than 100. That way when the Macbook reaches around 70% brightness, the external display would be at max brightness, perfect. However, I can't do the same for DDC min, as it doesn't accept a negative value.

Describe the solution you'd like

Have the ability to set a min and max brightness for the built-in display (I'm not sure if this is possible, cause if it was, you guys probably would've implemented it right?),

OR,

Have the ability to set a negative value for "DDC min" on the external monitor

Describe alternatives you've considered

Alternatives described above

Anything else?

No response

Originally created by @steo-ml on GitHub (Jan 7, 2022). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/878 ### Before opening the issue, have you...? - [X] Searched for existing issues ### Is your feature request related to a problem? Please describe I've came across issues #159, #310, #418, but they don't quite address the issue I have. My Macbook's built-in display has a brightness range that is bigger than the external monitor's, so when they're both perfectly synced, the Macbook display would be darker at low brightness, and then brighter at high brightness. If I could set min and max for the Macbook, then that would perfectly solve the problem, but it's not available: ![image](https://user-images.githubusercontent.com/80666855/148526097-1674c483-16c3-43eb-82d2-006161ddd59b.png) I had somewhat of a workaround, which is to set a "DDC max" of the external monitor to a value higher than 100. That way when the Macbook reaches around 70% brightness, the external display would be at max brightness, perfect. However, I can't do the same for DDC min, as it doesn't accept a negative value. ### Describe the solution you'd like Have the ability to set a min and max brightness for the built-in display (I'm not sure if this is possible, cause if it was, you guys probably would've implemented it right?), OR, Have the ability to set a negative value for "DDC min" on the external monitor ### Describe alternatives you've considered Alternatives described above ### Anything else? _No response_

gitea-mirror

2026-05-05 06:13:14 -06:00

closed this issue
added the
Status: Abandoned

enhancement
labels

gitea-mirror commented

2026-05-05 06:13:21 -06:00

Author

Owner

@waydabber commented on GitHub (Jan 7, 2022):

It is possible, but only for the adjustments that go through MonitorControl (if you use the native sliders or controls it will be disregarded).

@waydabber commented on GitHub (Jan 7, 2022): It is possible, but only for the adjustments that go through MonitorControl (if you use the native sliders or controls it will be disregarded).

gitea-mirror commented

2026-05-05 06:13:25 -06:00

Author

Owner

@steo-ml commented on GitHub (Jan 10, 2022):

I see, I'll be looking forward to this being implemented!

@steo-ml commented on GitHub (Jan 10, 2022): I see, I'll be looking forward to this being implemented!

gitea-mirror commented

2026-05-05 06:13:28 -06:00

Author

Owner

@stale[bot] commented on GitHub (Jan 10, 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 (Jan 10, 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.