Just thought Id note this issue is not resolved, other than having to abandon specific project file and redo a lot of stuff, but found the following in Windows log specifically refers to Melodyne, also I've sent dmp file to Melodyne people, and  they are looking into it, will let know if I hear back.
(Seems lately I'm spending more time on issues than on producing my music.)
Description
Faulting Application Path:              C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
 
Problem signature
Problem Event Name:                      APPCRASH
Application Name:                           SONARPLT.exe
Application Version:                         21.12.0.36
Application Timestamp:                   56aa51ca
Fault Module Name:                        MelodyneCore-4.0.2.001.dll
Fault Module Version:                      4.0.2.1
Fault Module Timestamp:                569a3aaf
Exception Code:                                c0000005
Exception Offset:                              0000000000fb12d6
OS Version:                                        6.1.7601.2.1.0.256.48
Locale ID:                                           4105
Additional Information 1:                052b
Additional Information 2:                052b092f631f928fc5885cef24500e94
Additional Information 3:                da33
Additional Information 4:                da33b0aa792f0e63c7a2bbb7321d21f4
 
  Cheers

I've got the same problem, but have developed a work around that usually gets me by.
 
What I noticed is that when the problem starts occuring (can't seem to identify a pattern....), it usually is when I am trying to create a melodine region within a section of a track - as against a new track and just doing it all. At any rate, my work around is this: create a new, blank track.  Copy and paste the section of a track (or clip) I want to use melodyne on into the new track. Then melodyne it there.  This seems to work every time.
 
It's a pain in the as%, and I am hoping something as fundamental as melodyne "explosions" gets resolved so creating extra tracks and extra work is not needed.
 
(Note: full disclosure, I am using Melodyne editor, but the issue 100% matches yours).
 

Thanks guys!

I have not had a crash with Splat Newburyport using Melodyne Studio 4, but every time I do a region FX with Melodyne 4 it stops my audio engine.  I reset my audio engine and everything is working properly after I reset the audio engine.

rickidoo
I've got the same problem, but have developed a work around that usually gets me by.
 
What I noticed is that when the problem starts occuring (can't seem to identify a pattern....), it usually is when I am trying to create a melodine region within a section of a track - as against a new track and just doing it all. At any rate, my work around is this: create a new, blank track.  Copy and paste the section of a track (or clip) I want to use melodyne on into the new track. Then melodyne it there.  This seems to work every time.
 
It's a pain in the as%, and I am hoping something as fundamental as melodyne "explosions" gets resolved so creating extra tracks and extra work is not needed.
 
(Note: full disclosure, I am using Melodyne editor, but the issue 100% matches yours).
 

Interesting, that's exactly how I work with melodyne (or any other Region FX), but I've never felt I'm doing extra work. I just like to keep a copy of the original unedited track / clip, for comparison or... just in case. 
 
 
Best,
Klaus

Klaus
Interesting, that's exactly how I work with melodyne (or any other Region FX), but I've never felt I'm doing extra work. I just like to keep a copy of the original unedited track / clip, for comparison or... just in case. 
 
Best,
Klaus

>>>> You can easily do this without a copy by selecting "by-pass region"... that lets the original wave file play...

Thanks, it does seem somewhat random, while I appreciate knowing a work around in desperation, I guess I have issues with spending time on determining, and using work arounds rather than things working as they're supposed, and prefer spending my time producing music. However, when editing single tracks within Sonar I would usually clone the whole track and then work in the clone using region fx where required and keep what I need. I don't seem to have the any issues with Melodyne 4 crashing Sonar used in this way, and still using actively.  In my case consistently, an analog bass track, I did melodic algorithm, saved midi file, when I import that midi file into a soft synth instrument, is when all hell breaks loose (so to speak :) the issues start with transport, continuous unstoppable playback, and audio engine goes down,  and cant be re-enabled audio. Oddly though while continuously playing with no audio I can actually delete synth track midi content or entire track(s) to no avail, or other menu functions, as it continues playing merrily along, worse thing is even though I deleted these tracks entirely, the project file I imported the midi file to now seems permanently corrupted with this behaviour when reopened, even after being saved with offending midi and synth track deleted, I guess my current work around is not to use Melodyne 4 generated midi files, until I have time to sleuth or hear its been resolved. I've since rewritten a new midi file manually, and using in a previous project version not affected.     

Just for further failure mode clarification for those who might be reading of import:
 
Mine, upon create Melodyne 4 region effect Sonar says in the control bar, "creating region effect" (I think) , "mixing down audio", "reset button" .
 
 
You all?
 

I finally got Melodyne Studio 4 to crash on me.
I had created a region effect for two measures of a guitar solo to tune 1 note a few days ago.
Today, I tried to create a region fx for the whole 16 bar solo and Melodyne caused Sonar to crash.
Restarted Sonar, rendered the two measures that I had created a region fx for a few days ago and then created a region fx for the whole 16 bars.
No crash.

My help ticket has not been reviewed yet. Hopefully the bakers will get to this soon and we can get some idea what's causing these crashes. Thank you all for your feedback. Evidently I'm not alone!