mudgel
Sound forge and Vegas spring to mind. Both use DX and VST, will select a windows driver model by default and just run immediately after installation. I know because I've tried it. They also allow you to use ASIO if you choose.
While I agree SONAR setup could be easier if users are willing to accept poor latency performance, I think 90% of the issue involves Windows. The only time I've had the experience Mudgel describes is on the post-OS X Mac. The low-latency Core Audio interface protocol is the
only Mac audio protocol. Software and hardware knows what to look for and what to find. Core Audio even allows for easy aggregation.
Yes, Vegas just works but that's because it defaults to the inefficient Microsoft Sound Mapper. If SONAR defaulted to that, we'd be getting posts like "latency problems" and "strange distortion at low latencies" or even "can't adjust latency."
The unfortunate reality for Windows-based musicians is that the most "universal" low-latency protocol for Windows is not from Microsoft and not part of the OS. That means the user has no guarantee of being to access that protocol. There is also no guarantee an interface will work with WDM/KS, which is my experience is decent but not equal to ASIO. Who even knows what WASAPI and WAVErt are...DirectSound...MME...(and don't get me started on ASIO4ALL).
So then it's necessary to select ASIO and it's associated I/O, and that's not easy in
any program. I won't name names but I've used no Windows program that didn't require multiple steps to get it to speak ASIO to an audio interface.
What would be cool is if upon opening SONAR for the first time, you had to choose one of the following and SONAR would act accordingly:
- I am using an external interface and its ASIO drivers are installed
- I am using a computer's internal sound card
- I have no clue. Start the wizard and yes, I realize this will now take up 15 minutes of my life
But back on topic...yes, thanks to the Bakers. They done good, and continue to get better.