mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1312] Questions and observations with Apple Cinema Display 30" #750
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#750
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 @forthrin on GitHub (Feb 13, 2023).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1312
Before opening the issue, have you...?
Question
I have read other issues and discussions, but causes and effects seem so complex that it isn't evident to a non-developer what might constitute a duplicate, so I choose to post my results and questions in full in hope of a helpful response.
Apple Cinema Display 30" (A1083)
MonitorControl 4.1.0
Test 1: MacBook Air 2017 with macOS 12.6.3 via Apple Dual Link DVI cable
Test 2: MacBook Air M1 with macOS 13.2 via CAC-1510-A adapter
Questions, in order of importance:
How can I increase the hardware brightness as neither the physical brightness button nor M1/Ventura/MonitorControl can control it. It would be ridiculous to keep the 2017 for the sole purpose of increasing hardware brightness :P
What is the common reason the physical brightness buttons stop working? Can this be fixed without opening the case?
When reducing hardware brightness, a hissing frequency (around 300 Hz) increases in volume from the left side of the monitor (assumedly the PSU). Are all A1083 specimens like this? Can the noise be eliminated by replacing components?
Is there any performance/battery hit on using SW brightness, or is this done on the GPU so it has no practical effect?
Do these physical brightness keys control the monitor directly, or do they send signals to the computer via USB, that in turn sends the effective control signals back to the monitor?
Is it the M1 (HW) or macOS 13.2 (SW) that does not support hardware control of the monitor?
Sometimes, if I exit MonitorControl, the software brightness jumps up to a much higher (normal maximum) level, even though the slider was at max before I exited. Is this a bug? Or how does this situation occur in the first place?
@waydabber commented on GitHub (Feb 16, 2023):
I'll move this one over to discussions, hopefully somebody with experience with this particular display will be able to answer the questions!