SOLVED: Not responding on launch

[dougalex]

SOLVED: See my post at end about Steinberg in Add/Remove programs

I have had Cakewalk by BandLab running for over a year on my new dell xps17 with Behringer x32 for audio interface. Today Cakewalk began getting "Not responding" on launch.

I installed latest Sonar and that also is "Not responding" on launch.

I do see it repeatedly flashes the audio interface configuration notification about every minute.

Safe mode does same thing.

Any suggestions?

Edited 18 hours ago by dougalex

[Bristol_Jonesey]

https://discuss.cakewalk.com/topic/80961-resolution-startup-crashes-with-latest-sonar-release/

 

Pinned, 4 posts above yours

[Noel Borthwick]

This is an audio driver issue not a redist problem. If you are using a non native asio driver that is your problem. 
Use WASAPI shared mode and not ASIO mode if the driver hangs when starting Sonar. We don't support ASIO4All and its variants.

[dougalex]

6 minutes ago, Noel Borthwick said:

audio driver issue

Hummm... Vegas Pro and YouTube are using my x32 Audio interface driver just fine. And cakewalk was too (for years)... until this morning.

[Sock Monkey]

Yes I have a Behringer X18 and it comes with a good ASIO driver.
But Behringer doesn’t always make it clear about the drivers on the web site. They still push Asio4all which shows me they are not Windows oriented company. They are out of touch. 
Motu is a bit like that as well. 
 

Best you could do is go to the website and download the driver again and re install it.Not the Asio4all but the proper driver. 

Then just to troubleshoot 
Make sure and disable all other audio systems in Windows settings. Only leave the X32 as the device. in the advanced settings 
Set your sample rate globally the same in windows, X32 control settings and the Daw too. 
Also allow the device to share and not have apps take exclusive control of the audio. 
Open your Daw and choose ASIO. 

There's a lot of software that comes with the X series, It is found here

https://www.behringer.com/downloads.html

Edited yesterday at 06:31 PM by Sock Monkey

[dougalex]

14 minutes ago, Sock Monkey said:

Open your Daw and choose ASIO. 

Nothing looks new in Audio drivers device manager
I never ever installed any "ASIO4all" 
Vegas Pro and YouTube are using x32 driver just fine.
Seems like something changed in Cakewalk, but I cannot "Open the DAW" because Cakewalk is "Not responding" on launch.

 

 

Edited yesterday at 05:59 PM by dougalex

[SirWillyDS12]

The Behringer x32 does have its own dedicated ASIO driver... If you were using Cakewalk with your x32 in ASIO driver mode one very simple way to determine if the x32 ASIO driver is now causing the problem is to launch Cakewalk with the x32 powered down...

Cakewalk should launch correctly with the dialog box "There are no audio devices for the current driver model on your system... ect..." After clicking that notice Cakewalk should continue to launch without issue... If it does not something other than your ASIO driver is causing the problem...

[Noel Borthwick]

Alternatively, you can force switch to WASAPI. With Sonar closed open regedit and double click and change the "Core" value listed below to 3d
On next restart Sonar will use WASAPI shared mode.

If that opens fine, the issue is one of your ASIO drivers that get enumerated at startup. Nothing has changed in this area in 5 years so if the issue just started, its exposing the incompatibility now. We have not supported non-native ASIO drivers for years because they have problems with switching sample rates and interfere with other devices being enumerated as well. Contact your vendor for a native ASIO driver if you aren't sure how to resolve it.

 

[dougalex]

I turned off all Audio Drivers in Device Manager.
Rebooted.
Sonar (latest Beta) now asked me to set Audio driver (thankfully, instead of "Not responding")
I set to x32 (all 32 channels) and Sonar (not Cakewalk) seems to be working now.

However, in Cakewalk I do get further but there is a Steinberg I cannot uncheck (I never saw before). AND... it is not in Device manager.
So I have more battling to try get rid of that Steinberg driver and get Cakewalk working.

 

 

Edited yesterday at 06:33 PM by dougalex

[Sock Monkey]

2 hours ago, dougalex said:

eir
Seems like something changed in Cakewalk, but I cannot "Open the DAW" because Cakewalk is "Not responding" on launch.

 

 

Then this might be the Redist issue so many are having. But I put my money on all those invasive drivers that have been installed. 

 

Delete that Steinberg and any other drivers that are not your x32 driver . You have to delete it in the REG EDIT app. 

 

Edited 22 hours ago by Sock Monkey

[SirWillyDS12]

