mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #962] Brightness offset between displays #588
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#588
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NathanielIR on GitHub (Mar 2, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/962
Before opening the issue, have you...?
Is your feature request related to a problem? Please describe
Different displays have different max brightnesses
Describe the solution you'd like
Suggestion: The ability to change the value of an external display when the internal display is at a certain value. For instance, if the internal display is set to 100% make the external display 100%. But if the internal display is at 50%, set the external display to 75%, etc. A lot of external displays (including mine) can't reach the same brightness as Apple's so when they're at the same brightness value the external one can be a lot dimmer. Having the ability to equalise this would be super helpful. Especially when you've got keyboard shortcuts set to "Change for all screens"
Describe alternatives you've considered
There are none in the app
Anything else?
No response
@JessicaMaine commented on GitHub (Apr 14, 2022):
I also can't increase brightness of my external monitors to match MBP brightness :(
the 100% for external is very dark
@stale[bot] commented on GitHub (Apr 18, 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.