mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #207] Some monitors have full brightness at ~40% slider #154
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#154
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 @willerbee on GitHub (Apr 20, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/207
I would think that this is because my monitor probably didn't implement DDC/CI well (it's an AN-238W03K). But I can control brightness and volume alright. This gem is such a blessing.
Volume slider controls monitor volume well, but with brightness slider at roughly 40% in the app my monitor is at 94% brightness. From there, pressing "brightness up" and my monitor goes blank (because the monitor is being set to something equivalent to 100+). Doing another "brightness up" keypress and the monitor works again but reports at 142% brightness 😄 and it's a little bit brighter (and worrysome it could break lol). It would be nice to be able to have some kind of scale/override/calibration to set in the preferences so that I can let the app know that 40% slider is the real 100% brightness.
@kumowoon1025 commented on GitHub (Apr 22, 2020):
Yeah, display controllers can literally be on a spectrum of "speaks perfect DDC/CI MCCS VCP" to "hi u wont pixels mate?" even on brand name models.
In particular they can be pretty horrible at reporting luminance state & capability, especially if they support NCL curves with HDR. The display itself reporting 100%+ brightness is weird though, is it supposed to do that? (extended range or something?)
@willerbee commented on GitHub (Apr 22, 2020):
LOL. I don't think it is supposed to do that because if you control the brightness using the monitor's controls at the back, 100% is the max you can go. They might have restricted past 100% on hardware buttons and forgot about limiting it through DDC/CI. This monitor supports HDR though (as Windows 10 reports), but it feels like emulated.
@kumowoon1025 commented on GitHub (Apr 22, 2020):
Windows 10 reports any display capable of 8bit+FRC as HDR capable I think (Windows HD Wide Color or something). Maybe that's why it feels unnatural... At the same time though, HDR displays are supposed to be able to represent brighter-than-100% brightness for a short time or in a small area (specular highlights, like maybe sunlight glinting off in an already lit up scene)
I've never even heard of brightness going over 100% though. Volume maybe, if they have European max limits set or have a preamp or something.Did you try seeing if macOS detects it as an HDR display?
@willerbee commented on GitHub (Apr 22, 2020):
I don't know about this AN-238W03K if it is 8bit+FRC, but I had a Dell P2415Q and it doesn't show Windows HD Color options like this one does. MacOS detects it like a regular 75Hz monitor.
Photos I took with OSD HDR setting, Youtube showing HDR quality options, and brightness setting indicating 94% and 142%
https://photos.app.goo.gl/xwvLaHjLfAi7JEdH8
I mentioned earlier that it feels like emulated HDR because Windows UI look like crap, but HDR videos (at least from youtube) look amazing.
@JoniVR commented on GitHub (Jun 10, 2020):
I think this is closely related to #201, will continue tracking there.
@kumowoon1025 commented on GitHub (Jun 25, 2020):
Hey, don't know if this is related, but for what it's worth, I finally picked up my Thunderbolt Display that's been sitting in the closed Apple Store, (it's the original one from Apple, with TB1 and FW800/USB2.0 combo expansion on the back) I plugged it into an iMac with a missing display, and it did something similar.
100% brightness on MonitorControl, and the brightness HUD showed at 100% too (which is to be expected since it's overridden I guess). Quit the app, and used the driver or whatever macOS uses to control the display, and it went back to show it was at about ~20% brightness, which was how dim it seemed to me. I could then use the same brightness controls on my keyboard to bring it back up to full brightness.
Now that I recount it, maybe it's kind of the opposite of the issue you had, but I think a conflict between two control channels trying to light up or dim down the display could have been an issue. OP only used the app for volume control right?