• SONAR
  • V-Vocal crashing Sonar "cronus.dll" Workaround (p.3)
2009/04/16 00:11:52
Vinny
WM -

I'm not sitting at my DAW right now so descriptions may be a little off - Go to the plug-in manager and select DX plugins from the picklist on the left side. Under that pickbox is a selection for "excluded" plug-ins. Click that, and all the DX plug-ins that have been excluded for use with Sonar will show up, and cronus.dll will be one of them. Click on that and select "enable".

By chance are you using an ATI based video card? After reviewing my records and previous posts, it appears that this problem surfaced for me only after my nvidia based video card died and I replaced it with an ATI card. Could be a driver conflict...

V.
2009/04/16 13:47:53
wm0203
Thanks for your prompt reply Vinny. following your instructions, I found the cronus .dll file and enabled it and everything has been working well for a couple of hours with loops involved. I haven't changed my NVIDIA based card, so it couldn't have been that, that caused the problem.

wm0203
2009/04/16 15:41:04
Vinny
Interesting.... so that's +1 for this working for someone other than me !

Good luck, hope that continues to work for you.
2009/07/31 00:18:01
ljimmyc
THIS WORKED FOR ME!!!  Great job brutha.   Not sure but I think mine bombed after I deleted a V-Clip w/o undoing 1st.  Who knows - thanks a bunch
2009/07/31 09:32:52
michael japan
bitflipper


cronus.dll (along with VpEnc.dll and VPSoloDec.dll) is V-Vocal.

It is also an ActiveX library, which means it has to be registered in order to work. If it's not registered, SONAR will not be able to link to it at runtime and a nasty error will be raised when you attempt to invoke V-Vocal.

Registration should take place during installation, but if anything (e.g. insufficient Windows permissions) prevents that from happening you'll need to re-register it manually. I have also seen ActiveX libraries become un-registered after a successful installation, but I do not know why that happens.

To manually register an ActiveX DLL, use the REGSVR32.EXE utility. At the Windows Run prompt (or in a DOS window) invoke REGSVR32 twice, once to un-register the DLL and a second time to register it:
REGSVR32 /U "c:\program files\cakewalk\shared dxi\vvocal\cronus.dll"
REGSVR32 "c:\program files\cakewalk\shared dxi\vvocal\cronus.dll"

If REGSVR32 fails, it will say so and give you an error code that indicates why the registration failed. If you've given the correct path, AND cronus.dll actually exists, the most likely cause of failure is that your Windows profile does not have sufficient rights to modify the HKEY_LOCAL_MACHINE registry hive. The second most-likely reason is that cronus.dll itself is corrupt.

(For many DLLs, the most likely reason for failure to register is a missing dependency. However, all of cronus.dll's external dependencies are standard Windows files so this shouldn't be an issue unless you've got a serious problem such as a mismatched OLEAUT32 or something.)

The other two DLLs are static libraries and do not require registration.

do you teach math in university? That was fascinating man. I have had the problem a few times. Can you re-write simply point by point and where to find that little cronus bugger? Great post.

Michael


2009/07/31 11:49:07
bitflipper
do you teach math in university?


No, but in a previous life I taught electronics math at a vocational college. That was a long while ago; we used slide rules back then!

Registration of ActiveX DLLs is a deeper topic than you might imagine. As a software developer, over the years I have had to spend a lot of time troubleshooting ActiveX problems such as unexpected interdependencies and version mismatches. Many late-night telephone conversations with on-site installers. They don't call it "DLL Hell" for nothing.

ActiveX DLLs differ from conventional DLLs in several ways. One of those differences is that it doesn't matter where the ActiveX DLL physically resides. Applications that call the DLL are able to find it by looking it up in the Registry, where the DLL has previously written crucial information such as where it physically resides.

The calling application doesn't refer to the DLL by name, but by a unique identifier called a CLSID (class ID). Every DLL must have a unique CLSID. Cronus.dll's CLSID is "{0E7C41F0-68A2-45F5-B9C2-CC37BA99810D}", quite a mouthful. But that's how V-Vocal is known inside the computer, not as V-Vocal or cronus.dll but as "{0E7C41F0-68A2-45F5-B9C2-CC37BA99810D}".

Maybe that would be a cool forum handle. Just call me "{0E7C41F0-68A2-45F5-B9C2-CC37BA99810D}" -- or just "0E7" to my closest friends.

This is what is meant by "registration": the DLL is checking in and introducing itself to the Registry. When you invoke the REGSVR32.EXE utility, it's simply calling the DLLRegisterServer function within the target DLL, which every ActiveX DLL must include. DLLRegisterServer creates some registry keys under HKEY_LOCAL_MACHINE, the most important one in \software\classes\clsid, where the DX/DXi writes its unique CLSID, its primary entry in the internal "phone book".

Software installation programs normally take care of this as part of the installation process. Sometimes, users fix problems by re-installing software packages, which can be quite time-consuming when all they really needed to do was re-register one or more DLLs.

If you're not sure if a DLL is ActiveX or not, just run REGSVR32 against it. It doesn't hurt anything if it's not an ActiveX DLL, it'll just tell you that the DllRegisterServer entry point was not found. It also doesn't hurt anything if the DLL has already been registered (as long as you're re-registering the same DLL - you can get into trouble if you have multiple versions of the same DLL on disk; re-registering a different one de-activates the previous one.)

