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.

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?

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.

That for sure. No I don't know what I could be doing differently. In the world of computers there are practically infinite variables. I'm on Win 10 64 at the moment but it worked the same under Win 7 64. I use lots of third party content and don't even dedicate my system purely to music, though I don't really game or anything (but I have and use Lightroom and Photoshop and it's also my general interne and administration machine). I have a whole bunch of peripherals that I use in various combinations.

In short, I think this is one of those things that is just worse on some systems than on others. I HAVE learned to bounce my edits when they're done. I forget to do this half the time but it does seem to help to have fewer Melodyne instances active at a time. And not specific to Melodyne: save often.

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!
 

Just to add to the pile here, I have found the following melodyne actions to cause reliable crashes, and I now now save before doing any of these. I've filed multiple bug reports, but don't bother any more because I can get it to crash 10x an hour when doing vocal comping:

• insert time/measures before a melodyne clip
• drag two or more melodyne clips in same track but different lanes
• drag melodyne clip to the empty space below tracks to create a new track
• create Melodyne RE when the take lane overlaps another Melodyne RE
• clone track
• cut and pate of any sort

Other weirdness:

• insert melodyne on two versions  of a clip, and have edits in one clip cause changes or loss of edits in the other clip. 

Any now, after doing the June update

• melodyne REs losing all editing info (back to default detection)
• REs showing up empty on project load
• display errors, edits not showing up, old edits ghosting over new ones. 
• a random "File not found" dialog box showing up in sonar all the time. 

Attached is a screenshot of my saved files for a current project that's only a few days old, contains one audio clip with one melodyne RE. This is the least complex project I have, and it has been a horrible experience working on it. I had to revert to previous versions multiple times, and make ultra-paranoid sub-versions just to keep things working. Half the saved versions here don't open. 

http://imgur.com/a/pUxQu

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.

I hate to be another to add to the frustration, but I too am running Melodyne in every single project.
no problems. I use it as region FX. as I do vocal synch and drum replacer.
I use those 3 region effects on every single project as I need them to fix things.
 
I don't insert Melodyne as an FX. sorry.
(oh I also bounce my edits as soon as im doing using it in Region FX.
 
Sorry to hear for you guys experiencing problems. I cant imagine what I would do without those tools.

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.
 

One other note FWIW...   I always use the Trim command on every clip before applying Melodyne as a Region FX.