Windows 10 for DAW

[telecharge]

I wonder if Cakewalk has figured out yet what to do about that problem.

I don't know, but if you look at the post count and history of the person making (what I believe is) the best argument, it seems to have fallen on deaf ears. You may have missed my earlier posts where I stated I have shelved Sonar for the time being.

[tonedef71]

The first reboot after I switched to the Microsoft audio driver resulted in the "Blue Screen of Death". It took three more attempts to get Windows 10 to boot up without hanging or locking up. I hope this behavior does not become a regular occurrence, otherwise I am switching back to the Realtek HD audio driver for good. Windows 10 actually seems to prefer the Realtek driver; every time I would uninstall the Realtek driver, Windows 10 would reinstall the Realtek driver on the next hardware scan.

My PC actually needs the Realtek driver to be installed. It is unstable otherwise, and Windows will try to automatically install it when it is not already installed. I experienced lockups and blue screens while I tried in vain to keep the Realtek driver uninstalled from my PC and have a stable system at the same time. If I want to use the Microsoft High Definition Audio Driver, I need to leave the Realtek driver installed on my PC and running in the background:

That being the case, I am not going to bother with the Microsoft High Definition Audio Driver anymore.

I did manage to get WASAPI driver mode to work in Sonar Platinum after I discovered a few things. First off, the Realtek driver provided by Windows does not appear to have what is needed for the Sonar wave profiler to find compatible configurations. Once I uninstalled the Windows-provided and installed the driver package from the Realtek website (I had to reboot into Windows safe mode in order to achieve this), the Sonar wave profiler found compatible configurations under the WASAPI driver mode:


Secondly, I realized that Sonar's WASAPI driver mode is of the WASAPI Exclusive mode variety. I needed to enable the "Allow applications to take exclusive control of this device" setting in the "Exclusive Mode" section of the audio driver's property settings:


This would explain why Sonar kept complaining that the driver was already in use when I tried to run in the WASAPI mode; Sonar wanted to gain exclusive control of the driver but was not permitted to do so:

A more appropriate error message would have helped me to understand the problem more quickly.

Also, the fact that FL Studio did not have issues with the driver not being enabled for exclusive mode leads me to believe that FL Studio does not support WASAPI (at least not WASAPI Exclusive Mode, anyway). For FL Studio, ASIO is still the way to go.

[telecharge]

Also, the fact that FL Studio did not have issues with the driver not being enabled for exclusive mode leads me to believe that FL Studio does not support WASAPI (at least not WASAPI Exclusive Mode, anyway). For FL Studio, ASIO is still the way to go.

Looks like you have it mostly sorted. That's why I said at the beginning of this exchange that using WASAPI/Windows Audio successfully will depend on your interface/sound card and host. It takes some experimenting to figure things out.

You may be interested in this "nerdy" bit from Scott of FL Studio fame.
http://forum.image-line.com/viewtopic.p ... i#p1109619

[tonedef71]

You may be interested in this "nerdy" bit from Scott of FL Studio fame.
http://forum.image-line.com/viewtopic.p ... i#p1109619

Thank you for your guidance and input. That link you shared from Scott explains it all perfectly.

Hopefully this whole thread will benefit others in the future who try to make sense of using Windows 10 for pro audio applications.