The issue

I insert Melodyne to a track, all tracks lose sound! Sometimes i can click the audio engine button or inputs button and the audio will come back on. After I updated Melodyne that no longer works. What i have to do to get the audio back on is go to the ASIO panel button and change the buffer from 7 to 6 or vice versa, click save and the audio comes back on and works fine for about 10 min and then i get the Rdas1089.dll crash with "SONARPLT has stopped working". If I do not save during the 10 min that it is working all changes are lost.  I can play and record fine. It is editing in Melodyne that causes the crash as far as I can see. I'm using the VS-700R interface with Sonar Platinum.

Just weighing in... same problem. I created one Melodyne region.... second one causes a crash. Here's a snippet of the Windows event log:
 
Faulting application name: SONARPLT.exe, version: 21.13.0.32, time stamp: 0x56c1f66a
Faulting module name: MelodyneCore-4.0.4.004.dll, version: 4.0.4.4, time stamp: 0x56f43463
Exception code: 0xc0000005
 
I'm going to try rendering the first region and try again. I'll report on what happens.

Yes... it appears to be a work around to 1) close the Melodyne Editor; 2) render the clip (Bounce to Clips). This allowed me to finish my work on that project. However... once I did that, I didn't encounter the issue again... so, inconclusive.

I continue to be disappointed that I still can't use this (supposedly superior to vVocal) tool because it completely crashes Sonar when used without (painful and previously unnecessary) workarounds (like bouncing every step along the way and saving between everything just in case the plugin takes down Sonar).
 
Seriously.  April.  It's September.  I GET that ti's Melodyne's issue, not Cakewalk's.  But it's definitely not MY problem!  Right?  Who should fix this?  Who SOLD it as an integral part of their product?  Me?  No.  Did I purchase from Melodyne?  No.  Cakewalk - come on.  I spent my money and expect a feature that came out BEFORE the lifetime updates to work.

Melodyne seems to be one of those quirky German companies.  The upgrade from 3.0 to 4.0 took almost five years!  And THEN they seemed to pay more attention to some crap that I doubt I'll ever use- like the sound editor.  I know I'm off topic but I've come to think of them as a weird bunch.  ...but I still use it everyday...

I've been reporting M4 Essential issues for a while now. Hopefully the Bakers are looking at it.

Blades
Seriously.  April.  It's September.  I GET that ti's Melodyne's issue, not Cakewalk's.  But it's definitely not MY problem!  Right?  Who should fix this?  Who SOLD it as an integral part of their product?  Me?  No.  Did I purchase from Melodyne?  No.  Cakewalk - come on.  I spent my money and expect a feature that came out BEFORE the lifetime updates to work.

Exactly. That times 100.
 
While not an acceptable 'solution' by any stretch, it would be a step in the right direction if Sonar was able put up a dialog box saying "looks like launching Melodyne failed - maybe (do various things) and try again", but otherwise continued unharmed.
 
Because regardless of what's going on in the German code, it's SONAR that's ultimately crashing and potentially losing our work. That is solely within the provenance of The Bakers, and should never happen!

Celemony is well aware of these issues and has already addressed the issues we reported to them. They have an upcoming release soon but we don't have any control over their schedule so if you have questions on this please contact Celemony.

Thank you Noel for letting us know.
 
And for everything else too btw.

Exception handling could be slicker to stop/ditch an offending plugin/process and revert the audio engine to a stable state. Some of this does exist now, but is also a massive programming effort to achieve and ultimately a safety blanket that "shouldn't" be required.

Icing on the cake would be a pop-up of "X plugin just went belly up, would you like us to spam tweets on them for 90 days on your behalf?"