I adopted the habit long ago, of committing V-Vocal changes immediately via Bounce to Clips.

Me, too. There is also a copy of the clip (sometimes on top of it, sometimes underneath the bounced clip w/ a red circle/arrow through it on the clip and it's kinda greyed out). I always delete that, too. No issues when doing these things. HTH, Shep

ORIGINAL: jshep0102

I adopted the habit long ago, of committing V-Vocal changes immediately via Bounce to Clips.

Me, too. There is also a copy of the clip (sometimes on top of it, sometimes underneath the bounced clip w/ a red circle/arrow through it on the clip and it's kinda greyed out). I always delete that, too. No issues when doing these things. HTH, Shep

FYI...the "red circle/arrow through it" bit is simply a muted clip. You can un-mute it by selecting it and hitting 'Q' on your computer keyboard. SONAR is being good to you by making a copy of the clip before you mess with it so, even if you commit your changes with a bounce, you can still go back to the way it was before (so you can screw it up differently the next time).

Another issue I was having with V-Vocal earlier this week was this "invalid argument" error dialog box. I had two V-Vocal clips (before bouncing) open. I did some research and realized that there have been problems when having the loop construction view open as well. I discovered that the loop construction window was open under my track view. I also had two real time external effects going. At this point, I think I just had too much going on at once. When I got the invalid argument error the second time (of course it completely freezes the machine, requiring hard boot), I decided to take off the external inserts, close loop construction and then do one V-Vocal clip at a time.

Im rambling, but I wanted to weigh in on some of the issues Im encountering as I push the system.

Regards,

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.

In my system, V-Vocal just seems to be unstable in general regardless of cronus.dll status. V-Vocal does run okay for the most part but then as I have it keep looping for editing, the stability of the system decreases significantly often causing SONAR to crash.
I'm a bit confused about this cronus.dll file. Even with it being excluded in the plug-in manager, V-Vocal does run in my system. I wonder if there would be any difference in stability with bitflipper's 'regsvr32' advice. I'll try it out and see if that improves the system stability with V-Vocal.

Bitflipper -

I think we know that cronus.dll is, or is a part of, v-vocal. This is not a case of v-vocal not working. It is a case of it working fine and then with multiple clips open it causing an un-handled exception error which causes Sonar to crash, which the dialog always names "cronus.dll" as the offender - Different problem. Were cronus.dll not registered, it would not work at all, and wouldn't show up in the plug-in manager at all, either excluded or otherwise. And yes, I have tried un-registering and re-registering "cronus.dll" and it didn't fix the problem.

Everyone is talking about how they fix this crashing problem with workflow, by immediately committing changes to clips by freezing them and closing v-vocal. That workaround works for some people (for me too), but does not fix the underlying problem. The workaround I'm suggesting doesn't fix the problem either, but it seems to stop the crashing due to the un-handled exception error on MY system. I'm interested in seeing if it limits the issue in other systems as well. If it does, then we may have additional clues for Cake TS (or Roland) for a real fix, so we don't have to do workarounds, and we can work with v-vocal with multiple open clips without having to worry about Sonar crashing, and making a great program that much better and more solid.

I am fully aware that this "shouldn't" be a fix, and in my mind it's not - its a workaround. Someone at Roland probably left some parameters exposed in the cronus.dll that shouldn't be, which is causing this behavior (as a completely wild, but not entirely uneducated guess). All I can say is that it works for me, and I'm trying to find out if that's dumb blind luck or if there's something behind it!!

Have a great day...

V.

If it does, then we may have additional clues for Cake TS (or Roland) for a real fix, so we don't have to do workarounds, and we can work with v-vocal with multiple open clips without having to worry about Sonar crashing, and making a great program that much better and more solid.

This problem with V-Vocal has existed literally for years. It is doubtful anything will be done about it any time soon.

Many users experience the V-Vocal bug. It comes up very frequently. For proof, just do a search of this forum.. The bug has existed since Sonar 5 when V-Vocal was first introduced.

The workaround of working on 1 clip at a time, and bouncing to clip, works 100% of the time for most users.

Cakewalk by lack of action must feel that the work-around is to be considered the fix... It certainly is not on any burner to be addressed. If it were a hot issue, they would have fixed it 3 years ago...

This problem with V-Vocal has existed literally for years.

I know...

It comes up very frequently. For proof, just do a search of this forum

I did...

The bug has existed since Sonar 5 when V-Vocal was first introduced

Very likely - I still used AT until S7, I think...

The workaround of working on 1 clip at a time, and bouncing to clip, works 100% of the time for most users.

I know this too - but I think the workaround I'm suggesting is easier than that one, and so may be attractive to some people.

I'm not trying to re-invent the wheel, I'm just sharing something I found that made my life easier. If in turn, we find something that makes it easier for Cake to fix something, is that not good? Use the other workaround if you want to. Try this one if you get a chance and see if it makes things easier for you. Report it to Cake TS if it does and if enough of us do, we may have a fix released in the future. In the mean time, I can mix with multiple v-vocal clips open on my machine and Sonar remains stable, and that's a good thing!

V.

ORIGINAL: kevo

Cakewalk by lack of action must feel that the work-around is to be considered the fix... It certainly is not on any burner to be addressed. If it were a hot issue, they would have fixed it 3 years ago...

Yes, they probably don't consider it a *workaround* but it's simply the way you're supposed to use V-Vocal.

Vinny
Could you tell me how to enable the cronus.dll file please?
I am having exactly the same trouble with V-Vocal. I have looked in Tools-Cakewalk Plug-in Manager but can't see the file.
Any help would be appreciated.
wm0203