8000 Volume Control and eqMac: Currently incompatible. Possible to remove conflict? · Issue #32 · alberti42/Volume-Control · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Volume Control and eqMac: Currently incompatible. Possible to remove conflict? #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
porg opened this issue Jan 19, 2025 · 3 comments
Open

Volume Control and eqMac: Currently incompatible. Possible to remove conflict? #32

porg opened this issue Jan 19, 2025 · 3 comments

Comments

@porg
Copy link
porg commented Jan 19, 2025

Today I realized that when Volume-Control is enabled that 3rd software eqMac which also works in conjunction with the audio control keys suffers the bug that eqMac cannot be unmuted anymore with the audio control keys, neither with unmute nor with *vol +`.

On the following video recordings Volume-Controls was set to Hide menu bar icon, and I did yet not knew Volume Control was the root cause for eqMac's bug. See video recordings further down to see the clear causal relationship.

System audio falsely remains muted after Vol-Down til 0 and then Vol-Up again

eqMac.-.System.audio.falsely.remains.muted.after.Vol-Down.til.0.and.then.Vol-Up.again.mp4

System audio falsely remains muted after HW-Mute pressed once to mute and again to unmute

eqMac.-.System.audio.falsely.remains.muted.after.HW-Mute.pressed.once.to.mute.and.again.to.unmute.mp4

Bug can be reliably reproduced

Volume Control running → eQ Mac runs into forementioned problems

eqMac.1.works.when.Volume.Control.disabled.mp4

Volume Control NOT running → eQ Mac operates normally with the hardware audio control keys

eqMac.2.fails.when.Volume.Control.enabled.mp4

Could Volume-Control be made compatible with eqMac?

I guess the root cause is that both intercept the system volume control via keys, as they:

  • listen to the hardware audio control keys
  • and/or also control the system volume control

Observation

Volume Control's menu item dropdown currently

Controlled Music Player:
☑︎ System (xx %)
☑︎ Music
☑︎ Spotify
☑︎ Doppler

Idea

  • ☑︎ System can currently not be disabled.
  • If you'd allow to disable it, then the user could control the system audio with the system audio keys, which are either handled by macOS itself, or by a 3rd party app which hooks into the control scheme, like eqMac.
  • But one can still remote control the apps Music/Spotify/Doppler/… with the ⌘ key when using option Invert behavior of ⌘-key
  • If you want to go with that, ofc the labels would need to be adapted a bit to be consistent.
@porg porg changed the title VolumeControl and eqMac: Currently incompatible. Possible to remove conflict? Volume Control and eqMac: Currently incompatible. Possible to remove conflict? Jan 19, 2025
@porg porg mentioned this issue Jan 19, 2025
Closed
@alberti42
Copy link
Owner

Thank you for the detailed feedback. Unfortunately, I have limited time, and I am not sure when and if I will be able to test the compatibility with the other piece of software.

Very likely the problem is related to what you described, that both apps reacts to the same events, namely when the volume keys are pressed.

It would be great if someone can look into the code and point out a possible way to fix the problem.

@alberti42
Copy link
Owner

PS: Can you post this issue report to the git repo of eqMac? The developer of eqMac may have an intuition what the problem is. Then I could help to fix it.

@porg
Copy link
Author
porg commented Jan 19, 2025

I asked them. Let's see if they react here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alberti42 @porg
0