Sonar X3 Studio and Melodyne

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.

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?

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

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.

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.

Are you using a registered version of Melodyne or are you using it in 30 day trial period ? I only ask because the trial version requires www connection each time you use it. Just trying to think of why your edits are going awol, not had that probem at all here.
 
As for the keep original debate, I tend to copy the track first, mute/hide the original and work on the copy. I hear what people are saying re keeping stuff that is "wrong", but I prefer not to leave loads of open clips, yet sometimes need to edit the edits which in some cases seems to work better starting over than trying to re-edit an edit. Once I'm totally happy with the project, it's easy enough to delete the audio tracks that are no longer required and a 'save as'  tidies up the audio folder at the end.
 
 
 
 

Sanderxpander

Any advertised function should work, period. The rest is work-arounds and goodwill from the user.
Regardless, if a function is advertised as working, I don't see why it should get special status just because it i

Should, yes. And expecting all advertised functions to work in every project and every set up is 100% unrealistic, not to mention relying on it.
If a simple thing like fast bounce can put a respected, pro quality VST to its knees, it's obvious that extremely complicated and deep VSTs can mess up whole projects if you don't treat them like opera divas. 
I'm sometimes amazed reading of guys doing complicated edits on the fly when project is playing back, and then getting annoyed when the whole program stalls.  If a program promises you the Moon, many start using it as if Mars was mentioned.
 

Sanderxpander...Any advertised function should work, period...
...I disagree...etc.

Hi, Sanderxpander - I do sympathize with what you're saying about expecting something to work as advertised.  I just wanted to explain that I'm not getting crashes due to pitch shifting, because I work in a way that makes fewer demands on my computer.  I want to get on with the work!--not deal with crashes I can easily avoid.  

I don't feel I'm giving Melodyne "special leniency."  What seems illogical to me is to Not bounce.  Permanently fixing something which wasn't intended in a track, a clam note, isn't a "work around - IMHO - Bouncing to clip to fix the clam is the only method that makes sense to me.  I want to be sure there isn't any DC Offset in a track too, but I wouldn't want to run some plugin that temporarily fixes it on the fly - I want to run the DC Offset filter and permanently fix that track.

Kalle Rantaaho...If a program promises you the Moon, many start using it as if Mars was mentioned.

That cracked me up - Very clever statement of something that's very true.

I hadn't looked at Celemony's online tips and tricks kind of pages about Melodyne.  Now that I have, I see they advise bouncing to clips to save Ram.  Saving Ram is always a good idea to avoid the "I expected Mars" syndrome.  

On their site, they're also still saying you should temporarily set your buffer to a much larger size than usual, 1024 samples - and then re-set again when through with Melodyne.  When engaging Melodyne, I think we all used to see that pop-up with the "your buffer is too small" message.  Melodyne still works with a more normal, smaller buffer, - but the warning is still there, ready to be referred to if we start experiencing problems when trying to run it the way we run real time effects.

All of that is IMHO - You can have a different opinion, but you can't say my method of working, based on my analysis of the situation, is "wrong."  It's hard to argue with the efficiency of how I work, but obviously there are other ways of working, including ways that can apparently cause crashes.

I don't disagree with you, Sanderxpander, and I don't think how you're working is "wrong."  I'm just letting you know what my attitude is towards the whole pitch shift question.  When it comes to fixing pitches here and there, the process is pretty stress free for me!

Randy

 
When an application edits, this action is being held in a temp file-cache file etc. When you close Sonar that 'file' is not being kept or the pointer to it is being dissolved.
As mentioned; you increase the size of that file "buffer". Also are you running as 'Administrator'