Before opening the issue, have you...?
Describe the bug
MonitorControl v4.3.3 does not read current DDC values from the monitor either at startup or when a new monitor is plugged in.
Steps to reproduce
Connect a new screen with brightness set at a level <100
or
with the screen connected, start up monitor control.
v4.2.2 will in both cases read the value from the screen and adjust the slider to the current brightness value.
v4.3.3 has the monitor brightness slider at 100% all the time until the slider is moved, then it sets the brightness value on the monitor.
Expected behavior
Both on startup and when connecting a new screen, the current DDC brightness value should be read. Worked on v4.2.0, not on v4.3.3.
Anything else?
- DDC values are correctly read and set by ddcctl
- Added config
Environment Information (please complete the following information)
- macOS version: Sonoma latest
- Mac model: 2020 MBP 13'', Intel, using thunderbolt cable.
- MonitorControl version: v4.2.0 / v4.3.3
- Monitor(s): LG 27'' 4K 27UN850-W
- Apple Silicon/M1 (yes or no): no
Before opening the issue, have you...?
Describe the bug
MonitorControl v4.3.3 does not read current DDC values from the monitor either at startup or when a new monitor is plugged in.
Steps to reproduce
Connect a new screen with brightness set at a level <100
or
with the screen connected, start up monitor control.
v4.2.2 will in both cases read the value from the screen and adjust the slider to the current brightness value.
v4.3.3 has the monitor brightness slider at 100% all the time until the slider is moved, then it sets the brightness value on the monitor.
Expected behavior
Both on startup and when connecting a new screen, the current DDC brightness value should be read. Worked on v4.2.0, not on v4.3.3.
Anything else?
Environment Information (please complete the following information)