as i have found out, some Celemony issues are not taken very seriously by Celemony.  they will punt if they don't feel like helping you.  for example, Melodyne Studio 4 will not install on my backup PC (a PC where all my other music software works fine).  i get install errors; i get VST scan errors.  Celemony didn't feel the need to help out a customer who was getting a bit angry during the course of 2 months of pathetic "customer service," so they punted & told me to contact Cakewalk about this, which i did almost 2 weeks ago . . . and i haven't heard anything back from Cakewalk yet.  terrible all the way around

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.

A brief update
Tried using Melodyne as an FX insert not Region FX.
Inserted, it opened ok and processed OK - all was great until I tired to freeze track, then it crashed  - after the crash the project would not open until Melodyne removed.
 
Whilst clearly a Melodyne issue, I think someone at Cakewalk / Gibson should be shaking a VERY big stick at Melodyne to get things sorted!!
 
By the way, anyone know if Melodyne is such an issue in other programs with ARA integration - I believe Studio One has this??
Nigel
 

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

i don't use it much, but just had a quick play in studio one 323:

• dragged a loop into track, set loop markers to 4 bars, hit transport play loopmode
• added melodyne essential 404 vst3 in track fx bin
• clicked "transfer" to get some blobs
• after the first loop, fiddled around with said blobs
• dragged another loop onto empty space creating second audio track
• added melodyne essential 404 vst3 in second track fx bin
• clicked "transfer" to get some blobs
• after the first loop, fiddled around with said blobs
• hit transport stop & wrote this
• went back and rendered the 2 tracks to audio (melodyne gets removed from fx bin)
• plays fine/as expected
• i5 laptop, win10, 8G, realtek via asio4all (woo! scary!) @ 44/24, 1024 sample buffer

so no, not really seeing any issues, unless i misunderstood, let me know if you want something specific trying?

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

A thought - just wondering how many other Melodyne / Sonar users now have a very expensive program (Melodyne) that will not function????

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.

As I mentioned before these issues are from Melodyne and not SONAR. The good news is that I got word from Celemony that they identified the cause one of the most common crashes and will be soon releasing an update to address it.

Noel Borthwick [Cakewalk]
As I mentioned before these issues are from Melodyne and not SONAR. The good news is that I got word from Celemony that they identified the cause one of the most common crashes and will be soon releasing an update to address it.

Well, glory be!