noynekker
This issue has been reported to both Cakewalk and Celemony . . . status is "submitted to development"
CWBRN-62536

Well done.  I guess that means they are working on it.

I would also send in a dump file.
Cant say I have ever frozen a Melodyne clip myself. I used to use the freeze track option to free up resources when I had a less than stellar CPU but just out of curiosity, why freeze it anyway ?
 
Sorry to hear about your problems.

I've also recently been having crashing problems with Melodyne, similar symptoms as well.  Every time it happens and the fault reporter pops up I submit it so hopefully they have lots of data to go on.  I've found splitting clips into smaller sections helps.  Also I work around it by inserting melodyne into the clip as an effect, as opposed to using regionFx.  Seems to be more solid that way with almost no crashing.  Crashes almost every time if I try to use regionFx.  Hope they fix it soon.

chuckebaby
I would also send in a dump file.
Cant say I have ever frozen a Melodyne clip myself. I used to use the freeze track option to free up resources when I had a less than stellar CPU but just out of curiosity, why freeze it anyway ?
 
Sorry to hear about your problems.

For me freezing is kind of like insurance, if something happens (project corruption, system changes over time, new versions of plugins etc.) you always have the rendered audio track to fall back on, work is not lost. Freezing is also easier to manage than bouncing and creating multiple versions of all sorts of tracks, and also with Melodyne, when you unfreeze . . . it happens right away, no waiting . . . just start editing.

Hi,
 
I have the exact same issue you have.  I use melodyne the same way that you do.  I have also reported the problem to both Sonar and Melodyne.  If more of us report it there will be a higher chance of them correcting the issue. Being able to freeze and unfreeze at will makes it worth editing in Sonar.  Prior to 4.1 I used rewire so I could save my changes in Melodyne and then copy the rendered Melodyne tracks to track lanes in Sonar but this was very tedious.  I am hopeful for a speedy correction from Sonar as 4.1 as ARA dramatically improves my workflow.

chuckebaby
Melodyne has been very stable here. I haven't had a crash with Melodyne since last year and I use it on every project just about.
 
- I only use it as a Region FX.
- I DO bounce to clips after I make my edits (Render it) Because think about it...Why would I want to go back to the original clip ? If I am using region FX this means the original was not worth saving anyway. However if it ever got that bad, I have a back up just like everyone else in the Projects Audio folder. So bouncing to clips might be destructive, but the original is still there (unless of course you are using the "Clean audio folder tool" after saving your project).
 
- I don't over use Melodyne because I don't think that's what it was ever intended for. (but that's only my opinion).
I use it sparingly to fix guitar mistakes, Vocal errors and anything else that might need a quick fix.
if something is so bad  that I would find myself using Melodyne on more than 50% of the track, I'd rather Re-record it .
 
I also use Vocal synch and drum replacer. those 3 region FX are my best tools for house cleaning.
this is typically the first step I take in the mix down process.
 
My whole planning set up (though not really related to anyone's comment on this thread) is:
I never use Melodyne to be something I am not. So with this, I have been fortunate to have success with Melodyne.
What im trying to say is, I work in sections and render as I go. As I said earlier, if the clip is bad enough that I need to use Melodyne, then it wasn't worth saving to begin with. However like any good producer, I get ADHD and try to fix more than I should. but with being said, still been lucky and had no problems, no crashes.
 
To those who do have crashes, im sorry for your issues. Try rendering as you go though and see if that makes a difference.
Remember you still have a back up in your Projects Audio folder if you labeled your tracks correctly.

When you say you have a "backup," are you cloning your raw vocal track into a second track and then hiding the second "backup" track for safekeeping, in case you want to start from scratch?
 
Thanks.
 

I've got exactly the same problem as noynekker. I have just started trying out Melodyne on a couple of short phrases of vocal takes, to tighten things up. I don't have exactly a powerful computer so I like to freeze tracks when I can to lighten the CPU load, and then if I want to come back and edit then I can just unfreeze and away you go. However, as I discovered this morning, this doesn't work with Melodyne. If I freeze a track and then try to save, Sonar crashes. I've tried this on a number of projects and it happens without fail. 
I've submitted the error reports so hopefully there might be a fix in the works before long.

Here's the call stack on this easy to reproduce bug (just followed the steps above).  While it's possible it's a SONAR problem, the call stack makes me suspect it's more a Melodyne problem and thus the odds of it being fixed soon are very low.
 

msorrels
 
Here's the call stack on this easy to reproduce bug (just followed the steps above).  While it's possible it's a SONAR problem, the call stack makes me suspect it's more a Melodyne problem and thus the odds of it being fixed soon are very low.
 

while it may be a melodyne problem, it also may not be, in studio one if you do the same with it's 'track freeze' equivalent 'transform to rendered audio' there are no issues, i know less than nothing when it comes to programing and how this stuff works, but one could be forgiven for thinking if x plugin was inherently broken, had an issue, it would be in all hosts, perhaps not but . . . . one of the reasons i think studio ones ara and melodyne integration is superior, far less issues and quirks than you get with sonar when dealing with melodyne.

The Grim

msorrels
 
Here's the call stack on this easy to reproduce bug (just followed the steps above).  While it's possible it's a SONAR problem, the call stack makes me suspect it's more a Melodyne problem and thus the odds of it being fixed soon are very low.
 

while it may be a melodyne problem, it also may not be, in studio one if you do the same with it's 'track freeze' equivalent 'transform to rendered audio' there are no issues, i know less than nothing when it comes to programing and how this stuff works, but one could be forgiven for thinking if x plugin was inherently broken, had an issue, it would be in all hosts, perhaps not but . . . . one of the reasons i think studio ones ara and melodyne integration is superior, far less issues and quirks than you get with sonar when dealing with melodyne.

I don't have S1 but this sound more like Sonar's "Render Region Effects" than Freeze Track.