stickman393
You can pry V-Vocal from my cold, dead fingers.
And in my opinion, there is no more reason for it to become "flakey" over time than there is for the Sonitus:fx DXi to do so. And they still work fine.
Cakewalk owns the code to the Sonitus:fx, and I think they've been tweaked from time to time to maintain compatibility. Also remember that V-Vocal has three DLLs: Cronus.dll, VpEnc.dll, and VpSoloDec.dll. DLL stands for "dynamic link libraries" and although I don't know the specifics about these, if there are dependencies with other DLLs, conflicts can arise. For example if a dependent DLL is overwritten, fixed, removed, or upgraded, all bets are off.
If you want to know more, here's the Wikipedia entry for
dependency hell. I'm not sure if that's the issue with V-Vocal, but it seems likely...IOW how V-Vocal performs at this point depends on what else is going on with your machine.
I was told one of the reasons Cakewalk found Melodyne so attractive as a replacement was because support calls about V-Vocal had gone through the roof, and given that Cakewalk didn't own the code, it wasn't going to be maintained by Roland, and DLL issues are so system-specific, there really wasn't much they could offer as a solution.