Whenever the bluetooth speaker is connected and selected, the sound vanishes. But when I change the output device in the FxSound app to laptop audio, I can hear the sound.
Also, when the bluetooth speaker is selected in the app, I can see the sound waves of the audio playing, but can’t hear anything from the bluetooth speaker.
And yes I have tried and checked the windows audio settings, but no luck.
Can you please check if the device volume is low in system volume mixer?
Yes, I have tried that. Nothing is at low volume in the volume mixer. Still facing the issue.
Hey I think I found a temp workaround, idk if it’s supposed to be the normal repairing-flow. But if you see the device the visualizer waves, then try right click the tray icon and click on your output device again. I believe when fxsound “allows” null audio when no device detected to prevent from freaking out and crash, but it “forgot?” to remove that null-audio effect even though a new device is present. So by selecting the device in the little flyout (img below) it will work normally 5/5 times I tested. idk why it only works when you choose the device in this little panel, the big panel doesn’t seem to work for me.
I messed around with preview version 1.2.7-1.2.9 and those are the affected ones by this behavior i believe. The 
1.2.4 and 1.2.5 imo are the most stable ones cuz personally it was smoother than butter for me.
@bvijay Could you also take a look into the GUI, I wonder if windhawk is conflicting with Fxsound (tho it shouldn’t if I exclude the fxsound.exe already), recently it seems like Fxsound panel is doing the windows (WDM) multi plane overlay flipping thingy only when there no devices detected, it starts flickering when I drag and move the panel around (both minimized and maximized) [1].
anyway, I’m pretty sure for some reason it force G-sync (VRR/adaptive sync) to be on [2] and I had saw this behavior multiple times on other apps like MPV [3], ABdownloadmanager, sniffnet etc… so I’m pretty sure on my judgement here. The thing they all did similarly to fix this flickering is force the GUI to fallback to CPU backend API (software). not a big problem to me, just thought it’d be some interesting finding. (for NVIDIA users, try add fxsounds in nvidia panel programs tab, and change monitor tech from max refresh ––> fixed refresh and see if that helps, or you can also set fps cap in there as well, I haven’t tried this honestly but it fixed other apps before for me so I couldn’t see why this can’t be a temp fix for fxsound)
cheereer 
regarding the multiplane flipping for windowed apps nvidia said the flickering is windows fault so they’re not gonna fix it, and if windows doesn’t fix it then big SOL 
↩︎
(though my gsync is set to only activate for fullscreen games ↩︎
very much similar if I add some config to make a fake GUI for MPV, the flickers happen when there’s no video or sound and gone when media starts, but that is fixed with “d3d11-flip=no” for me, not sure if this is TMI but i thought maybe it gives you some idea ↩︎
