[NobodyNada]

I needed something like this a few months ago. I use my MacBook to run my (musical) keyboard rig for live performances, and use low-latency wireless headphones for monitoring. The headphones have a transmitter dongle that plugs into my laptop, and the dongle sends a "play/pause" command if I press a button on my headphones...causing Music to launch and begin playing audio out of my default output device. It doesn't even care whether my headphone transmitter is selected as the default output device; in a complex multi-device setup, I can press a button on my headphones and it will happily play audio out of some other device.

This is problematic because if I were to accidentally hit the button in the middle of a set, and it decides to default to whatever interface is connected to the P.A. system, then now I've just started blasting some random song at full volume to everyone in the venue.

(It's not an immediate problem for me anymore because I've reworked my hardware setup such that the dongle connects through my audio interface rather than directly to my laptop, meaning my laptop no longer receives "play/pause" commands from it. There were additional reasons for this rework, but preventing this misbehavior was absolutely part of the consideration.)

It's absurd that a premium device marketed to creative professionals has unconfigurable behavior like this which is so unacceptable for a live show.

[scrumper]

That'd be a terrifying setup for me as a live player! I'm curious where you found low latency wireless headphones though.

Have a look at Loopback - very mature app now. I use this for doing live and studio routing, you set a live profile so that only your soft synths actually get an output and Music (and FaceTime, system, whatever) get sent to the musical equivalent of /dev/null. So an accidental press of "Play" has no effect (beyond perhaps catastrophic stuttering as Music.app opens.)

My laptop is disconnected at the moment so it's full of "missing device" notifications but this screenshot[1] will give you an idea. Profiles on the left, apps in the next column, routing to mixer channels (I have a multichannel interface) next and then "monitor devices" which can be multiplexed.

[1]https://imgur.com/gG1hG2c

[NobodyNada]

The headphones are from AIAIAI: https://aiaiai.audio/headphones/tma-2-studio-wireless

Loopback looks nice, but I prefer to keep the routing entirely within my DAW (or my interface where possible) to keep latency to a minimum, particularly since I'm already using wireless headphones that add 10ms latency.

Another mitigation I now have is to use an aggregate device that has BlackHole on the first two channels rather than the main outputs. That way, if I accidentally start playing audio, it gets harmlessly sent to the void; and it also means I can easily capture and forward it in my DAW if I actually want to play PC audio (for example, listening to a recording during a rehearsal).