Most Bluetooth devices only support 48 kHz and require audio (e.g. 44.1 kHz Redbook audio) to be resampled to a 48 kHz sample rate, which is why I avoid Bluetooth like the plague. You might try resampling everything to 48 kHz and see if it works then for your Bluetooth headset. You won't notice this issue in other apps like VLC, Windows Media Player, etc. since the system mixer is resampling everything in the background.
If the DAC doesn't have a driver, it's probably a USB Audio Class 2.0 supporting DAC and doesn't need them. All you'd need to do is use the WASAPI audio output for it, since I'm assuming it has no ASIO driver available.
Well, I found a driver under the Blutooth tab as opposed to Audio Devices and reinstalled that which seems to have done the trick. My Blutooth headset now works fine both in-and-outside of MC and it only took me 36 hours to fix . . .
And yes, you are right, the Nuforce uDAC2 doesn't need a specific driver. It has been with me through thick and thin for 12 years and never gave me a problem until now. It was always referred to by name though - not as "generic audio" or such.
Unfortunately, after installing WDM it has disappeared altogether and no longer seen on the list of available output devices in MC or anywhere else. Curiously, the ASIO4ALL still remembers it and plays just fine by selecting ASIO4ALL as output device and activated on the Configuration Panel (or from the Win 11 Start Menu). However, it cannot be used for sound in general and certainly not with Youtube or other streaming services.
The above leads me to suspect that there may be a conflict between MC and ASIO4ALL if both compete for WDM (ASIO4ALL has an option to select it just like MC). What do you think?
Torgny
P.S. I don't use Blutooth for musical enjoyment, only outside of MC for freedom of movement while doing other things - like cooking spaghetti and meatballs!