mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #212] Apple Thunderbolt Display slider scaling wrong (display too dim; audio too quiet) #161
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#161
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 @cpcallen on GitHub (May 6, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/212
When used a Thunderbolt Display, MonitorControl can adjust the brightness of the external monitor only between very dim and almost completely off (and one or the other; nothing in between). Comparing against the Brightness slider in System Preferences > Displays, it is clear that MonitorControl is selecting between the lowest and second-lowest possible settings.
Similarly, the volume control, when set on maximum, is equivalent to about 2/16ths of full range compared to setting by the volume keys / volume menu.
Monitor: Apple Thunderbolt Display (A14070)
Laptop: MacBook Pro 13" 2015 (MacBookPro12,1)
GPU: Intel Iris Graphics 6100
OS: macOS 10.13.6 (17G12034)
Info from Settings, in case it is useful:
@esusatyo commented on GitHub (Jun 2, 2020):
I have a Thunderbolt display and have the same problem. The brightness slider is completely broken though, sliding it to any direction will decrease the brightness to minimum.
Monitor: Apple Thunderbolt Display (A14070)
Laptop: MacBook Pro 15" 2018
GPU: Radeon Pro 560X 4 GB graphics
OS: macOS 10.15.5
Let me know if there is any debugging steps I can do. I also have Xcode so can step through the code.
@jlcd commented on GitHub (Jun 5, 2020):
I also have a Thunderbolt display, first thing I noticed is that once I pressed the "lower/increase brightness" key, the brightness went to fully dark and didn't change at all after that, not even on the app's slider.
And it also broke the brightness keys, as they don't do anything anymore even though the brightness scale shows after I press them.
Monitor: Apple Thunderbolt Display (A14070)
Laptop: MacBook Pro 15" 2018
GPU: Radeon Pro 555X 4 GB graphics | Intel UHD Graphics 630 1536 MB
OS: macOS 10.15.5
@JoniVR commented on GitHub (Jun 15, 2020):
Judging by the fact that this is only reported on Thunderbolt displays, I'm going to mark this as a monitor issue for now. Does the Thunderbolt display not support brightness controls natively?
@cpcallen commented on GitHub (Jun 16, 2020):
It certainly does:
(And I can confirm that these controls work as expected on the display in question.)
@JoniVR commented on GitHub (Jun 16, 2020):
In that case, what’s your specific use case for MonitorControl (or what’s missing)? Can’t you just disable the display and or MonitorControl and use the controls natively without DDC?
I’m sorry I’ve never used one.
@cpcallen commented on GitHub (Jun 16, 2020):
I have in fact stopped using MonitorControl because of this bug (and it not being needed); nevertheless, there are a few advantages to MonitorControl compared to the native controls:
@jlcd commented on GitHub (Jun 16, 2020):
In my case I have a second monitor that benefits directly from MonitorControl, as the other way to change brighntess is by pushing buttons under it.
I'm not using MC for the Thunderbolt Display anymore.
@dlopuch commented on GitHub (Jul 10, 2020):
A potential clue? It seems the MC brightness knob has a tiny jump or deadzone from "0-position" to "gradual scaling". On my apple thunderbolt, the MC 0-position sets it at minimal brightness, then after the deadzone jump the monitor goes up one click in brightness, but then it doesn't change any more.
So it's almost as if it has exactly two levels: minimum-dimness, and one-click-above-minimum-dimness
@stale[bot] commented on GitHub (Aug 3, 2021):
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.
@cpcallen commented on GitHub (Aug 9, 2021):
This issue still exists in MonitorControl v2.1.0. I am unable to test for it in v3.0.0-beta5 due to #508.
@cpcallen commented on GitHub (Aug 11, 2021):
I've now tried 3.0.0-beta6 and the behaviour is as reported initially.
@waydabber commented on GitHub (Aug 11, 2021):
Hey @cpcallen, the Apple Thunderbolt display can be controlled via a completely different protocol (much like internal displays) than generic non-Apple displays. I'd like to add this as a feature also. Hopefully I'll have some time to work on this. If yes, then your help would be much appreciated as I don't have an Apple branded display to test.
@cpcallen commented on GitHub (Aug 11, 2021):
Sure; I'd be glad to help (as time allows).
@waydabber commented on GitHub (Aug 19, 2021):
We'll be working on Apple display and other USB controlled displays here:
https://github.com/MonitorControl/MonitorControl/issues/364
I close this issue so we don't have two.
@waydabber commented on GitHub (Sep 3, 2021):
For those with Apple displays, there is a link to a test build with proper support here: https://github.com/MonitorControl/MonitorControl/issues/539