mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1106] User presets for brightness/contrast (feature request) #656
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#656
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 @waydabber on GitHub (Jul 8, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1106
Discussed in https://github.com/MonitorControl/MonitorControl/discussions/1098
Originally posted by WWWFWWW July 2, 2022
It would be really great if MonitorControl had custom user presets for specific brightness/contrast values.
I am often working on a calibrated monitor set to a rather low brightness and contrast (set to an approximate industry standard conditions in a darkened room) when editing photographs, with the brightness and contrast determined by hardware calibration for best colour accuracy.
However, when just browsing the web on a sunny day with the window blinds open, I'd like to quickly up the values to some higher value for readability, but still retain my previous fine settings as a preset I could easily return to.
Having two presets (or at least one, "calibrated") would really help with that, especially with keyboard shortcuts for them.
I am aware I could script ddcctl for that, but MonitorControl is so much nicer to use!
@hudsoncreativestudio commented on GitHub (Jul 25, 2022):
+1 from me on this idea.
@stale[bot] commented on GitHub (Jul 25, 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.