When I am working with Melodyne, I usually work in phrase size clips, especially for vocals.  I do a lot of save as with incremental filenames so I can easily go back, although archiving a clone of the tracks is probably not a back idea.

I really just started digging into Melodyne Essential that came with SONAR and this thread and the tips in it have been a great help.  I was getting crashes, but by working a vocal verse by verse and chorus by chorus so to speak, I have all but eliminated the nasty crashes.  Still, should this really be happening at all though?

Since 2016.12 creating a Melodyne Region FX has caused Sonar to crash...sometimes. Also rendering a small Melodyne file within Sonar has caused Sonar to crash...sometimes. TBH someone said earlier Melodyne in Sonar has always been buggy, and I have to agree. I've used Sonar since 2007, Celemony since 2008, and they have both been pretty stable, until they get together.

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.

Helpful reply chuckebaby, although I use Melodyne exactly the same way you do. I was using it yesterday, and had no problems at all. It's almost like it needs to settle down after a Sonar update. Hopefully it'll be fine now, because I hate that nervous feeling I get just before I do something Sonar doesn't "like"; until very recently I'd not had that for at least a year.

 
Thanks for the replies everybody . . . though, let me remind everyone the original point of this thread was to point out that there is an existing issue when freezing Melodyne (new Studio version 4.1) Region FX, and then trying to save the project . . . other than that, my use of Melodyne 4.1 in Sonar Platinum has also been mostly stable.
 
Regardless of how minimally or extensively Melodyne is used in a project, the Region FX freeze feature is broken and needs to be fixed.

I don't think too much about workflow with Melodyne. I use it...there are two options: if the track sounds better, render. If it doesn't, either don't use Melodyne or re-do the track. If I can sing something once, I can sing something twice. I naturally use short phrases because like Chuck, I'll do the odd fix and there instead of wholesale correction on a track.
 
Once upon a time I thought it was important to preserve the original track because V-Vocal did what I thought was a clever move - keeping a muted copy the original track. So, I'd clone a track and work on that. After about a year of never returning to the original, I just said forget it.
 
Bear in mind part of this involves a personal recording philosophy, not technology. Record, fix if needed, move on. The muse is wonderful, but incredibly impatient. Get too hung up in stuff, and she goes to visit someone else who's more exciting. I also render virtual instruments to audio (although I save the instrument preset and archive the MIDI track) as well as destructive editing, like gain changes with vocal phrases. With comping, it's listen, choose, flatten, done. It's more fun that way, I get more done...and call me crazy, but I think it makes the music better.

So, are you suggesting that freezing Melodyne Region FX is a useless feature ?
Never need to go back and tweak a mistake, rethink at a another time ?
Just flatten, or bounce and move on ? . . . certainly not my workflow, more fun to be able to revisit a track and tweak until "perfection" is attained . . . isn't that why the freeze function was created ?

noynekker
I've been able to reproduce this crash bug consistently on a completely new Platinum project.
1) start new blank project
2) add audio track
3) drag any wav file from browser to the track
4) create a melodyne region fx
5) save the project
6) freeze the melodyne region fx clip (it renders to audio clip correctly)
7) save the project - - - > instant crash, every time

Seems to me you have a bona fide bug here that you should report to Cakewalk.  Who knows, it may be the key to unlocking the intermittent bugs other people get in Melodyne.  Bottom line, this should work without a crash and as a customer, you should expect it to be fixed.  But you gotta help the bakers out by reporting it along with your recipe so they can investigate.  Reporting it here on this forum is good, but not enough to get it fixed.
 
Have a look in the Problem Reports forum.  Noel has instructions on how to capture a crash dump.  If you were to submit your recipe along with a crash dump, I'm sure we'd be well on our way to having this bug fixed.
Good luck!

BRuys

noynekker
I've been able to reproduce this crash bug consistently on a completely new Platinum project.
1) start new blank project
2) add audio track
3) drag any wav file from browser to the track
4) create a melodyne region fx
5) save the project
6) freeze the melodyne region fx clip (it renders to audio clip correctly)
7) save the project - - - > instant crash, every time

Seems to me you have a bona fide bug here that you should report to Cakewalk.  Who knows, it may be the key to unlocking the intermittent bugs other people get in Melodyne.  Bottom line, this should work without a crash and as a customer, you should expect it to be fixed.  But you gotta help the bakers out by reporting it along with your recipe so they can investigate.  Reporting it here on this forum is good, but not enough to get it fixed.
 
Have a look in the Problem Reports forum.  Noel has instructions on how to capture a crash dump.  If you were to submit your recipe along with a crash dump, I'm sure we'd be well on our way to having this bug fixed.
Good luck!

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