QUOTE: Development has ceased.
Yet we keep seeing new versions, and the latest 1.1.26.0 has removed the Auto-Switch Output setting.
Why? Can it be restored?
1 Like
Hi William,
And has since resumed,
Has replaced and improved upon the Auto-switch function with a new Preferred Output Device function, would be more accurate,
Yes, if you remove the driver and reinstall one of the previous versions. The changes made can be found on the Changelog page (not yet updated for v1.1.26.0).
2 Likes
Preferred Output Device seems to limit choice to use only 1 device at a time, unless and until you make a manual effort to change the output.
I for one have earphones, earbuds, 2 individual monitors that are used as Monitor Left OR Monitor Right, and are also linked to work as Output Left AND Right. When the Auto-Switch (to latest detected output) was available, all I had to do was activate one or another, turn on the earphones, or remove one set of earbuds from the charging case and Voila!, my output switched.
Now I have to select the audio output and click it to switch. Doesn’t seem like an improvement to me, though I recognize that many have only one output.
Still, can Auto-Switch be added as one of the dropdown choices?
Also, glad to know development is restarted. Makes that license purchase and future donations more palatable. Besides FXsound is, IMHO, much the best choice of all the audio enhancers .
1 Like
Will echo what CarlS has said. The feature “Automatically switch to newly connected output device” was a often used feature. With it removed the user has to manually switch to the newly connected output device which can be frustrating at times depending on the output device being activated. There are users who connect more than one or two output devices. For example switching between the PC’s inbuilt speakers, to a bluetooth speaker, to wired headphones, to attached HDMI TV. With 1.1.22.6 I had to manually select the correct device versus the last connected output device being selected automatically as was done with 1.1.22.0.
Have rolled back to 1.1.22.0 to regain the “Automatically switch to newly connected output device” functionality.
1 Like
Same, same. Have rolled back and added policy to prevent an unwanted update. While waiting for a user-focused fix, I will be testing other utilities which provide the same audio tweaks.
1 Like
The Preferred Output Device feature was an extremely popular request. There was a fork in the road, and we had a discussion about which path to take: one towards elaborating on automatic switching, or one towards a preferred output device function. The latter was chosen as the wisest direction. Expecting one single piece of software to be able to cater to all desires simultaneously, is a utopian and impossible goal. Please all, and you will please none.
1 Like
The biggest problem I am having with this new “preferred Output Device” is that I don’t use my ear buds for everything, I switch back and forth all day. I have set the ear buds to be the preferred output device, but as soon as I turn off my bluetooth earbuds, FXSounds switches my preference to none. and when I turn them back on, I have to manual switch to my earbuds. This is very frustrating as it used to switch automatically and was not an issue. It’s to the point that I am looking at other sound-boosting options for my PC. If FX Sound can fix this, and allow me to set a priority for my earbuds, but also allow for the system to auto-switch when I turn them off and on, that would be awesome.
1 Like
Just tested this on the new v1.1.27.0 beta.
It maintains the selected preferred output device after disconnecting, and also automatically switches back to it whenever connected.
What is the earbud brand and model?
Have you already tried either soft-resetting or factory-resetting them, or clearing their Bluetooth memory, and completely removing, then re-adding them to your computer’s Bluetooth list?
I’m using JBL Tune 230NC earbuds. I’ve removed them and reconnected, I’ve set and reset the settings in FX Sound. I’ve tried messing with every setting I can find to fix the issue. This was not a problem until FXSound updated to 1.1.26
1 Like