github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

lower bounds settings in Advanced Preferences #243

New issue

Closed

opened 2026-05-05 05:29:35 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 05:29:35 -06:00

Owner

Originally created by @emiyl on GitHub (Oct 19, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/310

Originally assigned to: @waydabber on GitHub.

Checklist

I have searched for existing issues
I have looked through the Monitor Troubleshooting wiki
I have updated MonitorControl to the latest version

Describe the issue
Going beyond around 60% brightness causes the brightness to wrap around to the lowest brightness, before going back up to the brightest setting to 100%.

Expected behavior
I expect the brightness to increase linearly from 0 to 100%

Additional context
I am using an incredibly niche setup, involving an iMac 5K panel hooked up to a controller board that I got from AliExpress, which I believe is based on the hardware inside the DELL UP2715K. When looking at the in-built monitor settings, it seems that going beyond 60% with MonitorController causes the brightness to go over 100% on the monitor. When it reaches 130% brightness it wraps around to the lowest brightness.

I recognise that I am probably one of very few people who have this setup, but I thought I'd mention it, just in case. Perhaps a minimum/maximum brightness value could be added to the Advanced tab?

Environment Information (please complete the following information):

macOS version: 10.15.7
MonitorControl version: 2.1.0 (Build 721)
Monitor(s): iMac 5K Display Panel with controller board possibly based on the DELL UP2715K?
Mac model: iMac15,1 (5K Late 2014)
Monitor Cable(s)/Connection(s): 2xDP1.2 cables

Originally created by @emiyl on GitHub (Oct 19, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/310 Originally assigned to: @waydabber on GitHub. **Checklist**  - [x] I have searched for existing issues - [x] I have looked through [the Monitor Troubleshooting wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [x] I have updated MonitorControl to the latest version **Describe the issue** Going beyond around 60% brightness causes the brightness to wrap around to the lowest brightness, before going back up to the brightest setting to 100%. **Expected behavior** I expect the brightness to increase linearly from 0 to 100% **Additional context** I am using an incredibly niche setup, involving an iMac 5K panel hooked up to a [controller board](https://www.aliexpress.com/item/32965911057.html) that I got from AliExpress, which I believe is based on the hardware inside the DELL UP2715K. When looking at the in-built monitor settings, it seems that going beyond 60% with MonitorController causes the brightness to go over 100% on the monitor. When it reaches 130% brightness it wraps around to the lowest brightness. I recognise that I am probably one of very few people who have this setup, but I thought I'd mention it, just in case. Perhaps a minimum/maximum brightness value could be added to the Advanced tab? **Environment Information (please complete the following information):** - macOS version: 10.15.7 - MonitorControl version: 2.1.0 (Build 721) - Monitor(s): iMac 5K Display Panel with [controller board](https://www.aliexpress.com/item/32965911057.html) possibly based on the DELL UP2715K? - Mac model: iMac15,1 (5K Late 2014) - Monitor Cable(s)/Connection(s): 2xDP1.2 cables

gitea-mirror

2026-05-05 05:29:35 -06:00

closed this issue
added the
enhancement

done
labels

gitea-mirror commented

2026-05-05 05:29:42 -06:00

Author

Owner

@JoniVR commented on GitHub (Nov 2, 2020):

I think a min/max setting in Advanced Preferences is indeed a good solution here as we've probably changed the volume/brightness calculation logic a dozen times by now and it seems like there are always edge cases because of the wildly different configurations.

Though it's pretty low priority in my opinion, if anyone feels like doing a PR I'd be happy to review it.

@JoniVR commented on GitHub (Nov 2, 2020): I think a min/max setting in Advanced Preferences is indeed a good solution here as we've probably changed the volume/brightness calculation logic a dozen times by now and it seems like there are always edge cases because of the wildly different configurations. Though it's pretty low priority in my opinion, if anyone feels like doing a PR I'd be happy to review it.

gitea-mirror commented

2026-05-05 05:29:44 -06:00

Author

Owner

@matiaspl commented on GitHub (Nov 9, 2020):

I vote for this feature too. My OEM (Uscreen) portable monitor also wraps around brightness and contrast values a couple of times using the default scale.

@matiaspl commented on GitHub (Nov 9, 2020): I vote for this feature too. My OEM (Uscreen) portable monitor also wraps around brightness and contrast values a couple of times using the default scale.

gitea-mirror commented

2026-05-05 05:29:47 -06:00

Author

Owner

@ninggu2008 commented on GitHub (Nov 29, 2020):

Me, too. My monitor also wraps around brightness values a couple of times using the default scale.

@ninggu2008 commented on GitHub (Nov 29, 2020): Me, too. My monitor also wraps around brightness values a couple of times using the default scale.

gitea-mirror commented

2026-05-05 05:29:51 -06:00

Author

Owner

@valfant commented on GitHub (Dec 9, 2020):

I think the min/max clamp will also be very helpful for matching displays with different physical brightness.
e.g.
Display A with brightness measured from 60 to 400 nit
Display B with brightness measured from 20 to 300 nit
Set Display A min/max to 0%/71% would yield a 60 to 301.4 nit range
Set Display B min/max to 14%/100% would yield a 59.2 to 300 nit range

@valfant commented on GitHub (Dec 9, 2020): I think the min/max clamp will also be very helpful for matching displays with different physical brightness. e.g. Display A with brightness measured from 60 to 400 nit Display B with brightness measured from 20 to 300 nit Set Display A min/max to 0%/71% would yield a 60 to 301.4 nit range Set Display B min/max to 14%/100% would yield a 59.2 to 300 nit range

gitea-mirror commented

2026-05-05 05:29:54 -06:00

Author

Owner

@Montvydas commented on GitHub (Jan 19, 2021):

Voting this up. My EVICIV portable monitor reaches max brightness when MonitorControl is around 45%. After that it goes black, then until it reaches 100% in settings the monitor turns random brightness levels. The same goes for contrast, while the volume works perfectly fine.

@Montvydas commented on GitHub (Jan 19, 2021): Voting this up. My EVICIV portable monitor reaches max brightness when MonitorControl is around 45%. After that it goes black, then until it reaches 100% in settings the monitor turns random brightness levels. The same goes for contrast, while the volume works perfectly fine.

gitea-mirror commented

2026-05-05 05:29:57 -06:00

Author

Owner

@Neogene commented on GitHub (Jul 7, 2021):

Vote up too. My external portable monitor 👍

slider value 0% - monitor reports 5%
slider value 38% - monitor reports 100% (greater values repeat 5...38%)

@Neogene commented on GitHub (Jul 7, 2021): Vote up too. My external portable monitor 👍 slider value 0% - monitor reports 5% slider value 38% - monitor reports 100% (greater values repeat 5...38%)

gitea-mirror commented

2026-05-05 05:30:00 -06:00

Author

Owner

@silvetti commented on GitHub (Aug 21, 2021):

When will this feature be implemented? Been months now :(

@silvetti commented on GitHub (Aug 21, 2021): When will this feature be implemented? Been months now :(

gitea-mirror commented

2026-05-05 05:30:03 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Hi @silvetti - we plan to add this in the future.

Also, you are always free to work on this and create a pull request if you'd like to contribute to the development or you can help financing the project by specifically pointing out a goal to see an issue prioritized. :) As of right now the project is rather understaffed and everybody's working on this in his spare time for free. :) Thank you for your understanding!

@waydabber commented on GitHub (Aug 21, 2021): Hi @silvetti - we plan to add this in the future. Also, you are always free to work on this and create a pull request if you'd like to contribute to the development or you can help financing the project by specifically pointing out a goal to see an issue prioritized. :) As of right now the project is rather understaffed and everybody's working on this in his spare time for free. :) Thank you for your understanding!

gitea-mirror commented

2026-05-05 05:30:05 -06:00

Author

Owner

@waydabber commented on GitHub (Sep 12, 2021):

See screenshots of the implementation in the v3.1.0 preliminary discussion.

@waydabber commented on GitHub (Sep 12, 2021): See screenshots of the implementation in the [v3.1.0 preliminary discussion](https://github.com/MonitorControl/MonitorControl/discussions/596).

gitea-mirror commented

2026-05-05 05:30:08 -06:00

Author

Owner

@emiyl commented on GitHub (Sep 12, 2021):

Looks awesome :) thank you!

@emiyl commented on GitHub (Sep 12, 2021): Looks awesome :) thank you!