CWBL won't launch, gets stuck on driver

[OPunWide]

I've been trying to get ready for the new Sonar, and as part of that I reinstalled the old Sonar 3 Producer. Why? I have about 300 Cakewalk/Sonar projects and I'm trying to make sure than most of them transition properly with all the plugins.

Sonar didn't work right, so I add ASIO4ALL (which previously worked on a different computer). That caused other problems, one of them was a warning that CWBL didn't work well with ASIO.

So I uninstalled the ASIO4ALL. Now Cakewalk won't launch.

I'm using an old AudioBox USB interface, and it works fine with Windows 11. What doesn't work is launching CWBL.

It gets the small splash screen, and behind that screen it's doing driver profiles. Then those close, and it gives up.

I've tried launching with SHIFT, rebooting, etc.  It's writing the driver results to "\AppData\Roaming\Cakewalk\Cakewalk Core\WaveProf.Txt" and that looks reasonable (I'm guessing).

I've rebooted, powered down, tried launching with the AudioBox unplugged and then plugged in as normal.

Any suggestions? I'm very hesitant to go to Sonar 2025 unless the older programs are working right.

 

[57Gregy]

Au contraire. Cakewalk recommends using an ASIO audio interface, just not the RealTek ASIO driver, or any of the wrappers like ASIO4All or any generic drivers . I'm about to run out but someone should be able to help you soon.

[OPunWide]

Thanks to @57Gregy I persisted with ASIO and got old Sonar to work using ASIO, without ASIO4ALL.

Now I probably just need a way to force CWBL to start over in deciding which driver to use.

[OutrageProductions]

As @57Gregy started on; completely delete anything that is ASIO4ALL related on your system and in the registry.

You may need to do the same with the Realtek driver system, but it causes lesser issues in about half of all systems, and may reinstall if it is on your MOBO.

The Audiobox should only use the Presonus ASIO drivers that were either supplied or can be DL'd from their support pages.

I've used one for 18 years with RT latency as low as 5.3ms and no other issues.

Any time you see anything relating to "wave profile" (or derivations thereof,) you are using the Win OS WDM/Wasapi style driver set, which have far inferior response specifications. 

Edited 2 hours ago by OutrageProductions