mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #228] Add option to always change Display Volume upon Volume keys press #175
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#175
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 @jheaton141 on GitHub (May 31, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/228
Originally assigned to: @waydabber on GitHub.
The volume adjuster does not work when Boom3D is in use. The brightness continues to work, however.
https://www.globaldelight.com/boom/
@JoniVR commented on GitHub (Jun 10, 2020):
I'm not sure about this, but doesn't Boom3D use a virtual audio loopback device? (it creates a "new" audio output)
@kikiwora commented on GitHub (Jun 14, 2020):
Boom3D definitely uses a new Device, which is always selected as output, no matter what device the user tries to select.
When user selects some other device, Boom3D detects that change and automatically switches its output.
The issue with this method is that if the real output device on its own does not support native audio control, Boom3D does not give it that functionality, despite the fact that Boom3D device provides volume regulation and mute functions.
So I assume, and I'm only assuming since I have no Display with Sound capabilities to verify, that when on display output is selected (and it is when you use Boom3D), MonitorControll ignores Volume buttons.
And as a Software Engineer, I also assume that this cannot be fixed without Boom3D developer collaboration from the MonitorControll side only, cause you know, there is no real way to detect which Device is really used to output sound when Boom3D is used.
However, I suggest bypassing this issue by adding the option for a user to "always change Display Volume upon Volume keys press".
This may not be the best possible solution, but it is quick and usable.
@JoniVR commented on GitHub (Sep 19, 2020):
Correct, when a different audio output is selected, MonitorControl will detect if that audio device can "set its own volume", if that's the case, then it'll stop listening for volume shortcuts.
I agree that might probably the best possible solution in this case.
@ileodo commented on GitHub (Jan 9, 2021):
If someone can provide some guidance, probably I can help with this.
@jbpenrath commented on GitHub (Feb 23, 2021):
Just to share my experience, I'm currently using Boom 3D and I cannot change the volume only from keyboard function keys. If I use the volume slider from the MonitorControl panel, it changes the monitor volume as expected.
Hardware:
Software
@waydabber commented on GitHub (Aug 19, 2021):
The app checks if the current audio output has volume controls or not. If not, then it toggles the volume. It would be possible to add as an advanced setting to force listening to the keyboard no matter what or better, manually specify on which audio output should the app listen to volume keys (this would also be useful if more than one display has volume control - as probably not the location of the mouse should decide which display to control in this regard as the user probably has his speakers hooked up to one display only).
@waydabber commented on GitHub (Aug 19, 2021):
This one will be dealt with here:
https://github.com/MonitorControl/MonitorControl/issues/11
enabledoption in settings #1066