You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, thanks for writing this tool, it's really handy.
Secondly, a useful feature would be a way to switch both the input and output with a single action. Usually, if I want to switch to my bluetooth headset, I want to switch both my speakers and my microphone to it, for example. One way would be to associate ports which are on the same card, but it might also be good to have options in the configuration file to allow linking specific inputs and outputs.
Obviously, sometimes one will still want to control inputs and outputs individually, so there should be a checkbox toggle to control this behaviour. If the box is checked, then clicking on an input also changes its associated output (and vice-versa) - if the box is not checked, then the the app behaves as it does currently.
The text was updated successfully, but these errors were encountered:
You open an "options" pane and then there is a tab in there that allows you to create "sets". A set is added at the top of the drop down for quick access as this is probably what most people would want to use if they create it. Clicking on a set just sets all items in the set automatically!
I might look into creating a PR for this eventually but don't get excited, i'm a busy man :)
I like your concept @crazycodr. There's currently no UI except for the menu itself, to minimise the effort required I'd propose starting with just the JSON config that's already in place.
Firstly, thanks for writing this tool, it's really handy.
Secondly, a useful feature would be a way to switch both the input and output with a single action. Usually, if I want to switch to my bluetooth headset, I want to switch both my speakers and my microphone to it, for example. One way would be to associate ports which are on the same card, but it might also be good to have options in the configuration file to allow linking specific inputs and outputs.
Obviously, sometimes one will still want to control inputs and outputs individually, so there should be a checkbox toggle to control this behaviour. If the box is checked, then clicking on an input also changes its associated output (and vice-versa) - if the box is not checked, then the the app behaves as it does currently.
The text was updated successfully, but these errors were encountered: