rbowser
Anderton...Unfortunately it was a tech support nightmare...A lot of the crash reports Cakewalk received had V-Vocal's fingerprints in there somewhere...
I think a lot of those crashes happened to users who insisted on have large numbers of V-Vocal instances in a project, having the plugin do its thing in real time, instead of rendering the results of each instance to an audio clip.
I've never, literally never had V-Vocal cause a crash. My habit is to use it on a small clip of a few seconds duration, and once I'm happy with the results, I bounce the results to clip. V-Vocal is gone, the edit is in place, and later if I need to revert to the original, it's conveniently parked there in the track, muted, ready to be un-muted again.
I think rendering the edits from Melodyne is probably the best approach also, instead of trying to have it do its work in real time, don't you think, Craig?
Randy
I'm not sure that's the correct analysis Randy.
Back in version 6/7 & 8, I could, and did have
many track & clips with V-Vocal on them - all live, none bounced, and they never caused a problem.
But this weekend, I tried to apply VV to a single short, clean, free of bleed clip with good levels** and every time I tried it, Sonar would crash to the desktop.
** This was on a project originally created in an earlier version of Sonar, though I'm not sure which version!
The solution was to copy the clip to a new, blank project, do my V-Vocal work in there, render it, then copy it back.
If anyone else attempts to try this, make sure your new project has the same tempo map & time sig as your original project, otherwise it will get screwed!