github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #418] Standardize the control range of different monitors when reported DDC ranges differ #333

New issue

Closed

opened 2026-05-05 05:45:32 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 05:45:32 -06:00

Owner

Originally created by @womeimingzi11 on GitHub (Mar 29, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/418

Originally assigned to: @waydabber on GitHub.

Checklist

I have searched for existing issues

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
I have two different model monitor, Monitor A and Monitor B. Their highest/lowest brightness are inconsistent, it makes the dual screen experience not so delicate.

Besides, the most interesting is monitor A provides a bad DDC implement, the 0 - 35%, 36-70%, 71-100% are replicates. So once I slide the slider of MonitorControl, the Monitor A goes to brighter and then become Dark, following it goes to brighter again.

Describe alternatives you've considered

Standardized the brightness of different monitors may solve this issue. For example, I can set 35% as the max brightness value of Monitor A, and 90% as the max brightness value of Monitor B. In this way, different displays can have more consistent brightness performance.

Additional context
Monitor A is Skyworth 27X1Q
Monitor B is AOC U2477WM

Originally created by @womeimingzi11 on GitHub (Mar 29, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/418 Originally assigned to: @waydabber on GitHub. **Checklist**  - [x] I have searched for existing issues **Is your feature request related to a problem? Please describe.** No **Describe the solution you'd like** I have two different model monitor, Monitor A and Monitor B. Their highest/lowest brightness are inconsistent, it makes the dual screen experience not so delicate. Besides, the most interesting is monitor A provides a bad DDC implement, the 0 - 35%, 36-70%, 71-100% are replicates. So once I slide the slider of MonitorControl, the Monitor A goes to brighter and then become Dark, following it goes to brighter again. **Describe alternatives you've considered** Standardized the brightness of different monitors may solve this issue. For example, I can set 35% as the max brightness value of Monitor A, and 90% as the max brightness value of Monitor B. In this way, different displays can have more consistent brightness performance. **Additional context** Monitor A is Skyworth 27X1Q Monitor B is AOC U2477WM

gitea-mirror

2026-05-05 05:45:32 -06:00

closed this issue
added the
enhancement

done
labels

gitea-mirror commented

2026-05-05 05:45:42 -06:00

Author

Owner

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

This is a relevant issue. What we'll try to do is to add a gamma curve and min/max ddc brightness boundary option that helps to synchronize various displays - but perfect synchronization will be super difficult to achieve because display backlight ranges and controllers differ immensely from display to display.

@waydabber commented on GitHub (Aug 21, 2021): This is a relevant issue. What we'll try to do is to add a gamma curve and min/max ddc brightness boundary option that helps to synchronize various displays - but perfect synchronization will be super difficult to achieve because display backlight ranges and controllers differ immensely from display to display.

gitea-mirror commented

2026-05-05 05:45:46 -06:00

Author

Owner

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

Regarding this issue the following will be the scope:

Use a standardized internal range (from 0 to 100) for all kinds of control no matter what are the actual DDC control bounds and control protocol (GammaTable, DisplayServices or DDC)
Matching the brightness levels of different display is not a scope of this issue.

Standardized internal range is required for #334 and #27.

@waydabber commented on GitHub (Sep 11, 2021): Regarding this issue the following will be the scope: - Use a standardized internal range (from 0 to 100) for all kinds of control no matter what are the actual DDC control bounds and control protocol (GammaTable, DisplayServices or DDC) - Matching the brightness levels of different display is not a scope of this issue. Standardized internal range is required for #334 and #27.

gitea-mirror commented

2026-05-05 05:45:49 -06:00

Author

Owner

@womeimingzi11 commented on GitHub (Sep 11, 2021):

This is a relevant issue. What we'll try to do is to add a gamma curve and min/max ddc brightness boundary option that helps to synchronize various displays - but perfect synchronization will be super difficult to achieve because display backlight ranges and controllers differ immensely from display to display.

I definetly agree with you that the perfect synchronization is not easy. But you know, for low-end display, not so bad is perfect.

And I am so glad to know this feature is in progress.

@womeimingzi11 commented on GitHub (Sep 11, 2021): > This is a relevant issue. What we'll try to do is to add a gamma curve and min/max ddc brightness boundary option that helps to synchronize various displays - but perfect synchronization will be super difficult to achieve because display backlight ranges and controllers differ immensely from display to display. I definetly agree with you that the perfect synchronization is not easy. But you know, for low-end display, not so bad is perfect. And I am so glad to know this feature is in progress.

gitea-mirror commented

2026-05-05 05:45:52 -06:00

Author

Owner

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

Hey @womeimingzi11 - the solution for this will not make differint displays match in min/max brightness and the progression of change. What I will be working on is the groundwork needed for a standardized internal scale among displays and then later build on this the options required if somebody want to match the brightness profile of differing displays + to have the ability to use a single scale to control multiple displays or replicate the brightness of internal displays to external displays.

So I am not sure if this is what you had originally in mind. I think if all related requests are resolved that deal with display min/max, curve and synchronization issues, then there is a good chance that things will work out. But its a long way, this is just a first step.

@waydabber commented on GitHub (Sep 11, 2021): Hey @womeimingzi11 - the solution for this will not make differint displays match in min/max brightness and the progression of change. What I will be working on is the groundwork needed for a standardized internal scale among displays and then later build on this the options required if somebody want to match the brightness profile of differing displays + to have the ability to use a single scale to control multiple displays or replicate the brightness of internal displays to external displays. So I am not sure if this is what you had originally in mind. I think if all related requests are resolved that deal with display min/max, curve and synchronization issues, then there is a good chance that things will work out. But its a long way, this is just a first step.

gitea-mirror commented

2026-05-05 05:45:54 -06:00

Author

Owner

@womeimingzi11 commented on GitHub (Sep 13, 2021):

WOW @waydabber, it looks complicated but delicate.

I have carefully read your discussion with @JoniVR, and I find your plan is really academic. To tell the truth I am not sure whether I have understood the display profile feather.

But I am definitely looking forward to your contributions.

@womeimingzi11 commented on GitHub (Sep 13, 2021): WOW @waydabber, it looks complicated but delicate. I have carefully read your discussion with @JoniVR, and I find your plan is really academic. To tell the truth I am not sure whether I have understood the display profile feather. But I am definitely looking forward to your contributions.

gitea-mirror commented

2026-05-05 05:45:55 -06:00

Author

Owner

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

@womeimingzi11 lol, no problem, don't worry about it. Takeaway is that there's gonna be a bunch of advanced settings to play with and you'll be able to experiment with them until you find the result satisfactory.

@waydabber commented on GitHub (Sep 13, 2021): @womeimingzi11 lol, no problem, don't worry about it. Takeaway is that there's gonna be a bunch of advanced settings to play with and you'll be able to experiment with them until you find the result satisfactory.

gitea-mirror commented

2026-05-05 05:45:57 -06:00

Author

Owner

@womeimingzi11 commented on GitHub (Sep 13, 2021):

Fantastic @waydabber ! Your explaination is easy to understand, lol! I even can't wait to try all the features!

@womeimingzi11 commented on GitHub (Sep 13, 2021): Fantastic @waydabber ! Your explaination is easy to understand, lol! I even can't wait to try all the features!

gitea-mirror commented

2026-05-05 05:45:58 -06:00

Author

Owner

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

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

@waydabber commented on GitHub (Sep 15, 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:45:59 -06:00

Author

Owner

@womeimingzi11 commented on GitHub (Sep 15, 2021):

OMG! It looks really cool and delicate! I guess it even cover all the edge cases.

Especially the brightness/volume/contrast curves, it even beyond my original suggestions!

Cheers!

Chen Han
E-mail: @.***
School of Life Sciences, Lanzhou University, Lanzhou, 730000 P.R.China
在 2021年9月15日 +0800 PM3:22，waydabber @.***>，写道：

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

@womeimingzi11 commented on GitHub (Sep 15, 2021): OMG! It looks really cool and delicate! I guess it even cover all the edge cases. Especially the brightness/volume/contrast curves, it even beyond my original suggestions! Cheers! ---------------------------------- Chen Han E-mail: ***@***.*** School of Life Sciences, Lanzhou University, Lanzhou, 730000 P.R.China 在 2021年9月15日 +0800 PM3:22，waydabber ***@***.***>，写道： > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe. > Triage notifications on the go with GitHub Mobile for iOS or Android.