You may also want to delete "Generic Low Latency ASIO Driver" from the Registry Key that @Sock Monkey indicated... Pretty sure that Cubase might install that one as well... And if you do not use the "Magix Low Latency 2016..." for anything get rid of it too... Just another useless "Wrapper" that will cause you grief...

[Noel Borthwick]

52 minutes ago, dougalex said:

I turned off all Audio Drivers in Device Manager.
Rebooted.
Sonar (latest Beta) now asked me to set Audio driver (thankfully, instead of "Not responding")
I set to x32 (all 32 channels) and Sonar (not Cakewalk) seems to be working now.

However, in Cakewalk I do get further but there is a Steinberg I cannot uncheck (I never saw before). AND... it is not in Device manager.
So I have more battling to try get rid of that Steinberg driver and get Cakewalk working.

 

 

This is your exact problem.
Irrespective of whether you use it or not ASIO4All and similar variants like this "built in" driver, cause complex problems and interfere with other drivers loading at startup because they lead to sample rates being changed abnormally. 
If you don't use those wrapper drivers just find and delete them (or rename them so that Sonar never sees them). You have 3 of them installed - god help you with that! Getting rid of them will also speed up startup of Sonar.

In the drivers page you must unselect both inputs and outputs before you can select a different driver.

 

[dougalex]

3 hours ago, Sock Monkey said:

Delete that Steinberg and any other drivers that are not your x32 driver . You have to delete it in the REG EDIT app. 

I am uneasy deleting in RegEdit, but if I want to be brave... are you saying, (if it was your computer), you would just go for it and  "right-click, delete" the folders named:
Steinberg Generic Lower Latency ASIO Driver 64bit"
AND
Steinberg Generic Lower Latency ASIO Driver 64bit"
(and presumably that also deletes their subfolders)?

Edited 20 hours ago by dougalex

[dougalex]

2 hours ago, Noel Borthwick said:

other drivers loading at startup

Thank you for leading me in the right direction! Just what I needed!
Just curious...
When this happens, Cakewalk or Sonar seems to be trying endlessly in a loop to configure audio interface or driver, making it hard for user to intervene and address more easily. I actually found random clicks will work if you hit it just at right moment between the loops (of the looping driver configuration routine).
Maybe in the future, there could be a loop count that then allows the user intervene more easily???

Edited 20 hours ago by dougalex

[dougalex]

Current status:

If I disable x32 audio driver in Device Manager, I can run Cakewalk and Sonar without problem AND Cakewalk/Sonar are using the x32 driver even though driver is disabled in Device Manager.

BUT then Windows cannot use the driver because it is disabled.

So I enable x32 audio driver in Device Manager for playing YouTube or Media Player, but then Cakewalk and Sonar are back to same problem (stuck in loop testing audio drivers upon launch).

Looks like I am now in a one-or-the-other situation now. Used to be fine before this morning.

[Sock Monkey]

You should not need to. Using a PC for audio production has always been an uphill battle to make everything work properly. These things are just another example of why you need to make sure everything is set up correctly. 

Windows apps can and will use your interface that’s what I’ve done for 15 years.  
I don’t even install any widows audio on my daw. It’s always worked. I make sure nothing has exclusive control as well as I only use 48 for clock rate. Movies are 48. 
 

I can run a You Tube and record its audio to my Daw while having Vegas and OBS open. 

This has worked using Focusrite, Motu, SSL and Zoom interfaces. The X18 is my sons but I have its ASIO driver installed on my W10 laptop and have recorded live shows. 

It just sucks that companies like Steinberg and Magix ( Vegas) automatically install an invasive driver. They are assuming you are not using an interface so supply a generic driver for use with their software.
1,000 of people have needed help due to the results. Sonar can end up with audio issues. Possibly other daw’s as well.!

If you’re insecure about the Reg editor you can always go to file and save a back up. I used to do that but I haven’t bothered for years. I’ve had to delete both the Steinberg and the Magix drivers numerous times. They seem to come back after updates and it’s super annoying. 
 

Edited 18 hours ago by Sock Monkey

[dougalex]

24 minutes ago, Sock Monkey said:

It just sucks that companies like Steinberg and Magix ( Vegas) automatically install an invasive driver.

FIXED!? OMG I was suspicious of Steinberg, but since no Steinberg was in device manager, I never looked in add/remove programs. (DOH!)

So, after all this (life sucking hours 😫), apparently all along it was the Steinberg that somehow got installed on Dec 17 that was the problem. I uninstalled it (and the older one)... and everything seems back to normal. 

Edited 18 hours ago by dougalex