mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #281] CTRL + Volume for Headphone Jack / Internal Volume #221
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#221
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 @chrisspiegl on GitHub (Aug 28, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/281
Originally assigned to: @waydabber on GitHub.
Add the ability to change the internal and external volume with modifier keys.
It's awesome that V2.0 already added support to change the Brightness of Internal and External Monitors. I would love to see this extended to the Volume Functionality, I use the headphone jack to send audio to a stereo system for music playback, but all other audio is going through my monitor.
The modifier with "CTRL + Volume Keys" would be an awesome fix (just like brightness works).
Warm Regards,
Chris
@pointmax commented on GitHub (Oct 7, 2020):
does changing the brightness individually work? It doesn't seem to work for me...
I can only change the brightness for both displays (macbook + monitor) simultaneously
@waydabber commented on GitHub (Aug 21, 2021):
Hi @pointmax - it should work - depending on where your mouse is situated (in version 3.0.0). Also you can use ctrl+brightness keys to control the internal display specifically.
Using CTRL+Volume Keys is a bit different since if there are several audio devices, the app will not know which one to fall back to in this case (unlike for internal displays which is easily identifiable). This would therefore require a more extensive solution where you could define which shortcut key should control which audio device - which is not really in the scope of MonitorControl (but might be for an other app).
Because of this I'll close this issue. If you don't agree with this answer or you have a suggestion on how this should work and still fit the profile of MonitorControl, please let me know! Thank you!