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
 

No kidding. give it a thrashing.
 

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...

I'd like to point out a potential workaround that I think is mentioned much earlier in this thread. It works 100% for me in my current project--meaning no crashes, but keep reading! To create a Melodyne region, create a new, vanilla audio track. Then copy your clip to the new track and make a region there. Now close the editor, move the clip back to the source track and reopen the editor. (I'm not sure if the close/reopen dance is strictly necessary, but I've always done it that way.) I can open and manipulate the Melodyne editor from here on with no problem. By contrast, Sonar crashes 100% of the time if I create the region on the existing track.
 
This workaround prevents crashes for me, but I have other problems. Sometimes creating the region inexplicably reduces gain by about 6dB. Other times a clip gain envelope is wiped out and clearly not applied to the resulting region; on these occasions, removing the region does not restore the clip gain envelope.
 
This behavior indicates that a track can be "poisoned" somehow. I get crashes on new projects created from a fairly bus- and effects-heavy template I use. But I get no crashes from a new project with a plain, default template. I've provided my template to Cakewalk and Celemony.

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.

Very encouraging.
 
But automap sound to me like the tempo mapper that I love so.

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.
 
 

I didn't have time to read all the responses, but I have no trouble with Melo, I think the key is
a) don't try to do the entire track at once. go phrase by phrase AS NEEDED - really you should only be fixing a few notes here and there (unless you are going for an effect like octave down)
b)render the effect immediately with bounce to clips. If you're worried about commitment then clone the track first. Having an active Melo running kills performance.
 
Just my 2 cents

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
 

I haven't read this whole thread - but for me melodyne crashes when I use my normal fx on a guitar part. This is S-gear, torpedo wos and slate vcc. If I use melodyne on a tea know with these fx - it will crash every time. (I can not be bothered to find out exactly which 1, 2 or all 3 cause the crash).
If I disable the fx bin - it works fine, every time.

So if I want to use melodyne, I use it without fx - then bounce the clip, and turn the V x back on.

It's a PIA, but it works...

So is it certain fx on the track that cause the problem?