To be honest this thread is making it seem as if these issues are universal and Melodyne is completely unusable with Sonar. I feel really bad for those users experiencing this but that is not the case for everyone. I use it a lot, as a region FX, and while I feel it's less stable than version 2, I get lots done with it and it doesn't really slow me down (quite the opposite I would say).

I hope Melodyne releases an update soon. I just wanted a little balance in the discussion.

Sheds

Sanderxpander
To be honest this thread is making it seem as if these issues are universal and Melodyne is completely unusable with Sonar. I feel really bad for those users experiencing this but that is not the case for everyone. I use it a lot, as a region FX, and while I feel it's less stable than version 2, I get lots done with it and it doesn't really slow me down (quite the opposite I would say).
SNIP

Thanks -- that's good to know.  Is there something you think you are doing different from others?

SanderExpanding I would expect.

stevec
Just to add another voice to the thread...   I also continue to experience no crashes at all using Melodyne Studio 4.04 in SONAR, exclusively as a Region FX.  I use the @#$% out of it and the only "weirdness" I've ever seen are infrequent odd blob behaviors (moving/stretching/etc), but even there it probably hasn't been more than 4-5 times out a hundred.   And like Sander I bounce my edits when complete, but the few times I did not (last time in SONAR .06) having 3-4 live instances didn't seem to be an issue.
 
Fingers crossed that those having these ongoing issues can get them resolved soon!
 

This is just crazy, I like so many have it $%^& up my project (s) so I don't use it except for that tempo mapping. I just use v-vocal.
 
Some have no problems, some a tsunami. No correlation with bitnes or OS.
I seemed to be ok if the clip I was regioning was devoid of spilts and edits otherwise look out.

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?

This might be related. Yesterday (really, early this morning), Melodyne Essential 4 requested that I authorize my installation. Yes, I know I did this previously, back in time immemorial, but it requested it again. This was when I inserted it as an FX. It was not quite a straight-forward process, but I accomplished the (re-)authorization after telling Firefox and Edge to accept the site with a safety exception.
 
I can't speak to its use causing crashes, however, at least not since about 3:30 AM this morning.
 

Another update - a positive one.
Think I might have found my issue.
Went to try it today and had the usual crash but I noticed something strange in the crash report - melodyne (automap).vst3 was the DLL that had crashed - automap!!! never heard of that so went and checked common files VST and , well there were TWO DLL's showing for Melodyne - the normal one and one called automap  - so I just deleted the automap one and all now seems to work perfectly.
I have an automap keyboard attached to my computer, a Novation Impulse but I have no idea where this Melodyne automap DLL came from 
So I will give it a good thrashing in the next few days, but this was strange to say the least.
Hopefully this was the "fault" but how it occurred I have no idea.
This may be of help to other people, I have no idea, or it could just be unique to my setup?
Nigel
 

Bajan Blue
well there were TWO DLL's showing for Melodyne - the normal one and one called automap  - so I just deleted the automap one and all now seems to work perfectly.

Alas, I checked C:\Program Files (x86)\Common Files and C:\Program Files\Common Files, and I do not have that file. No universal answer yet...

Bajan Blue
so I just deleted the automap one and all now seems to work perfectly.

Automap is what creates the earths gravitational pull.
dude, you just threw the earth off kilt. I felt that.

So - whether a "Cakewalk should be nagging Melodyne more about this" issue, or "Melodyne should get on with fixing this" it has been a full four months at this point without even a completely strong feeling that Melodyne is even accepting that there is a problem, let alone working on a fix for said problem.
 
 

Hi Guys
Final update - after a severe thrashing, I am happy to report Melodyne operating at 100% - so it was the "stray" automap Dll
Hope this is of some help
Nigel
 

Random data point. I'm running Melodyne Assistant 4.0.4.004 64-bit. I only ever use it as a Region FX from within Sonar Platinum -- never as an FX or the standalone. I do not have the 'automap' DLL, whatever *that's* all about.
 
I can keep multiple regions 'live' simultaneously as long as their on separate tracks. Useful for working on my crappy attempts at harmony. I then have to render them all out. If I forget, and try to create a second Melodyne Region FX further on in a track that already has one, bam! instant crash, every time.
 
There also seems to be an upper limit on the length of a clip that is being turned into a Region FX, though I haven't worked out exactly where it is. If I try to do an entire vocal track (say 3 minutes) it crashes *sometimes*. Keeping the clips shorter (30 seconds or so) seems to reliably work, however.
 
Thankfully, and for what it's worth, there doesn't appear to be any length issues when using the "compute a tempo map from this audio file" that's in Assistant and higher editions. I've fed it 6 minute long mp3s and it hasn't chocked on any of them.
 
It would be super keen to get this actually fixed, though. It's not acceptable that there's this ticking time bomb waiting to go off if I foolishly try to have 2 Region FX clips on the same track. If I want all my vocal tracks to be 'live' regions, it should let me. If performance degrades, fine, I'll lower my expectations accordingly -- but an instant crash and core dump is inexcusable.
 
FWIW, if this were properly fixed (after 4 months), I'd be somewhat more inclined to the 'lifetime' upgrades deal. 

Bluegrasser 
I downgraded back to 2.0, and I don't get the crashes, but now note preview does not work.

Try enabling input echo if you haven't already.

I did some troubleshooting this evening.  I have 132 projects with 75% of them containing Melodyne 2.0 FX Regions.
 
I uninstalled Melodyne 4.0 using Control Panel->Programs and Features.
I uninstalled SPLAT and reinstalled both.
 
 
I created a new Project and tested Melodyne 4.0 on a new clip.  Works ok.
 
 
When I open a project with a Melodyne 2.0 Region I get the warning that there is no going back.  Sonar crashes.
I can reopen the project after the crash and audition does not work.  In the Melodyne 4.0 window in SPLAT I can see audio being sounded in the box beside the "Compare" Button.
 
 
I tried Input Echo on and it made no difference.
 
 
I have backups of the Melodyne 2 projects I opened in Melodyne 4, so I am going back to Melodyne 2 until this stuff gets worked out.

The only clean way I found to back out of Melodyne 4 is a System Restore (simplest as M4 disappears and M2 reappears).

There are files in an M4 directory that created issues and were resolved by deleting that folder and reinstalling M4, but I forget the details of what I had done there. These "extra files" wrought havok on SONAR due to conflicting registry entries. Ultimately I passed on M4, so cannot provide much insight beyond the above.

The "Rdas" refers to the Roland VS drivers.    Unfortunately I can't offer much more than since I don't have a Roland interface, but I've seen the DLLs in a few other threads.