Jump to content

Cakewlk/Sonar Hangs in Background Processes


sjoens

Recommended Posts

At least one reason for Sonar is upon initial startup when the VST Scan "Toast" message gets toasted & stops responding and hangs indefinitely for some reason.

Edited by sjoens
Link to comment
Share on other sites

By Sonar, are you really meaning Cakewalk by Bandlab, or an older version of Sonar?

That will likely be a plugin issue rather than a Cakewalk issue.

What you might want to do is enable “Generate Scan Log” in preferences - File - VST Settings

The generated file will be in %APPDATA%\Cakewalk\Logs\VstScan.log

This might give you have indication of which VST is causing the issue.

Then you can see if you are using the latest version or a different iteration of that plugin.

Link to comment
Share on other sites

No doubt. In this case Sonar is the victim, as I go b&f between 32 bit Sonar & CbB for older project migration and Melodyne 4 usage. 

(Melodyne 4 won't run under 64 bit Win11 & Melodyne 5 has no 32 bit version.)

Both have "Automatic Background Scan" checked, but of course, Sonar does not have "Generate Scan Log".

Link to comment
Share on other sites

32 bit Sonar scans different folders, so that could be a factor. They each hang so sporadically that there could be hardware issues to blame as well.

Sometimes I have to reboot the system several times before everything plays right together.

Link to comment
Share on other sites

What you might want to do in this situation is temporarily add the folders that 32 bit Sonar scans into your CbB VST settings.  Then get CbB to do a VST scan (with logging enabled) to see if it hangs CbB. 

If that VST scan does hang in CbB, then look at those VST logs to help you troubleshoot.

Of course, remove the 32 bit Sonar folders from CbB when you are done.....

Link to comment
Share on other sites

  • 2 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...