mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #335] LG 38GL950G has partial range support, highest volume mutes #266
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#266
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 @Hexxeh on GitHub (Nov 26, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/335
Originally assigned to: @waydabber on GitHub.
Checklist
Describe the issue
LG 38GL950G connected via USB-C to HDMI adaptor to 2019 Macbook Pro 15" can control volume and brightness, but has several quirks
Volume settings behave incorrectly at both ends of the scale:
I: VCP control #98 (0x62) = current: 255, max: 255Brightness settings behave incorrectly for much of the scale:
/character when brightness set by OSXI: VCP control #16 (0x10) = current: 60, max: 194values stick at 60 even when settings change lower than 4.I: VCP control #16 (0x10) = current: 194, max: 194Not sure if these are just quirks of my monitor that can't be fixed, since in some cases the range reports correctly. If so, maybe I can help implement quirks support to handle these?
Expected behavior
Brightness and volume control same full range possible via OSD.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Environment Information (please complete the following information):
@Hexxeh commented on GitHub (Nov 27, 2020):
Noticed for brightness that setting
/ddcctl -d 1 -b 255does result in a brighter image than full brightness via MonitorControl, which I'm guessing is stopping at the reported 194 max.@waydabber commented on GitHub (Aug 19, 2021):
It would be great to have an advanced preferences option where DDC min. and max. values could be overridden. I will assign this task to myself, but I don't know when will I be able to actually implement it. :)
@waydabber commented on GitHub (Aug 19, 2021):
Hi, since this is a duplicate of the issue below, I'll close this issue now - please follow developments here:
https://github.com/MonitorControl/MonitorControl/issues/310