Version 2.1.1 of Melodyne editor is ready for you to download. The update offers support for the AAX plug-in interface in Pro Tools 11 and contains a variety of bugfixes and optimizations, which is why we recommend it to all users.

For you, the update is free of charge. The simplest way to get your personal installation program is by using the "Check for Updates" function in Melodyne's Preferences dialog.
 
http://www.celemony.com/cms/index.php?id=melodyne211&L=0

Just got round to updating mine - I have never used it greatly because normally we don't melodyne vocals but it was always just in case sort of thing.
Also it always seemed a bit buggy on my system.
However I have just tried this latest version and it seems vastly better - in fact the first thing I tired it on was some acoustic guitar which it processed brilliantly without any adjustment etc from me. 
Really surprised as I did not expect it to work that much better - perhaps something strange with my set up?
Anyway happy to have it working so well now
Nigel
 

Haven't updated to 2.1.1 yet but Melodyne has worked for me pretty well lately. I do freeze the tracks after melodyne has done it's thing though.

I did have a strange problem today with Melodyne 2.1.1: when used in X2a I can only do one edit as the next edit resets the previous one. Really weird. Anybody seen this???
 
Everything worked perfect with Melodyne 2.1.0 and the only other changes to the system were installation of some WAVES and FabFilter plugs ...
 
I contacted Melodyne support and it took only about 10 minutes (!!!) to get a reply (pretty cool response time). However, the message was they can't reproduce it ... so I fired up my backup system (different PC, but identical software installation) and there it works, either (at least on the projects that are available on the backup) ...
 
So now I need to start digging deeper on the main DAW. Any hint would help.
 
Will start with re-installing Melodyne ... can't re-build that particular Sonar project because that's close to final and way too much work ...
 
 

Hi  -I've not had that specific issue with X2, but I did have similar, non reproducible graphic glitches quite a bit in the short time I used X2  -I did the one and only upgrade and that didn't help so went back to X1.
Have you tried X1 on the same machine to see what happens? I found once I had gone back to X1 (same machine, windows 7 64 bit, 64 bit Sonars X1 and X2) the strange behavior stopped - so it seemed to prove to me that the graphic issue must have been with something different in X2 and the way it interfaced with my specif machine / set up.
 
Whilst as I said I did not have that specific problem in X2 it does sound a bit "graphical" to me.
 
I do think trying X1 and seeing what happens could be a really good starting point.
Nigel

thanks nigel.
haven't thought about that since i quite happily used x2a for the past 8 months...
I still got x1 installed - so I'll give that a try in a minute ...

it did work on x1 right away - so i have a fallback solution ...
and re-install seems to have fixed it for x2 (1st test worked, still need to do the actual editing) ...
 
 

Glad to hear that - but these strange, almost one off problems with X2 did worry me - that's why I thought, as a temporary (ha ha) solution I would go back to X1 and await the next bug fix for X2!!
You'll have to let us know if this reoccurs when using X2 after your reinstall
Cheers
Nigel
 
 

did quite a bit of editing today using x2a + melodyne 2.1.1
got it all done and yesterday's problem has gone (it definitely was a weird sonar x2a issue)
 
yet, sonar did lock up twice (forcing me to reboot) while editing 3 melodyne tracks in parallel. the project has become fairly large in terms of plugs & tracks in use, still this should not happen ... didn't lose anything due to auto-save working fine, though ...
 
now, melodyne edits are bounced and melodyne tracks archived ... so it should all be downhill from here :-)