mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #273] Change brightness in 1% increments #215
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#215
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 @quantumgolem on GitHub (Aug 3, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/273
Checklist
Is your feature request related to a problem? Please describe.
Some monitors have a strange flickering issue when changing brightness through DDC, as described in this issue.
Describe the solution you'd like
To avoid the issue, the brightness needs to gradually be changed down. For example, instead of telling the monitor to go to 20% from 80%, it can be told to go to 79%, then 78%, then 77%, etc. all the way to 20%. This would prevent the flickering issue.
Describe alternatives you've considered
I have considered using a bash script with ddcctl, but that seems strange heh
@JoniVR commented on GitHub (Aug 3, 2020):
You can use shift+alt modifiers to change brightness in 1% increments for now. iirc there's a different issue (which I can't remember) where we considered making a setting that allows the shift+alt behaviour to become the default. I think that's probably the best solution here.
@quantumgolem commented on GitHub (Aug 4, 2020):
Oh, that's neat, I didn't think of that. It makes it much better. However, the monitor sometimes glitches out and if I do it too long, it sometimes blanks out, lmao. Maybe that was the issue?
But yes, I'll do this. It's not a huge deal anyway. I should just get a better monitor which implements DDC specs and functionality better...