I should let everyone know that as indicated in the Mini Dump sent to Cakewalk at their request revealed that at least in my case the crash is occurring inside melodyne 4.04 and not in cakewalk's code.
 
 

I have the same problem, which started immediately after upgrading to Melodyne 4 back in January I think.   I had no success dealing with Cakewalk support but found the Celemony folks very responsive.  I have been sending them mini dumps of the crashes since February and this morning they said that this is recognized as an issue and they are working with the Cakewalk techs to find a solution and they will be releasing an update to fix the problem. 
 
In the meantime I have been able to continue with the following workaround. 
 First of all save your work frequently.   After you create melodyne instances save the project containing these Melodyne instances with its own name.     Once you finished the edits in Melodyne, bounce the tracks, remove the Melodyne instances and save the project with a new name.
 
Certainly not ideal, but it has kept me out of the crash zone for most of last month.
 
Looking forward to the update!

Thanks for the update jeo49!

jeo49
I have the same problem, which started immediately after upgrading to Melodyne 4 back in January I think.   I had no success dealing with Cakewalk support but found the Celemony folks very responsive.  I have been sending them mini dumps of the crashes since February and this morning they said that this is recognized as an issue and they are working with the Cakewalk techs to find a solution and they will be releasing an update to fix the problemw. 

 
Did they offer any indication as to what the causal factor might be? I am surprised they said it is a recognised issue with Cakewalk as many are running Vs 4 without problems. I certainly sympathise with those that aren't though!

I have. like others here (loosely) found that bouncing split clips to tracks before creating regions enables those regions to be created without issue. I say loosely because it seems to be a bit of a moving target for me to pin down any sure fire work around(s).

bitman
I have. like others here (loosely) found that bouncing split clips to tracks before creating regions enables those regions to be created without issue. I say loosely because it seems to be a bit of a moving target for me to pin down any sure fire work around(s).

Yes - I did see in your earlier post that you found it was linked to split clips. I don't seem to have that issue with Melodyne Studio 4 64bit plugin on Win 64, but I see others have. It's a weird one. Always so frustrating when issues occur inconsistently. Here's hoping they come through with a fix for you soon.

bitman
I have. like others here (loosely) found that bouncing split clips to tracks before creating regions enables those regions to be created without issue. I say loosely because it seems to be a bit of a moving target for me to pin down any sure fire work around(s).

So, if I understand this correctly, you need to bounce a comped, (or edited) audio track to a single clip prior to using Melodyne 4?  Once you do a region FX, you end up with split clips again.  Will you need to bounce it all down again each time?
 
Melo 4.2 Studio has given me fits off and on but seems to have settled down since Newburyport, (although I haven't done that much Melo-ing as of late.
 
Also, am I reading this correctly?  Once you patch up to the newest 4.4 version you need to have an active internet connection to use Melodyne?  I don't like the sounds of that.
 
Thanks.

All I know is that I have a vocal track that has some spits and slip edits. If I try to create a region for melo4 anywhere on that strip, the world come crashing to an end. If I bounce this track so it is a single strip the crashes don't occur. I haven't tested beyond that finding as I don't want to risk project corruption from testing. Doing so has caused this project and only this project to no longer want to successfully load Rapture Session. - this is a whole nuther can of worms I don't want to open here. Suffice it to say I'm going to wait until it seems safe to use melodyne 4 before I do again. I'll just use vVocal for now as it's on my system.

Paul G
 
Also, am I reading this correctly?  Once you patch up to the newest 4.4 version you need to have an active internet connection to use Melodyne?  I don't like the sounds of that.
 
Thanks.

Where did you read this?
 
Thanks

NeoSoul

Paul G
 
Also, am I reading this correctly?  Once you patch up to the newest 4.4 version you need to have an active internet connection to use Melodyne?  I don't like the sounds of that.
 
Thanks.

Where did you read this?
 
Thanks

Hi Neo.
 
Here's what I found on a re-review of this thread.
 
Quote: mettelus #42
"The solution was they simply needed to reset my entry in their server. What made me most irate is that it is my understanding that an internet connection is required to use Melodyne 4 (sans ILok) anyway. I am always connected, only on one machine, yet their "phone home" feature doesn't check the client side's functionality - only that their server has your computer ID on file."
(emphasis added)

and this...

Quote: mettelus #48

"I asked about earlier versions and Celemony confirmed that the upgrade 1) requires relinquishing a previous version and 2) an internet connection (or iLok) is required. The only recourse you would have is to contact them directly."

and this...

Quote: jeff s #56

"I installed Melodyne 4.0.4 yesterday and was surprised to discover that it now requires internet connectivity which my DAW does not have.  I contacted Celemony and they said go on-line as no off-line registration option exists."

(...although Jeff appears to be talking about registration here.)
 
I do hope I'm misunderstanding this.  I may just send an email to Celemony myself.
 
Paul