@bvijay the issue is delay is there but coming so reduce the delay but now some how detecting but after connecting suddenly not detecting it is taking some time
@bvijay issue is that bluethooth is detecting but after delay it is switch or after i click on current devices
@bvijay no reply still why
Hi @vish
Sorry I was busy with the other bug fixes and feature implementations, I will look into Bluetooth headset auto detection.
At present I have provided workaround through manual detection of the headset when the output devices dropdown is clicked.
FxSound doesn’t auto-detect Bluetooth headsets after they reconnect unless re-paired because it doesn’t pick up the device from Windows automatically. The only workaround that works consistently is running Windows’ Bluetooth troubleshooter, which forces the OS to reinitialize the device so FxSound can detect it again. No permanent fix exists yet, but using the troubleshooter or restarting FxSound after reconnect usually resolves it
Thank you for the clarification and for providing the manual detection workaround.
I understand that currently FxSound detects the Bluetooth headset only when the output devices dropdown is clicked, which triggers a device rescan. In practice this causes a delay or requires manual interaction whenever the Bluetooth headset reconnects.
In Windows, when a Bluetooth audio device reconnects, the system registers the audio endpoint and sends device change notifications. Many applications listen for these events so they can automatically refresh the audio device list when a headset reconnects.
At the moment it seems FxSound relies mainly on manual device enumeration, which is why the device appears only after opening the dropdown or restarting the application.
Possible fix suggestion:
FxSound could subscribe to Windows audio endpoint notifications and refresh the device list automatically when a device is added or its state changes. For example, implementing the Windows audio notification interface (IMMNotificationClient) and handling events such as OnDeviceAdded, OnDeviceStateChanged, or OnDefaultDeviceChanged could allow FxSound to immediately detect a Bluetooth headset when it reconnects.
This would remove the need for manual detection through the dropdown and make Bluetooth reconnection seamless for users.
Thank you for your work on FxSound and for looking into this issue.
@bvijay audio boosting in not coming properly only means if speaker of laptop is low we should hear all call any low audio into accurate high audio and clearpitch
Take my opinion with a grant of salt, but you’re overthinking it hon, believe it or not I have a bunch of problematic pair of headphones and earbuds here and though sometimes I do run into the same not-so-significant issue you’re enduring, it takes me 2 seconds to form a better practice to make things run smoothly most of the time: If I was in your shoes, I’d turn off fxsound first before disconnecting (just in the app UI, 1 click on the power button 2 seconds at most no need to exit), and just re-pair your bluetooth device as usual, another 2 seconds to switch fxsounds on, bam
it will be there — zero, nie, nada prob to the lem). I think you could try to focus on how to operate the tools efficiently moving on, it’s chiller that way yeah? 
Turn up the volume of your headphone and in the call app.
If you’re venting about Handsfree telephony effect (will fuck the volume 50% ish), oh babe you’re at the wrong tree… try Microsoft or your gear’s manufacturer instead, though you can play around with Fxsound effects to make a preset for calling, they do wonder.