For anyone experiencing this problem, if you first use the Trim command on all clips you want to simultaneously use with Meldoyne/ARA, does the error still occur?
 
 

Thanks for the report.
 
Viva la resistance!

Just wanted to give an update on this.
We had sent the fault reporter crash dumps we received to Celemony, they are looking into it.
Thanks for those that sent them in.  

I'm having the same problem with Studio 4.  It's the first time I've had Platinum crash.  It sent error reports twice.  I had to use Studio 4 in stand alone mode to be able to use it at all.
 

I've just kind of skimmed through this thread but I noticed something yesterday that may be relevant.
 
I've been experiencing lots of Melodyne crashes as well, but I noticed yesterday that it seemed to occur on tracks with lots of take lanes, and it seemed to occur on takes that takes overlapped one another.  When I rendered the takes out I was able to create a Melodyne region.  
 
I'm wondering if Melodyne is interpreting the take lanes as multiple tracks?
 

danbottomburp
Slightly off topic but i just wanted to check , I am definitely using Melodyne 4 but in CCC it is listed as Melodyne 2. Is this the same for everyone  ?
 
I have even logged out and back into CCC and it still lists it as Melodyne 2 

I'm seeing the same thing here - I received an email on 5/12/2016 from Celemony announcing the availabliilty of Melodyne 4 Essential. I thought I would just wait and let the Melodyne update occur through CCC. The email from Cakewalk announcing Sonar 2016.05 arrived two days ago. I updated through CCC yesterday, but no Melodyne update was included - so I went to Celemony to get the update and install it.  Seems to work fine in SPlat on my Win 7 PC - but I did notice that CCC says I still have Melodyne 2 Essentials - no Melodybe 4 found anywhere in CCC. ???

Has there been an official Celemony resolution to the above issues todate?  I keep getting prompted by Melodyne that there is an update but I'm hesitant because of what I've been reading here.

It seems that this issue has been happening in various system configs and version combos since some time in February at least.  Sure would like to see some input from the Bakers as there seem to be some people unaffected by this.  There must be something that triggered the incompatibility.
 
My big issue was that I HAD to upgrade to Melodyne 4 from 2 (which I had via X3) because no matter what I did, there was no way to authenticate to their system with the old serial, the Cakewalk "fixed" serial, and the activation system.  I upgraded to Melodyne 4 with a brand new purchase of Sonar Platinum and immediately had repeated crashes.  Unfortunately, this was my intro to the new Platinum (to me) and the Lifetime upgrades for which I was so excited. 
 
To resolve this, I had to go back to an X1 installation to get v-vocal reinstalled so my old projects would work at all without a bunch of useless audio that I couldn't play because v-vocal was broken and when I replaced these clips with MElodyne, that was broken too.  Unfortunately, my X3 didn't exhibit these things, so my first intro to the Platinum system was a series of predictable crashes.  And then I find that these have been happening for months without a fix and decent documentation in at least two threads (one here and one in the Feeback Loop forum leading to this one).
 
Don't get me wrong, this is not the "deal killer" or anything, but the motivation for me to "come out of hiding" after 2.5 years was to get to a new Sonar that was upgraded frequently and bugs squashed rapidly.  When I've found that several of MY long-standing bugs still exist and this one, around such a prominent major bullet point as Melodyne are not fixed, it's concerning...
 
All that said - what's up with this?

Thanks guys, so not fixed yet!
Noel, I do take on board that this is a Melodyne issue, but as Blades said above, Melodyne integration in Sonar is / was a big selling point  - it seems just a tiny bit disingenuous to now just pass it off as a Melodyne issue and be done with it - if this has been an issue since February as Blades says, as a big customer of Melodyne, surely you are the ones that should be applying pressure for them to get their proverbial fingers out and get it fixed. Having dealt with their "customer service" some years back, I will not be wassting my time contacting them and will hope Cakewalk will have more luck with them than us mere Melodyne customers.....Please give them a good kick Noel!!
Thanks
Nigel
 
 

JohnEgan
I've been having all kind of what I thought were midi issues, with a recent project (revisited older project that had no functional issues previously), coincidently since Melodyne 4 Studio and Manchester update, I had converted an analog bass line to midi from Melodyne, ever since at some point into editing and playing it wont stop playing endlessly and shuts down audio engine, mouse still works allows various selections, even rewind on transport  jumps backward, when held down and jumps back to play point, but stop or pause don't work I have to click close "x" icon to close project, and Sonar subsequently crashes. I can reopen and edit for a while, until it happens again. I hadn't made the Melodyne connection till I saw this post, so now not sure midi or Melodyne or both, and/or Manchester.  So various possible update coincidences at same time to consider in my case. I'm still on Win7x64 though. I'm reluctant now to open any other projects in case they become corrupted as well.
(I thought it might be an upgrade conspiracy by the Win10 people LOL, guess not) 
 
I should add I get Windows Stackhash error, their fix is to disable DEP control on application exe file, yet wont allow for 64 bit applications.  

I'm having the exact same issue. Added Melodyne 4 to 1 track, everything seemed to go OK. Got ready to add to the next track, boom, crash. Re-booted the computer and gave up for the night. Next morning, project wouldn't open. Opened it in safe mode, got to the last bit of the load, boom...crash. It bears mentioning that my system is normally rock stable.

Well, as far as big sticks go, there should be plenty of rejected Les Paul necks about.

pwalpwal - thanks - so it would seem a Melodyne / Sonar issue - an even bigger reason for Cakewalk to shake a big stick at Melodyne perhaps

Pwalpwal, that method doesn't use ARA at all. Not sure if that makes any difference though.
 
Melodyne is less than perfectly stable for me too, unfortunately. It's the only thing that crashes Sonar fairly regularly for me, though there doesn't seem to be anything specific that produces it. Or at least I can't find it. But if I get a crash, nine times out of ten I just hit CTRL+M to create a Melodyne clip.