App assumes control over native audio keys even if the display is uncontrollable when assume method is set to Current audio device matches a controllable display's name

[waydabber]

This might create issues in some edge cases when other apps (like a Hammerspoon script) is used for other forms of control using native audio keys, making the apps fight for control which is unnecessary. It is better for BetterDisplay to be a bit less keen grabbing control.