Could be those "purists" who hate autotune devices are hacking it.  I jest, of course.  I haven't gotten around to installing Melodyne 4 yet.  It's too new and I'm watching the boards to see how those (like you) who have braved it are making out with it.  I hope you find a successful solution.
 
John B.

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.  

Well my project which had a Melodyne crash yesterday refused to open today. For every attempt to open the project I got the Sonar error/minidump splash screen. I eventually opened it in safe mode (shift open) and kept all plugs except Melodyne and it worked!! Something weird going on for sure. 

Well, that tears it for me.  I was going to do my upgrade to Melo 4 yesterday.  Now I'm holding off.  I don't want it freezing my projects if I use it.  Will watch this post to see if they resolve it.
 
John B.

FWIW, I almost always bounce my MD edits when complete so have never had any hold-over issues.  It's a habit from using VVocal in previous years.    This would at least give you the expanded palette of V4 until some headway is made for those having this problem. 
 

FWIW, I almost always bounce my MD edits when complete so have never had any hold-over issues. It's a habit from using VVocal in previous years. This would at least give you the expanded palette of V4 until some headway is made for those having this problem.

 
I have the feeling you're on the money. Every time i've had issues there's been un-rendered clips involved - not sure this is the same for everyone, but in my case it is. 

I had the same issue after updating to Melodyne 4, an instance of Melodyne would not even load, just crashed Sonar. I had to increase the buffer settings, and this seemed to have solved (or maybe just mitigated, as I haven't done a great deal of testing yet) the issue.
 
Being a 32bit install, and the lack of being able to address more than 3GB or so of memory, I've always had trouble running more than a dozen or so bars through Melodyne at a time. So, as per Steve, I too must always bounce my edits each and every time I use Melodyne. I don't run more than 1 instance at a time either, and this helps keep the crashing to a minimum.
 
As an aside, I've always been able to run much larger sessions of Melodyne as a stand aloneprogram, as opposed to an ARA session inside Sonar. This is probably related to lack of memory too, as a large Sonar project can quickly eat into what is essentially only 2.5GB of system RAM after Windows loads. Sonar can easily take another 1GB, depending on project size, leaving precious little left for Melodyne. AD2 and AK also seem to take up their fair share of memory too and can quickly crash Sonar if I go over the limit.
 
Anyway, I'm rambling now. I just wanted to let the OP know to check their buffer settings, as this does seem to effect Melodyne, perticularly running as an ARA inside Sonar.

What did you increase your buffer setting to? My Melo4 crash dummy is always at 1024 for mix n' edit.

dlesaux
Up until now Melodyne Essential 4 had been working fine but for some reason, Sonar crashes every time I try to create a region effect with it. I wonder if the latest Windows update has something to do with it. Anyone else having this problem?

Not good,I had a terrible time upgrading from the base version from X3[I now have Platinum though] to Editor,I accidentally blew 2 authorizations,and cannot install the version that comes with Platinum,as the command center then wipes out my $149 USD upgraded Editor,and only the basic one shows,thus blowing another Editor licence.
 
I loved being able to turn audio to MIDI,and then have a whole array of synth instruments play,what I played on guitar,but I haven't had any luck doing anything else,It really does seem true,that as you age new concepts are more difficult to grasp,but lately I'm getting "white out's" for many scenarios,also I cannot tolerate Windows 10,and that opinion comes from a fair amount of experience while attempting to use it on my very recently deceased Mothers Dell Inspiron,so if future versions of Platinum lock out Windows 7 Professional,I'll go back to X3,but I heard a horrible thing the other day: Waves are no longer supporting/working on X1?,this is bad if quickly progresses to X2,then X3,then Platinum-I spent a silly amount of money with Waves,their sales and marketing,made me believe I saved thousands,when all I really did was spend thousands.
 
I apologize if my rant is a bit all over the place,but I wouldn't upgrade to Windows 10 if I was being paid to!
All the best
Bob

Ok,
 
Has anyone in this thread who has had Sonar/Melodyne crash on them, updated to Newburyport?
If so, how is it now Melodyne 4 now?