Sacco_Belmonte

Hi guys. I have been wrestling with this for the last two years. GRRRRRRRR!!!!!!!!!!! I narrowed it down to the Windows Audio Service and the way MS implemented it since then. I have a Presonus Firestudio Project interface and I initially thought it was about the firewire card. But is not. If you see in your interface control panel, when you open an ASIO app, you'll see your interface settings change for no reason. A temporary fix is to quickly go to the windows Sound settings and going to the record tab and back to the playback tab. You'll hopefully see your interface settings going back to where they should. For that your interface should be listed and enabled in the Sound settings (Play and most importantly, Record) Furthermore, if you disable the Windows Audio Service and start your ASIO apps, no matter how much you try to abuse the ASIO driver your interface will not be affected by the bug. Therefore, I conclude MS has made a mistake and there is a nasty bug driving us MAD! the bug is either in the "Windows Audio" service or the "Windows Audio Endpoint Builder" service. I already reported the bug in the windows Feedback Hub. Please chime in there, otherwise this might be never fixed. The feedback title is: "Windows audio service unwillingly changing my audio interface settings when using ASIO" Thank you! EDIT: Another workaround is to use ASIO4all. It will bypass the windows audio somehow. The only drawback is that you cannot use daisy chained interfaces (case here). It will only detect one interface. Still, better than nothing.