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.

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.

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

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

So if Melodyne is fully responsible for fixing their own product and Cakewalk can't/won't take the hit to do anything about the fact that the current version completely crashes Sonarpdr, can you at least provide us a way through the Command Center to completely remove all remnants of the Melodyne 4.x code and replace it with the older, working 2.x code that was in there prior to the Platinum install I did?
 
I would at least like to use the plugin for fixing some stuff while we wait for whatever date the new fixes might or might not be coming.  Since it's been at least 5 months, I'm not holding out for this to start working before the end of the year.  I don't think it's an unreasonable expectation for the Cakewalk Command Center, which is control of all of the updates and installations of all of the integrated software to provide some way to put things back to a working state and allow the blocking of the upgrade until such time as it is working.  Windows Updates allow for this, I would think that the Command Center could handle it since the "ecosphere" here is so much smaller and more controlled.
 
I've seen posts of others who have tried to surgically remove Melodyne and not been terribly successful and end up with some kind of code soup.  This is all beside the "activation" pain that I went through just trying to get the install to work.  Again - seems that there would be tighter work between Cakewalk and Melodyne to make some of these processes silky smooth.  That IS what the purpose of the Command Center is supposed to be right (and mostly successful, btw).
 
Looking for guidance here to get a fully working product. 

Hey Blades, the only way I found to cleanly back out of M4 without sides effects is a system restore. There are ancillary files left on the drive otherwise that confuses SONAR even more.

I did not upgrade to M4, and "supposedly" the M4 upgrade invalidates M2. This can be overridden if the system is offline and a restore is done. The bigger hurdle is if you have a restore point prior to the M4 installation.

I do not know the official answer from Celemony about M4 invalidating M2, but I did tell them point blank that M4 was out of the question without that answer.

Ultimately Celemony would need to address this, but their customer support is not far behind CW's IMO.

Heres how i solved this for my rig (and i mean my rig)

1) uninstalled Melodyne then ran CCleaner
2) downloaded the latest version from the Celemony site
3) installed it etc.
4) chopped up the track i wanted to "Melodyne" into small managable pieces.
5) made sure autosave was on
6) after two or three pieces of work with Melodyne, did a manual save

I stress, this works fine for my set up and touch wood, it doesn't crash. Ok, so chopping up a track and doing it in small pieces adds a little to the workflow, but it doesn't crash

Just my 2 euro-cents.
Jerry

I have the full version and checked it just now and it works. 

I have found an interim work-around to the problem of Sonar crashing when creating a second Melodyne edit region.
 
If you leave the Melodyne editor open in the dock view, this does NOT happen.
 
If you create a new Melodyne region while the Melodyne editor is open in the dock view (any previous Melodyne edit in the project will work), it will open the new region in the editor without crashing Sonar. I got through a four hour mix session last night (two-hour live show, 24 tracks) using this method without a single crash.
 
FYI -- I am in contact with Ulf Kaiser at Celemony about this problem and he has been very responsive.

Well, James - that's an interesting find.  I will give the same a shot and see if it works here.  I've been able to reproduce this issue very reliably on one particular project.
 
In your contact with this guy Ulf at Melodyne, have you gotten any indication of their awareness of the issue, how long it has been a problem, contact with Cakewalk about it, and plans to correct it?
 

Starting with 2016.08 V-Vocal is also crashing Sonar when creating a region FX. I hope this is related, since they're not likely to spend as much time on something that affects V-Vocal.
 
IN my case it doesn't happen that often. Here's what fixes it for me. Freeze synths to free up memory, even if you're running 64 bit Plat like I am. Go to utilities and choose convert to 24 bit, if you're mixing formats. Erase the pic cache.
 
It'll be interesting to see if these fixes help with Melodyne

May I ask: where exactly are we on the Melodyne 4 problem? (I still have Melodyne 2 on my computer,  have downloaded Melodyne 4, but hesitate to install it until I know the hassles are gone.)
 
I have installed Sonar Platinum 2016.09 Second Release, if this helps.

Not fixed unfortunately - it just crashed with the latest version.
 
There does seem to be a workaround - move clips to a new audio track.
 
Faulting application name: SONARPLT.exe, version: 22.9.2.42, time stamp: 0x57f9caf1
Faulting module name: MelodyneCore-4.0.4.004.dll, version: 4.0.4.4, time stamp: 0x56f43463
Exception code: 0xc000041d
Fault offset: 0x0000000000de96b7
Faulting process ID: 0x2be4
Faulting application start time: 0x01d22e2d9ea0d802
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
Faulting module path: C:\Program Files\Common Files\Celemony\Bundles\MelodyneCore-4.0.4.004.dll
Report ID: ff0a7ec5-e415-4bf8-907e-eac79dcc12b3
Faulting package full name:
Faulting package-relative application ID: