davisb24
Still beta testing. Despite all the frustration Celemony has been very responsive in working through the issues and they are making good progress. I would hold out a little longer.

That's good to hear; I can definitely hold out longer. I've got the last update already DL'ed and I ordered a new iLok 2 (my previous iLok is apparently not supported), so I'm good to go. I'll probably wait until the equivalent of an "all-clear" here on the forum to install Melodyne 4 and just leave Melodyne 2 on the system.

I ran through a new tune and an older one that had V-Vocal on several clips, which was the first one where I discovered that this Melodyne issue existed.  I did not have any crashes today after the update to the new 4.1 version.  I DID get it to crash once when doing a removal of the Region Effect, but under normal uses, it did not give the issues as it did before and I was able to run without issue.  It's interesting that the notes for the upgrade said something like "improvements in the performance of some ARA implementations" or at least that's what I remember from reading the updates from my phone yesterday.  I'm sure that's not the exact wording, but I know that it wasn't anything like "Fixes Crashing issues in Sonar that make our product completely unusable". :)
 
Nothing from Cakewalk on the matter, either - which is a bummer.  Nonetheless, I'm glad to see it working right at this point so I can at least play with it!

ok...I have been having the same crash issue with Mel... I would create a reg efft and after a year of work, it decided to crash one day and have never been able to access any project that i did a reg effect on with Mel. I just did the new update for X3 studio and I can now access the projects. Install the patch for SX3

So after all of this I was also still having problems in some projects similar to the post above. Some would crash after opening, some would just hang after opening. After fighting with this stuff for waaaay too long, I figured out what was going on and have some suggestions for anyone else who is still having problems or considering upgrading to Melodyne 4. (This post here is one of the problems I was having before I realized it was due to Melodyne 4: http://forum.cakewalk.com/Project-becomes-unresponsive-shortly-after-opening-m3537360.aspx)

Problems included:
1.) Project would crash on start up
2.) Project would hang indefinitely on start up
3.) Unbounced melodyne V3 data would be lost after upgrading to V4.
 
I resolved all of these problems by reverting back to the old version of Melodyne and bouncing all Melodyne clips. Since the upgrade to V4 requires you to save the project with inability to go back to earlier versions of Melodyne, I had to pull a few projects from backup after they were saved as V4. ALWAYS BACK UP YOUR PROJECTS.
 
Basically don't upgrade to Melodyne 4 until you have gone back to all projects you care to ever go back to and bounce ALL Melodyne clips. Aside from making sure you have no Melodyne v3/v2 data in the project, this ensures no Melodyne editor windows are saved open in the project, which can also cause projects to become unopenable.
 
When bouncing make sure you have solo and DIM off so the clips aren't bounced as muted. (DIM must be off even if mute is off- seems like a bug? this has been happening since switching to Platinum off of X3.). Just make sure to verify each bounced clip has sound after bouncing. IF you bounce and the clip sound is still cleared even though mute and DIM are both off, try moving the clip to a different take lane. This resolved a handful of cases where the clips simply wouldn't bounce correctly. You may notice when bouncing that some times the clip disappears. It did not actually disappear, the clip just jumped to a different take lane - possibly behind another clip (not confusing at all). About 50% of the time when this happens Sonar crashes. Restart and move the clip to a different take lane and try bouncing again. Also try moving any overlapping clips on different take lanes to a different take lane. Oh and don't try to undo the bouncing of a Melodyne clip that jumped take lanes, this is pretty much guaranteed to lock up Sonar without a crash.  If this still doesn't work freeze the track and re-import the frozen audio file to replace the whole track.
 
Unrelated to above, there is a minor annoyance that Celemony has yet to fix: Previously the plugin would store time-grid settings per project/clip.  It resets them now each time the project is closed.  I notified Celemony about this a few months ago during our 50+ email exchange.
 
Good luck to everyone who is having problems.

I wonder how many of you having problems are using a different sample rate, or possibly a something different than 44.1 kHz ?
Possibly Melodyne is having problems interrupting the different/higher quality audio, like 48, 96, exc.
Which in theory it shouldn't but I wonder if that's what might also cause some problems.
 
I run almost exclusively, always 24 bit / 44.1 kHz and haven't had a crash with any region FX in over a year and I use each one (Drum replacer, Vocal synch and Melodyne on every single project.)

I wonder how many of you having problems are using a different sample rate, or possibly a something different than 44.1 kHz ?
 
Chuckebaby, I use also 24-bit 44.1 kHz, but nonetheless I had a lot of crashes with Melodyne the last time (about a dozen automatic crash reports are sent to the development). So I began to save frequently in between and I found out that if I do switch a little slower from Melodyne to Sonar (e.g. play button), then there are almost no crashes anymore. I think it could have something to do with the audio driver in my case, because most of the time it was during playing or when I started playing.

I must be lucky...  Melodyne 4 has been working fairly well here.  Granted, I do bounce the clips when I'm done editing, but just for kicks I did leave 3-4 instances "live" thru multiple sessions but still didn't have any crashes.    There must something in common between those having this issue vs. those that are not...