booksmusic
Hi abacab:
No I don't get that message. I uninstalled ASIO4all; it's still "SONARPlt.exe has stopped working." I still have copies of ASIOmulti and FenderASIO on my hard drive, and "FenderASIO -SONAR.PLT 512 Samples 44.1mhz" came up once after I uninstalled ASIO4all. I thought of uninstalling both of those as well, but I don't see why that would make a difference. Maybe someone could explain it to me?
Reynold
Edit: I have been testing the ASIO4ALL driver on my non-DAW laptop to see if I could use it for audio output from Sonar Platinum x64 2016-07. My laptop is a stock Acer E-15 with Realtek audio, with only the original OEM drivers and no other DAW software or audio interfaces. Running Windows 10 Home x64. Seems to perform OK with Platinum at low latency using VST synths. In an effort to assist the OP, the following describes my attempt to pull ASIO4ALL out from under Sonar Platinum and observe how it behaves normally in this situation. I had no trouble re-starting Sonar and re-configuring the audio options. OK, I just uninstalled ASIO4ALL from Win10 Programs and Features in Control Panel.
Then when I launched Platinum normally I got this dialogue from Platinum (a rectangular pop-up with a yellow triangle inside):
"There are no audio devices for the current driver model on your system. <
reference to ASIO in Sonar settings>
Please go to Edit | Preferences | Audio | Playback and Recording
and choose a different driver model."
So I click OK and at that point Sonar launches and the VST scan starts.
I click to open my most recent project ... and get a "Silent Busses Detected" dialogue. In other words "Master" is not routed to anything now.
I click OK on that and my project opens normally. Except no sound output now.
Now I go to Edit | Preferences | Audio | Playback and Recording and choose a different driver model." so I pick WDM.
Then I still need to reassign "Master" to my on-board sound system.
Platinum runs, but now sounds like crap [expected]
So I have shown you the normal errors that Platinum should throw if you remove ASIO4ALL.
For some reason, it looks like something ASIO related is stuck in your system and Sonar is attempting to load it, but it may be corrupted. If I was you, I would remove EVERYTHING related to ASIO on your PC, until Sonar throws a "clean" error just like I described above.
And just for good measure, I ran CCleaner's registry scan (no, I don't clean my Win 10 registry with any programs other than regedit) to see if any fragments of ASIO4ALL remained in the registry. All good except for a broken application link to the uninstaller.
However the good news is there is now an obsolete software key listed as HKLM\Software\ASIO. Great, I assume this means Windows no longer has any knowledge of ASIO. So now I get the nice clean error from Sonar, that I can fix. Fascinating