X1B: I thought they fixed V-Vocal?

Stereo or mono clip?

As long as I select only the part I want to work on, and go slow and only use on mono files, it works fine for me.

Is there any way to reduce the lenght of the clip? I only use 5 second or less clips. I've found that works best. And instead of bouncing I drag a copy to a new track.

Well, I had thought I was on stable ground with X1B. Mixes like a master....but I Guess I shoulda tried V-vocal first.


And I bounced to a clip because I split that clip once already. Was just trying to give V-Vocal the best opportunity to work right. Apparently it doesn't want it.


Loading 6 back up again....


todd

when i see post like this.i see threrats of."am i going to have to use logic" and i dont even want to help.
seriously.if you want help there is a better way of asking.we are not getting paid to trouble shoot your daw if thats what your thinking.were merly a support group who really enjoys helping others who ask decently.we are no way affliated with cakewalk tech support department.were users helping users.do you usauly always ask for help like this?

when i see post like this.i see threrats of."am i going to have to use logic" and i dont even want to help. 
do you usauly always ask for help like this?
you need to re do the vocals and or get a new singer


Um, Okay...sorry to bother everyone. Have a great evening.

Thought of another obvious thing:

Were you going to submit the crash dump to CW support to find out what is causing the v-vocal crash? 

I have found that freezing all the soft synths in a project allows V-Vocal to work.
I get crashes when projects get large in the >4Gb RAM usage area....
If synths are frozen this reduces the RAm used and V-Vocal starts working again.
I believe V-Vocal has issues with higher memory addresses.
I wish Cakewalk would sort it out........or I might have to splash out on melodyne and I really don't want to have to.

Hi Guys... I am new to the forum although a long time Sonar user! I have always had problems with V-Vocal although it took me quite some time to discover that it was V-Vocal that was causing all my misery... To the point where I bought a new system!!! I am using a i7 system now with 32gb RAM and tons of storage!!... and guess what?.. V-Vocal still crashed!!.. After trawling through various threads on the subject I came across a post that solved the problem.. I replaced the AUD.INI file in X2!! Actually I changed the name of the file to MUD.INI and forced Sonar to create a new AUD file when I reopened sonar.. Dont know if this will work for everyone but it sure solved all my V_Vocal crash problems.. Hope this helps!

ypu may have multiple copies of the chronos.dll file on your computer. you should do a search for that file name. if you have more than one it could be a problem.

Why use X1 B? Why not use X1 D?

This is an ancient thread, guys. I doubt OP is still using X1b.

I believe this is Bitflipper's guide for V-Vocal http://forum.cakewalk.com/fb.ashx?m=2276613
Creating new threads with information pertaining the current problem and adding hardware/software specs is a much more productive approach to getting an issue solved.

  I gave up on V-Vocal. Even in X1D and X2a, I've had so many weird issues with it, from crashing Sonar, to Alvin and the Chipmunks treatment, to just simply getting poor results from it. It needs an overhaul, me thinks. Even the UI for it is so outdated and unlike Cakewalk.  

When Cakewalk plugged V-Vocal in X2's promotional videos, it actually made me seriously hesitate to upgrade. If Cakewalk had to plug V-Vocal for X2 sales, it showed me they were desperate to say anything to sell X2.