With my system V-Vocal crashes far more with 2018.08 than 2018.07 and 2018.09 build 29. Fortunately this is fixed in 2018.09. I've learned how to very quickly switch between versions to compare things and found this was true.

So don't use 2018-08. Of course, V-Vocal has never been known stability and it has been years since the last update from  Roland. Maybe time to retire the plug-in.

scook
V-Vocal has never been known stability 

Not true. Many people continue to use it and have never experienced major issues with it. I don't believe it has been the subject of more problem reports than any other feature in SONAR/Cakewalk.
 
That said, everything else you said is on point.

stickman393

scook
V-Vocal has never been known stability 

Not true. Many people continue to use it and have never experienced major issues with it. I don't believe it has been the subject of more problem reports than any other feature in SONAR/Cakewalk.
 
That said, everything else you said is on point.

 
Actually, scook's assertion is demonstrably true via a Google search. V-Vocal definitely has had its issues. You are correct in saying that not everyone experienced them, though.
 
But even if their frequency has been no worse than average, the main risk today is that nobody at Cakewalk has its source code and Roland does not support it. Consequently, fixes are not possible.

*sigh*. I know, I'm just in denial. I love V-Vocal and never had any issues with it. Even with CbB. 

I use V-Vocal because I haven't had the wherewithal to invest in a greater melodyne than essential which can't do much. I've learned to cut and pre bounce the section I intend on working on in order to avoid those cronus.dll crashes.
 
Viva La V-Vocal!!

stickman393
*sigh*. I know, I'm just in denial. I love V-Vocal and never had any issues with it. Even with CbB. 

And more power to ya. If it works, it works.
 
I didn't want to let go of V-Vocal, either. I had invested a lot of time and experimentation figuring out how to make it work well.
 
What pushed me to Melodyne was the Studio edition's ability to edit multiple tracks at once, making harmonies easier to treat as a section rather than as individual parts. I'm a big fan of 3-, 4- and 5-part harmonies, which often resulted in having 3, 4, or 5 V-Vocal windows open at once. With Melodyne Studio I've edited as many as 8 parts as a group. Having them stacked on the same display makes it much easier to adjust timing, as well as to spot conflicts.
 
Of course, that step did require a significant investment in buying Studio, which IIRC was around 400 bucks at the time (not counting three subsequent paid upgrades). It was a leap of faith, but I haven't regretted it. One of the best purchases I've ever made.

Haven't used it much lately but V-Vocal has it's uses where Melodyne falls short and I've never had any major issues with it, unlike other features.

stickman393
*sigh*. I know, I'm just in denial. I love V-Vocal and never had any issues with it. Even with CbB. 

No issues? Is that because you use it on small 1-2 bar clips, then bounce to clip, and have no soft synths connected, which takes up memory? Or can you do whatever you want and not the things I mentioned. 
 
Do you ever have crashes? Or get blank windows with no waveforms or a waveform that sounds and looks like noise?
 
Currently I can use it for about maybe 30 min and get a crash or blank window, but then all I have to do is double click on the CWP file and I'm up and running in about 10 sec since I have a SSD HD. So I can deal with that, yet 2018.08 which I started this thread with crashed significantly more often 
 
Which version of CbB are you using?

My comment was more of a response to "time to quit using it'. V-Vocal was never that great at handling large clips and especially complete mixdowns. BUT... it does work good on small individual track clips. I haven't used it in 2018.08 so I can't speak to that part.