Hi team,

First off, thanks for building and maintaining MonitorControl. It’s one of those tools that makes macOS so much more usable, especially in multi-monitor setups like mine.

Context:
I run a dual-monitor setup (let’s call them Monitor A and Monitor B):

• Monitor A has my surround sound system hooked up and is set as the main audio output.
• Monitor B is usually where I’m working — coding, designing, etc.

Here’s the thing: when I try to adjust the volume while working on Monitor B, the control applies to that monitor (and its speakers), even though audio is coming from Monitor A. I get why it works this way (it's tied to the cursor’s location) but, it does trip me up a lot.

Everyday Scenario:
Let’s say I’m deep into code on Monitor B and my music is just a bit too loud. I instinctively go to lower the volume, but nothing happens.. I then remember I need to move the cursor over to Monitor A for it to work. It’s a small thing, but it breaks flow, especially when it happens a few times a day.

Plus, the fact that the volume animation still pops up can be misleading - it makes it seem like something changed, but the output I’m actually listening from stays the same.

Proposed Feature:
It’d be super handy to have an option to lock volume control to a specific monitor or output, regardless of cursor position. That way, we could control the speakers connected to Monitor A from anywhere, without needing to think about it.

Maybe you could add a toggle between “cursor-based” vs. “fixed output” control? I see use cases for both.

Benefits:

• Keeps the workflow smooth, especially in creative or development-heavy environments
• Avoids the slight confusion & context-switching when the "wrong" audio output gets changed
• Makes multi-monitor setups more intuitive for folks who have dedicated audio devices

MonitorControl still works great and this isn’t a blocker by any means (a quick flick of the mouse does the job), but I figured this could be a nice quality-of-life improvement for others with similar setups.

Happy to provide more context or help test anything if needed.

Thanks again!