• SONAR
  • V-Vocal crashing Sonar "cronus.dll" Workaround (p.8)
2010/07/08 01:31:55
BluesMeister
The Good News: I got a response from Tech Support
The Bad News: I've already tried what they suggested and it didn't work... See Vinny's post #21 ( there's no Tech Support content in Vinny's post otherwise it would have been expunged)

Vinny *may* have a point regarding video driver conflict, my video is on the motherboard so I'll check it out.
2010/07/08 17:05:47
Featherlight
V Vocal is such a powerful tool and such a disappointment at the same time. It has, and continues to be, one of the MAJOR design flaws of Sonar. For those of us who use it in a production environment every day, this has been a PITA since its inception.

Even with all the workarounds ( delete old versions from VST list and registry before installing sonar updates, yada yada..)  it still causes system instability from an app that should well past these kinds of oversights by now.

Its the premeir DAW on PC and there are still some pretty major glitches that are several versions old now. Just my .02 cents but I think if Sonar wants to secure its foothold in an app saturated market, its going to have to do some tweaking to stay current.

Regardless if there are convoluted work arounds or not, most engineers have come to expect basic tools from their DAW tools, dependable automation, automatable/mutable busses, audio stretching that actually works while the client is sitting there, pitch correction that dosnt crash the app, buss templates that can be applied AFTER the recording process, more descriptive error reporting so we can troubleshoot problems without tying up app support.

Im hoping the increasing involvement with Roland with add some much needed code cleaning and development.  Seriously, in a world where a fifty dollar app like Reaper is legitimately competing against the big guns, times they are a changing.
2010/07/14 01:02:01
BluesMeister
Tech Support have been in contact with me and have been very helpful. I'll be trying their suggested work around which I'm confident will resolve the problem with V-Vocal. Don't ask me to post the procedure here, it's confidential information, if you want to know what to do, contact Tech Support.

-Frank-
2011/06/07 04:43:23
harikaram
Bump....

@BluesMeister, any chance of you PM'ing me the procedure so I can save the hassle of CW tech support?  I'd be most grateful!
2011/06/07 06:03:52
Bristol_Jonesey
Don't ask me to post the procedure here, it's confidential information


Did you read this bit?
2011/06/10 00:45:57
BluesMeister
Harikaram, I'm sorry, I'd be breaching confidentiality. You're presumably going through the same drama that I did with VV, if so you have my sympathy. Keep plugging away at Tech Support and they'll eventually let you in on the esoteric procedure.
2013/12/26 08:35:10
Paul in MA
I hope this saves somebody some time. On my Windows 7 computer I couldn't open my project after I saved it with few vvocal clips. In explorer, I went to c:\program files\cakewalk\shared dxi\vvocal\ and renamed "cronus.dll" to "cronus.dllold". My Cakewalk project was then able to open after spitting out a cronus.dll related error notice and I was able to remove the offending vvocal instances. I re-saved the project and renamed the DLL file back to the original cronus.dll and the project opens without problems.
 
Good Luck!
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account