V Vocal problem

I would recommend starting small and working your way up on that one. Does V-Vocal run on the problematic machine in any other project okay? If not, I would start with reinstalling V-Vocal (i.e. X2) and the X3 patch you are running (c?), driver checks, etc.

That's weird, Colin.  I won't hassle you about system specs of post bitflipper's VVocalpost, as I know you know your stuff.
 
Do you have the same editions of Sonar on both machine's? i.e. X1, X2 and X3 on both of them?  Are they both same edition of Windows?
 
Same settings in Preferences, like I/O settings?
 
I'm just fishing, so excuse my time wasting.
 
Happy New Year, "Bro", as our American cousins would have it.
 

Could that project have become partially corrupted?  What happens if you copy that track's audio clips to the Windows clipboard, then paste them into a new project - on an empty audio track. and THEN try to fire up V-Vocal there.
 
Bob Bone
 

stevec
If it crashes on all projects on that machine, I would check that all three VVocal related files are available under c:\program files\cakewalk\shared dxi\vvocal\.  
 
You could also try this oldie but goodie:
https://www.cakewalk.com/Support/kb/reader.aspx/20091009
 

• All 3 files present & correct
• Cronus was in the list of excluded plugins, but re-enabling it makes no difference on this project
• I tried it on an older project and V-Vocal fired up as normal (yippee!)
• Tried it on another old one but V-vocal didn't initialize, Sonar just hung and I had to close it all down manually (boohoo!)
• I opened another project which contains multiple unbounced V-Vocal clips and the VV editor opens fine on selected clips (yippee!)

 
I think I'm going to have to just write this one off.
I can work around it by copying the clips I want to a blank project, make sure this is the only project open, do my edits then copy it all back

Hi Bob.
 
This isn't likely as I've only ever installed the 64 bit version of Sonar on my DAW