Melodyne Essential 4 Crashing Sonar Platinum

Up until now Melodyne Essential 4 had been working fine but for some reason, Sonar crashes every time I try to create a region effect with it. I wonder if the latest Windows update has something to do with it. Anyone else having this problem?

Mine too. boom boom boom.
 
Sent 3, no 4 fault reports in. Hope it's fixed in the next drop.
Production on hold.

Just submitted CWBRN-46337

I'm also having this same crash.  Only thing that has crashed Sonar in the last couple years!
 
JIm

Well, for the first time ever, Melodyne crashed my Sonar Platinum yesterday also. After the crash I couldn't create another region fx until I closed down the pc and re-booted. Then all was fine again.
 
I'm not running Win 10, i'm still on 8.1 so I in my case it's not that. What I did when it crashed was delete a clip that I had created region fx on, but not rendered. Straight after that I went to create another region fx on another clip in the same track and Kapow, down she went! I'll try and reproduce it and report if I can. The fault logger worked but the studio pc isnt on the web, so it didnt send.

Could be those "purists" who hate autotune devices are hacking it.  I jest, of course.  I haven't gotten around to installing Melodyne 4 yet.  It's too new and I'm watching the boards to see how those (like you) who have braved it are making out with it.  I hope you find a successful solution.
 
John B.

Well my project which had a Melodyne crash yesterday refused to open today. For every attempt to open the project I got the Sonar error/minidump splash screen. I eventually opened it in safe mode (shift open) and kept all plugs except Melodyne and it worked!! Something weird going on for sure. 

I had the same issue after updating to Melodyne 4, an instance of Melodyne would not even load, just crashed Sonar. I had to increase the buffer settings, and this seemed to have solved (or maybe just mitigated, as I haven't done a great deal of testing yet) the issue.
 
Being a 32bit install, and the lack of being able to address more than 3GB or so of memory, I've always had trouble running more than a dozen or so bars through Melodyne at a time. So, as per Steve, I too must always bounce my edits each and every time I use Melodyne. I don't run more than 1 instance at a time either, and this helps keep the crashing to a minimum.
 
As an aside, I've always been able to run much larger sessions of Melodyne as a stand aloneprogram, as opposed to an ARA session inside Sonar. This is probably related to lack of memory too, as a large Sonar project can quickly eat into what is essentially only 2.5GB of system RAM after Windows loads. Sonar can easily take another 1GB, depending on project size, leaving precious little left for Melodyne. AD2 and AK also seem to take up their fair share of memory too and can quickly crash Sonar if I go over the limit.
 
Anyway, I'm rambling now. I just wanted to let the OP know to check their buffer settings, as this does seem to effect Melodyne, perticularly running as an ARA inside Sonar.

dlesaux
Up until now Melodyne Essential 4 had been working fine but for some reason, Sonar crashes every time I try to create a region effect with it. I wonder if the latest Windows update has something to do with it. Anyone else having this problem?

Not good,I had a terrible time upgrading from the base version from X3[I now have Platinum though] to Editor,I accidentally blew 2 authorizations,and cannot install the version that comes with Platinum,as the command center then wipes out my $149 USD upgraded Editor,and only the basic one shows,thus blowing another Editor licence.
 
I loved being able to turn audio to MIDI,and then have a whole array of synth instruments play,what I played on guitar,but I haven't had any luck doing anything else,It really does seem true,that as you age new concepts are more difficult to grasp,but lately I'm getting "white out's" for many scenarios,also I cannot tolerate Windows 10,and that opinion comes from a fair amount of experience while attempting to use it on my very recently deceased Mothers Dell Inspiron,so if future versions of Platinum lock out Windows 7 Professional,I'll go back to X3,but I heard a horrible thing the other day: Waves are no longer supporting/working on X1?,this is bad if quickly progresses to X2,then X3,then Platinum-I spent a silly amount of money with Waves,their sales and marketing,made me believe I saved thousands,when all I really did was spend thousands.
 
I apologize if my rant is a bit all over the place,but I wouldn't upgrade to Windows 10 if I was being paid to!
All the best
Bob

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

Thanks guys!

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

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.     

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.