Sean Chapman

Not quite as easy as it appears on the surface. Looks like it will require work between the bluetooth/device management api and the coreaudio/device topology api. This functionality probably belongs...

Thanks for the detailed issue report! It's superb! There is known issues with the GUI technology (Windows Forms) and High DPI settings. Most of the UI positioning is done by...

Thanks! Yeah I'm not sure why Windows makes such a simple task so obscure. Yep totally valid request, and is "impossible" to do int v1.x due to how the hot...

Yep, you're totally on point. The hotkeys in 2.0 now do "actions" instead of just setting default devices. I've created three actions so far: - Cycle through favourite devices -...

@malikoth Here's a good as place as any. It's certainly a v2 feature. In v2, there's a handful of "events" that you can "bind" to and do anything you want....

Related: https://github.com/xenolightning/AudioSwitcher_v1/issues/2131

Yup - this is the right place for such feature requests :) Seems like a useful feature. I assume it's a toggle for mute/unmute for the default playback device only?

What's the current behaviour? Does it detect the Volume Up/Down key without modifiers? I don't have access to media keys to test this, so fixing it will be difficult

Your English is good, can understand it without a problem :+1: My work PC has media keys, I can reproduce the Shift + VolumeUp issue. It's a strange one, I'll...

Ok cool, it must have something to do with the combination causing issues. Will raise another bug for the hotkey issue, not sure if I can fix it at this...