I haven't reached any problem yet, but I'm just starting to tidy up my vocals and using V-Vocal is great, but should I bounce the tracks after editing them?
I just want to know if I am putting a strain on the cpu/system resources by having many V-Vocal clips.
Thanks in advance.

Some say you should, others manage to get by without bouncing.

If you're not experiencing performance issues then leave them "live"

Whenever I use some type of pitch correction, e.g. VVocal, Melodyne, I always bounce to a new track. 

I always bounce to a new track when I'm happy with result.
 
But, as Bristol Jonesey pointed out, if you're not having any problems, then leave it.
 
I highly recommend reading bitflippers post on using VVocal:-
 
http://forum.cakewalk.com/tm.aspx?high=&m=2276613&mpage=1#2276613

The advantage to the bounce is the release of system resources...
however, if you then delete the source track to save those resources
then you've cut off your "retreat" point...that is to say, if you decide
you want to go back and try it differently or fix something, you've
cut off your means to do so...

I personally save my projects with different (numbered) names so 

that if I want to go backwards I can...and not lose a lot of work...
Also X2 allows "versions" which many use...

That choice is up to you...but I HIGHLY recommend leaving an "escape" route..

I'm a little confused that some are suggesting to bounce to a new track- Vvocal is designed to bounce IN PLACE and it leaves the original, un-altered clip beneath it (in case you change your mind). I find that feature to be very useful and I'm not sure what the advantage would be to bouncing to a separate track. I have had experiences with Vvocal causing crashes in the past. My habit is to bounce to clips when I like the result. (except when i get lazy)

BlixYZ

I'm a little confused that some are suggesting to bounce to a new track- Vvocal is designed to bounce IN PLACE and it leaves the original, un-altered clip beneath it (in case you change your mind). I find that feature to be very useful and I'm not sure what the advantage would be to bouncing to a separate track. 

The goal is to get V-Vocal out of memory so it's not using system resources. Yes, it clones the clip you are working on and you can undo what V-vocal does at any time, unless you bounce, but the goal is to not have V-vocal running while you're working on the rest of your project.


I never Bounce a V-Vocal track. I actually never Bounce anything. It's permanent once you save your project and close Sonar and I always regretted it when I used it, so I Freeze everything now.

Tracks that are Frozen can be Un-Frozen at any time even after you save your project, close it, and re-open it.

Instead of system resources I recommend bouncing because of stability. I've experienced many very nasty glitches by leaving Melodyne active in a project, that's why I'd bounce any pitch-shifter when editing is ready. 

Thanks for all the input.
I got halfway through my 24 tracks of vocals using V-Vocal and then the audio engine kept stopping, so the decision was made for me!
I bounced the V-Vocal clips and deleted the originals and it's running fine again now.
Having the safety net of the original files is fine, but it also makes you less decisive about the choices you make.
Am I correct in thinking that the original clips which lie under the V-Vocal clips (automatically muted) are still using resources, even though they are muted?
Another question. As I am getting further into the project and adding lots of layered vocals, simply clicking on Solo in a track takes about 5 seconds (every time) and the tracks all flash until the solo lights up. This happens when the song is stopped. 5 seconds doesn't sound like a lot, but it is when I just want to quickly solo each of 24 tracks on loop! Is this "normal" behaviour because there is a lot going on in my song?