Cakewalk gathers most DX (ActiveX) effects and instruments under a folder named "shared dxi" under the main Cakewalk folder (usually program files\cakewalk). In there you'll find V-Vocal and most of the other DXi's such as TTS-1 and Dreamstation. Not all of the DLLs in there are ActiveX, though. V-Vocal, for instance, consists of 3 DLLs, only one of which (cronus.dll) requires registration. But again, there's no harm in attempting to register a DLL that doesn't need it or re-registering one that's already been registered. So register away.

Want to explore further? DLLs often call other DLLs. Those other DLLs are called "dependencies", because the top-level DLL depends on them to be present in order to work properly. Sometimes, an ActiveX DLL will fail to register because a dependency is missing. Or worse, the DLL registers OK but subsequently crashes because a dependency is missing.

There is a tool you can get from Microsoft that shows file dependencies for any DLL or EXE. It's called DEPENDS.EXE. If you run Depends against cronus.dll, you'll see that cronus relies on 10 other DLLs, and each of them has their own dependencies, and their dependencies have dependencies. Fortunately, for cronus.dll the dependencies are standard Windows files, so they're unlikely to be missing.

DEPENDS.EXE can be fun. OK, fun if you're a total geek. Use it to see what dependencies SONARPDR.EXE has - a boatload of 'em!

Mmm, this was kind of a rambling response, but maybe it's piqued someone's curiosity and taken a little mystery out of DXi registration.
2009/07/31 12:43:08
j boy
V-Vocal is still not ready for prime time.  I don't really care --why-- it crashes, I just care that it does.  We paid for something that doesn't work as advertised is the bottom line.  CW needs to fix it once and for all or bundle Melodyne LE next time, please.
2009/08/01 15:55:07
vocalid
j boy


V-Vocal is still not ready for prime time.  I don't really care --why-- it crashes, I just care that it does.  We paid for something that doesn't work as advertised is the bottom line.  CW needs to fix it once and for all or bundle Melodyne LE next time, please.

I concur! V-Vocal was one of the main selling points for me to get Sonar. I've now bought Melodyne as Cakewalk doesn't seem to be interested in fixing it 
2009/09/02 14:02:41
Sacalait
Thanks Vinny!  I was having the EXACT issue in the last few days- V-Vocal constantly crashing Sonar.  So I decided to do a search here and found your post.  I found exactly as you stated.  Much appreciated!
2010/02/10 10:59:33
alexdamk
Hi...I have this problem with cronus.dll too, and I get not open my project because this problem. when i open my project it appears and reset my computer. I tried to enable the the cronus but not resolved. What do i do? I need to continue my project! thanks...
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account