In response to stevec in post #92, I do get the crash even after applying trimming to the clip.
 
This is with SONAR Platinum 2016.05 and Melodyne Essential 4.0.4.001, 64 bit. Delta 1010 with ASIO buffer size grudgingly set to 1024.

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?
 

Vanblah, at least on my repro project, take lanes don't seem to have an impact. The project did contain a great many empty take lanes, so I removed all but the one with the three test audio clips. I still get a crash creating a Melodyne Region FX.
 
I also tried isolating one of the clips to its own take lane, and I still get the crash.
 
Also tried isolating the clip to a take lane and applying trimming to the clip. No luck, it still crashes on region creation.
 
However, when I move one of the clips to a new, vanilla audio track, the crash will not reproduce. I routed the new vanilla track to the same aux and sends as the original track, and the crash still does not reproduce. Then I cloned the track without cloning its events, moved a clip to the clone, still got no crash on region creation.
 
Cloning the track and its events results in a crash when creating a region in the cloned track. Cloning the track without events, then moving all the original track's events to the clone also results in a crash.
 
So a workaround may be to create Melodyne regions on a new track, then move the region back to the original track. Yet in my repro project, the track with the clips doesn't seem to be inherently poisonous, because I can also avoid a crash by deleting most of the other (empty) tracks in the project.

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. ???

Just wanted to toss in my input on this.  I installed the newest Platinum, opened up an old project, and over and over crashed Sonar when applying Melodyne.  This was on split clips but not on take lanes, and typically happened on the second clip I edited this way.  I hope to see this issue corrected rather quickly since it seems to be new to either a new version of Melodyne, a new version of Sonar Platinum or the combo of the two.  This renders this part of the program pretty much useless, even if there are a few possible workarounds, as it causes a complete dump.
 
Are there any official updates on this since the 5 weeks ago posting from Keith?

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.

Hi Guys
Just installed latest version Melodyne Studio 4 and every time I try and create a region fx with Melodyne it crashes  - does anyone know if any solution has been mentioned for this yet?
Thanks
Nigel
 

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?

This is a known issue and we have reported several crash dumps to Celemony. They have acknowledged that it is an issue on their end. I have not heard any updates but my assumption is that it will be addressed in their next update.
You can also follow up with them on this if you need more info. You can pass on any crash dump files to them.

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