Twice now, I've performed some pitch correction using Melodyne Essential as a region FX.  However, both times, when I save, close, then open the song later, all my Melodyne edits are gone.  How do you save your Melodyne edits so they are there the next time you open the song file?

patmc007
Twice now, I've performed some pitch correction using Melodyne Essential as a region FX.  However, both times, when I save, close, then open the song later, all my Melodyne edits are gone.  How do you save your Melodyne edits so they are there the next time you open the song file?

If you're happy with the edits you've done, bounce that Melodyned region to clip.  Your audio is now forever fixed, no need to keep Melodyne open for next time you open the project - It'll be disengaged once you bounce to clip.
 
Randy B.

It should save just fine regardless, I almost never bounce to clip.
EDIT: in other words, it seems something is wrong, though I don't know what exactly. Bouncing to clip may be a good work-around to save you some headache.

Bouncing the clip will help save precious resources, I like that idea.  But I would like to know why my Melodyne edits aren't saving.  Any other thoughts?

Reminds me of ReValver, which doesn't save preset display. It saves the settings, but next time you open it, you don't know what preset you're using.
I can't resist saying that IMO it's good practice to delete Melodyne as soon as you've done the edits. I never close a project with Melodyne active. I've "almost" lost projects by not doing that. I've used the Plugin version, though, but according to what I've read here the newer versions can be sensitive, too. I've had Editor for a year, but haven't installed it yet.

patmc007
Bouncing the clip will help save precious resources, I like that idea.  But I would like to know why my Melodyne edits aren't saving.  Any other thoughts?

That is a problem, and obviously shouldn't happen - it's a drag.  Hopefully Cake will straighten out what's happening. 
 
Meanwhile, as I just now posted on another thread (that one about V-Vocal), I don't consider bouncing a pitch corrected bit of audio to a clip to be a "work around" - I want my archived projects to have everything in place, with any off pitch bits permanently corrected.  Why would I want to archive out of whack audio that could have been fixed?  I don't save bits of audio that peaked out - those are re-recorded, so for me, it doesn't make sense to save out of tune bits either.  Bounce to clip takes a second, you're not relying on a plugin running in order for the audio to sound right - That all only seems logical to me.
 
Randy

Confirm you have updated to the latest version of Melodyne and you are running X3E.

Considering performing a VST reset (a reset followed by rescan in preferences).
http://www.cakewalk.com/S...ommended-for-Upgraders

Confirm if the behaviour happens with brand new projects.

Thanks.

rbowser
I don't consider bouncing a pitch corrected bit of audio to a clip to be a "work around" - I want my archived projects to have everything in place, with any off pitch bits permanently corrected.  Why would I want to archive out of whack audio that could have been fixed? 

Agreed 100%. Also if you're going to do a "universal" backup by exporting the project as WAV files, you'll end up exporting the un-fixed WAV if you haven't bounced to clip first.
 
Once it's fixed, it's fixed. You can always work on a copy and hide the original if you think you might want to redo the settings someday.

I don't like working destructively on my audio unless resource management makes it necessary. It usually doesn't. That's all.

Thanks for all the input.  Good to see both sides of the subject.  Each has good points.  I'm still waiting on Cakewalk Tech Support for a response.  I'll post once I get it.