mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1408] contrast and start up problems with monitorcontrol #795
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#795
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 @cosicrac on GitHub (Aug 3, 2023).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1408
Before opening the issue, have you...?
Describe the issue
I use monitor control on a macmini m2 with an apple led cinema display. I'm Very happy to be able to control brightness and volume.
But, I have to start up the application every time I start up the computer, I have clicked -the start up after login- box in preferences several times but after starting up it's empty
And the contrast control does not work. the slider is working in the menu but does not change contrast.
Can anyone help me with this,
Ce.
Expected behavior
The programme to automatically start up.
and the contrast control slider to work
Thank you
Anything else?
No response
Environment Information (please complete the following information)
@guidogoni commented on GitHub (Sep 22, 2023):
Same here, running on Mac Studio M2 Max (Ventura 13.5.2) with an AOC CQ32G3SE attached by DP. Any information I can provide to help on this bug let me know. Thanks!
@stale[bot] commented on GitHub (Sep 22, 2024):
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.