mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 22:01:08 -06:00
[GH-ISSUE #14] Feature: change brightness/volume for all displays, including internal #15
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#15
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 @Amir-Hass on GitHub (Feb 18, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/14
Originally assigned to: @the0neyouseek on GitHub.
The setting to change brightness and volume at the same time for all displays doesn't work. This happens both with the keyboard shortcut and the menu bar widget, they only do one display at a time. (version 1.2)
@the0neyouseek commented on GitHub (Feb 18, 2018):
Hi again @Amir-Hass ,
Thank you for testing this, as I currently don't have a multi-monitor setup I couldn't test it well. I'll try to see if I can find another monitor to squash this bug soon.
Have a nice day !
@funbben commented on GitHub (Feb 22, 2018):
I confirm it doesn't work, changing brightness/contrast with sliders works fine, for external monitor but doesn't work for internal display.
@the0neyouseek commented on GitHub (Feb 25, 2018):
Hi @funbben ,
Actually, this was not what I had in mind with this option. MonitorControl doesn't handle at all the internal display, so the settings should only affect (in theory since I haven't tested it) external display for now.
But as it's a very good suggestion I'll had this to the list of things to do. (Maybe as a separate setting for example)
@marcelfarres commented on GitHub (Mar 27, 2018):
I would love to be able to control internal+external brightness together.
@cseelus commented on GitHub (Jun 14, 2018):
@the0neyouseek Maybe you could use code from Brightness Menulet to achieve this.
Brightness Menulet sets the brightness for the internal screen as well.
One thing thats really convenient, is the option to follow the main screens (internal screens) brightness, which dims/brightens the external display automatically with the internal display, when the ambient light sensor of the iMac/MacBook detects changes there.
@retrography commented on GitHub (Jun 18, 2018):
@cseelus: Your excellent idea is being explored here: #27.
@retrography commented on GitHub (Jun 18, 2018):
The idea of controlling the internal monitor along with the external is great. It has some caveats, though:
So, a locking solution needs to consider this, and yes, it will be absolutely worth the pain to do so. This is an excellent feature.
I would also gladly have the same locking solution for the volume. The same caveats apply to the volume level.
@cseelus commented on GitHub (Jun 18, 2018):
Hi, @retrography , thanks for getting back
I can't say much about the volume settings though, as I only use Headphones (via TB3-Dock) or a pair of Speakers via Bluetooth.
@yedlosh commented on GitHub (Nov 28, 2019):
Well I had tried the Brightness Menulet because of this, and it's Follow Main Screen option works great for me, but the app has a bug that only one of my two identical monitors gets controlled, and it's apparently not supported anymore. So yeah.. It's a shame there still isn't one DDC app which has everything working.
@JoniVR commented on GitHub (Jan 26, 2020):
I'm working on this in #148, I'm going to try to make it respect the "Change brightness/volume for all displays" checkbox and allow the user to select it from the display preferences.
Not 100% sure how well it would work since talking to the internal display requires the usage of another (private) api, the same one other brightness tools use. Tracking progress mostly in there.