Hi Gang...
 
It goes through it's processing then I get toast telling me the area is empty? It's not... I repeated this many times... In the same piece... A few select clips exhibit this... One or two were previously processed using v-vocal, but bounced to clip before attempting the vocalsync... It is also happening on clips that were not previously processed...
 
I've tried many things including bouncing to clip again and even bouncing to new track...  Closed Sonar and re-opened.... Re-booted machine... Continues to give me toast...
 
Any thoughts?

Are you talking about the message that pops saying that the guide track is empty?
 
Other than that, Vocalsync is just a nightmare in general.  Very problematic.  I was really excited about this feature but it has been almost unusable due to the HUGE issue that I and many others have run into that causes deafening white noise when you play a clip with Vocalsync enabled.  I've almost went deaf and almost blown speakers a couple of times b/c of this. Smh. 

Yeah... That's the puppy.....
 
Guide track is empty...
 
this is a new issue for me as I've been using Vocalsync occasionaly and getting good results...
 
It's even working in the song I'm experiencing the problem in, just no on all clips...?
 
Luckily I haven't had the noise problem, eh? :-)
 

A good alternative to VocalSync is to use the "multi-track viewing" in Melodyne

I have recently done this by adding a Melodyne region fx to all of the vocals

You can currently still only work (edit) one track at a time but you can see the other tracks, which makes it very useful for lining up timing of words (and key syllables) as well as checking on the tuning of harmonies

It is obviously best to do things manually but there are auto-correct options in Melodyne with the a selection of the % correction so you may find a good balance for an auto option

I now much prefer tightening timing issues with Melodyne than audio snap for vocals - but tend to still use audio snap for drums to keep the workflow going

I'll look at Melodyne some more but as I only have essential (too poor to get upgrade), I find the tools I need not there and so use V-Vocal....
 
Once Sonar has rendered a V-Vocal clip via bounce to clip, it should no longer be any different than other clips, but again I mention that some of the clips that are having this problem have not been altered since recording, and other clips work just fine with vocalign...
 
My recent experiences with vocalign have been good overall as they make their' magic decisions... I can do this with audiosnap, but it takes longer....
 

In situations like this, it's always worth your while doing a bounce to clip before invoking any of the more exotic processes we have available.

Yeah... I tried that too...
 
What is making these clips different?
 
Some were not processed at all...