Not sure if this is just an X3c/d thing or whether it was fixed in previous versions of X3, but although I had excellent luck with V-Vocal, the one problem it did have was occasional crashing when inserted in Take Lane clips. Last night I was working on several Take Lane clips with V-Vocal, and there were no problems.
 
The other difference I noticed was that V-Vocal no longer generates a new clip on top of or behind (it never could quite seem to make up its mind) the existing clip. Some won't like this because they don't have an automatically generated "safety copy," but I prefer it as I always had to go in and delete the old clips anyway.
 
Although Melodyne is great, V-Vocal has some features I use a lot so I'm glad both are working well.

Craig I've also noticed that X3 overall handles jBridge plug-ins better as well. No more graphics glitches.
 
Used Melodyne for the first time last night since X3 and it works great, V Vocal was good to, but the occasional crashes have left me jaded.
 
 
 

Anderton
 
The other difference I noticed was that V-Vocal no longer generates a new clip on top of or behind (it never could quite seem to make up its mind) the existing clip. Some won't like this because they don't have an automatically generated "safety copy," but I prefer it as I always had to go in and delete the old clips anyway.
 
 

I'm one of the "some" - I kinda liked the old non-destructive ability to start over once you realised several days later that you didn't quite get that adjustment on that clip right - just to prove that you can't please everyone, it's something that I don't like about melodyne.

Speaking of graphic glitches, did X3 fix the "FX Chain when docked" issue of misplacing it's graphics?
 
In case you didn't notice... in X2 the plugin name screen flies off the background and hangs in "thin air" next to it. It would also stretch any background graphics incorrectly that you applied to it. Goofy!

Anderton
Not sure if this is just an X3c/d thing or whether it was fixed in previous versions of X3, but although I had excellent luck with V-Vocal, the one problem it did have was occasional crashing when inserted in Take Lane clips. Last night I was working on several Take Lane clips with V-Vocal, and there were no problems.
 
The other difference I noticed was that V-Vocal no longer generates a new clip on top of or behind (it never could quite seem to make up its mind) the existing clip. Some won't like this because they don't have an automatically generated "safety copy," but I prefer it as I always had to go in and delete the old clips anyway.
 
Although Melodyne is great, V-Vocal has some features I use a lot so I'm glad both are working well.

All part of the original X3 release :) We took out the extra clip - it was way too confusing when you tried moving the vvocal clip as you found. As a side effect of the big ARA rework some old vvocal workflow bugs were fixed.

Noel Borthwick [Cakewalk]

Anderton
Not sure if this is just an X3c/d thing or whether it was fixed in previous versions of X3, but although I had excellent luck with V-Vocal, the one problem it did have was occasional crashing when inserted in Take Lane clips. Last night I was working on several Take Lane clips with V-Vocal, and there were no problems.
 
The other difference I noticed was that V-Vocal no longer generates a new clip on top of or behind (it never could quite seem to make up its mind) the existing clip. Some won't like this because they don't have an automatically generated "safety copy," but I prefer it as I always had to go in and delete the old clips anyway.
 
Although Melodyne is great, V-Vocal has some features I use a lot so I'm glad both are working well.

All part of the original X3 release :) We took out the extra clip - it was way too confusing when you tried moving the vvocal clip as you found. As a side effect of the big ARA rework some old vvocal workflow bugs were fixed.

Aha! So it wasn't just my imagination...it does work better. Not having the extra clip doesn't bother me at all. I usually copy any track that will be subject to extensive destructive processing anyway.

Noel Borthwick [Cakewalk]

Anderton
Not sure if this is just an X3c/d thing or whether it was fixed in previous versions of X3, but although I had excellent luck with V-Vocal, the one problem it did have was occasional crashing when inserted in Take Lane clips. Last night I was working on several Take Lane clips with V-Vocal, and there were no problems.
 
The other difference I noticed was that V-Vocal no longer generates a new clip on top of or behind (it never could quite seem to make up its mind) the existing clip. Some won't like this because they don't have an automatically generated "safety copy," but I prefer it as I always had to go in and delete the old clips anyway.
 
Although Melodyne is great, V-Vocal has some features I use a lot so I'm glad both are working well.

All part of the original X3 release :) We took out the extra clip - it was way too confusing when you tried moving the vvocal clip as you found. As a side effect of the big ARA rework some old vvocal workflow bugs were fixed.

 
Noel, is there a way in X3 to set the melodyne/vv to open as an undocked window by default ?

If I don't like the results of a track that's "subject to extensive destructive processing" I sometimes use the Ctrl+Z function and start over.

Melodyne or VVocal as region FXes are not really destructive processing until you explicitly bounce them. I say that because you can remove any region FX and return to the original audio, totally outside the flow of Ctrl-Z.

bvideo
Melodyne or VVocal as region FXes are not really destructive processing until you explicitly bounce them. I say that because you can remove any region FX and return to the original audio, totally outside the flow of Ctrl-Z.

Yeah I get that, but VV had a habit of causing crashes, especially if too many instances were left open, so I got into the habit of bouncing to clip pretty quickly, safe in the knowledge that I could re-do if necessary at a later date. I don't know if melodyne would do that or not yet, or what impact it has on CPU if left open in many instances. Cloning and then hiding the original track takes is an easy enough way around it, but it's a case of old habits now I guess and something else to remember when there is so much other new stuff to take on board.