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. 

mettelus
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?"

Thanks for the yucks, I like that.
 

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.

Thanks for the update Noel.
 
I got fed up with all the Melodyne crashes so have given up on it for now (awaiting a proper stable version).
 
I have been using Waves Tune LT instead which at least doesn't crash although recording pitch corrected output to an Aux track causes pops/glitches on the recorded track so not ideal. I would go back to Melodyne in a hearbeat if it was as stable as version 2 used to be.

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

joakes
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

Close to what I do, and it works for me as well. Only thing I will add is that I cannot use Melodyne on any take lane, including a flattened comp. The results can be a disaster. Take lanes disappear, audio gets corrupted. So I always copy my flattened comp to a new track and bounce it, which removes all ties from the original take lanes. As a result of this, I also never now use autosave, even though I make many new versions along the way of any song to have something to fall back to. I manually save a lot. After every successful altered region, I bounce to clip, save, and work on the next region. I don't know what's going on with take lanes, but since the last update, there have been a number of bizarre instances of mutilation of my takes. After tracking all takes now, I save a copy before moving on, so that the original takes are saved elsewhere. I mostly did this before, but now it's imperative to do so.
 
I hope this stuff with Celemony gets sort soon. It was sold to us as a highlight by the team and hasn't worked. Passing the baton is a bit rich in my view. But I accept it for what it is, and hopefully a solution is on it's way sooner rather than later.    cheers. Dave.

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

Has everyone having problems with Melodyne crashing actually contacted Celemony?  The more people that report the problem the better. The more data that they have about how the problem occurs the easier it will be for them to resolve the issue(s).  I upgraded to 4 yesterday (wish I would have seen this thread first...) then I reported to them yesterday a few hours later.  We have sent about 5 emails back and forth since then.
 
Here is the support email if you haven't contacted them: support@celemony.com
 
They requested the dump/crash files from here: 
C:\Users##USERNAME##\AppData\Roaming\Cakewalk##PRODUCT_NAME##\MiniDumps
 

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.

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.