mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #932] Control only volume via DDC #576
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#576
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 @lloeki on GitHub (Feb 3, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/932
Before opening the issue, have you...?
Is your feature request related to a problem? Please describe
I have two identical LG 4K displays on a Mac Mini M1.
As is known:
So to keep brightness consistent between both I use Software (gamma) mode, forcing it on the USB-C display. Still, I would like to keep being able to adjust volume via DDC.
Describe the solution you'd like
Have "Use hardware DDC control" per-display checkbox split into "Use hardware DDC control for picture" and "Use hardware DDC control for volume", or something to that effect in the advanced mode table that would allow me to uncheck the former but still check the latter.
Describe alternatives you've considered
I tried tricking it using advanced settings:
Anything else?
No response
@waydabber commented on GitHub (Feb 5, 2022):
You are right, there is no way to achieve this now. Probably Brightness DDC unavailable when hardware DDC control is enabled should kick in software mode.
@stale[bot] commented on GitHub (Feb 5, 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.