I apologize if someone has already answered this with the same thing I'm going to say but there so many answers and I didn't want to read them all ( I wanna go make music LOL) I had this exact same problem and the fix was easy. Uninstall Melodyne 4 64bit and in install the 32bit version. Stable as a rock afterward. Hope this fixes it for you too.

Mack
I am a bit surprised that Cakewalk has not chimed in on this thread. There is obviously an issue. They could at least say that they are aware of the problem and are working on it.

I submitted a help ticket weeks ago to Cakewalk but never got an answer. This is surprising. Not like them to ignore an issue, especially if it's reported through a help ticket.

Having the same issue here with Melodyne Editor 4, SONAR Platinum.  Works fine as a plugin but crashes SONAR when used as a region F/X.

FittingRoomStudio
Having the same issue here with Melodyne Editor 4, SONAR Platinum.  Works fine as a plugin but crashes SONAR when used as a region F/X.

Are you using the 32-bit or 64-bit version.  See Anni's helpful reply earlier (post #80)

dlesaux
I submitted a help ticket weeks ago to Cakewalk but never got an answer. This is surprising. Not like them to ignore an issue, especially if it's reported through a help ticket.

I don't think they're ignoring your ticket. It's more likely they're very busy, like: extremely busy. A lot of issues have come up with subscriptions. I had assumed that my subscription would automatically end after 12 monthly payments, but it didn't and I'm assuming a lot of other people were thinking the same thing. It took almost a month for me to get a reply on a ticket I initiated, but it was finally solved over the last two days.
 
Hope this helps alleviate any frustrations or impatience you may be experiencing.

I have a sneaking suspicion is a tricky one involving at least two companies no matter how chummy. I know in my case the dumps i sent to support show the crash to be in the melodyne code. I am on 32bit Windows, so obviously I'm use 32 bit Melodyne. I can also say that from my perspective, as long as the track I'm trying to region fx is not split anywhere we're all good.
 
I'm back to melodyning without issue if I follow this "rule".
 
I save first for the time being as it's always an apprehensive feeling as the "Initializing Region" message displays and for so many days it was follow by the dreaded "Reset Button".
 
 

Slightly off topic but i just wanted to check , I am definitely using Melodyne 4 but in CCC it is listed as Melodyne 2. Is this the same for everyone  ?
 
I have even logged out and back into CCC and it still lists it as Melodyne 2 

rontarrant

dlesaux
I submitted a help ticket weeks ago to Cakewalk but never got an answer. This is surprising. Not like them to ignore an issue, especially if it's reported through a help ticket.

I don't think they're ignoring your ticket. It's more likely they're very busy, like: extremely busy. A lot of issues have come up with subscriptions. I had assumed that my subscription would automatically end after 12 monthly payments, but it didn't and I'm assuming a lot of other people were thinking the same thing. It took almost a month for me to get a reply on a ticket I initiated, but it was finally solved over the last two days.
 
Hope this helps alleviate any frustrations or impatience you may be experiencing.

No frustration here. Waiting patiently. I'm sure there will be a fix soon!

Once again, why the silence from Cakewalk? They owe it to their customers to respond in some way. I am a bit surprised and disappointed in their lack of initiative on this.

Started a different thread in the forums and was informed this thread was alive... I'm retiring my thread and will continue monitoring this one.
My issue (mirrors what many of you are experiencing):
Since upgrading to 2016.3 (Sonar Platinum) Melodyne (4.x editor) is only allowing one effects region per track... if I edit one section of, let's say a vocal track, and the try and create another region without bouncing the clip, sonar crashes and needs to be restarted .. I can create a region on another track ( but only one) . Also, the effects region seems to play both the new edited Melodyne region as well as the original untouched track... creating weird chorused/doubled vocal/phasing...
I did see someone else earlier in these posts also mentioned the phasing issue as well.
When I get back to my studio, I will see about uninstalling the 64 bit version in favor of the 32 bit and see what happens...
Nice to see I'm not alone here  :)