Anderton
If you apply changes to a clip that aren't permanent, all those changes are stored in RAM

Also, it may be of note, Melodyne also saves polyphonic process data to files under your username,
My Documents/Celemony/Separations folder, so the un-rendered/unbounced data is available when you re-open a project you saved with un-rendered Melodyne clips. However it saves data there regardless if rendered or not, and these files accumulate over time, I managed to recover over 10Gig of SSD space at one time by deleting these files, as I didn't have any projects with un-rendered Melodyne Region-FX data I needed to return to.
Cheers
 
(Dear John,
 the separation folder contains data that is needed by the polyphonic algorithms in Melodyne. But if Melodyne can not find this data if a project is loaded, it will create it automatically again. So in other words: you can delete the content of this folder, but it will be populated again after each loading of projects using the data stored in here.
 
Best regards 
Tom Bratka
Celemony Support)
  
 

JohnEgan
IMelodyne also saves polyphonic process data to files under your username,
My Documents/Celemony/Separations folder, so the un-rendered/unbounced data is available when you re-open a project you saved with un-rendered Melodyne clips. However it saves data there regardless if rendered or not, and these files accumulate over time, I managed to recover over 10Gig of SSD space at one time by deleting these files, as I didn't have any projects with un-rendered Melodyne Region-FX data I needed to return to.

Wow, I cant believe I have never noticed that before. I had almost 2 GB in that folder.
Good tip John. thanks.
 
Also good tip from Mr. Anderton on the RAM usage.

chuckebaby
 
Wow, I cant believe I have never noticed that before. I had almost 2 GB in that folder.
Good tip John. thanks.

I never knew that either!! What a great tip. Next time I'm at my music computer, this will probably free up a terabyte of disk space 

Yeh thanks, this was other note from Celemony, I think I had over 20gig, at one time, and did it again sometime later had 10 gig
 
Dear John,
 
if you work with bounces, you don’t need the files created by Melodyne in Sonar. I would recommend to do a backup of the project, that you can store on another hard drive by simply copying the complete project folder. After that you can copy the project folder and use the option “Clean Audio Folder…” in Sonar’s Utility menu.
After that the folder should just contain the bounced data and the rest of the files that are needed in the project.
 
Best regards 
Tom Bratka
Celemony Support

Unbounced Melodyne clips are also stored in the cwp file, which is where that folder gets recreated from. For many who see cwp files grow suddenly in size, this is one of a few reasons why.

Melodyne also let's you specify the location of the Separations folder in its preferences. You can either use that or a directory junction if it is threatening SSD capacity.

mettelus
Unbounced Melodyne clips are also stored in the cwp file, which is where that folder gets recreated from. For many who see cwp files grow suddenly in size, this is one of a few reasons why.

Melodyne also let's you specify the location of the Separations folder in its preferences. You can either use that or a directory junction if it is threatening SSD capacity.

Another great tip! Thanks.

WOW!
What a great thread this has turned into!
So many great tips!!! Thanks for the valuable Melodyne lesson, Mr. Anderton and everyone!
 
Okay, So is the FX Rack in the fader strips, the same as the FX Bin?
And you're saying if I leave clips "open" they take up PC resources? Meaning they haven't been "rendered" by Melodyne?
So... I have to run Melodyne on ALL the clips that have an effect in their corresponding FX Rack?
Is that correct? Just really trying to understand.
I've recorded about 6 or 7 songs so far and I'm just now learning about Melodyne! And ONLY because we did our first vocals!
Thanks again everyone!
 
 

here's the best way to create a Region FX / use Melodyne in Sonar
https://www.youtube.com/watch?v=FIzNTGrENIY
Video also shows how to render your edits.

I think I might be having trouble understanding the terminology used in this thread.
If I use Melodyne Studio applied to entire vocal track, I'll "Freeze" the track after fixing all the tuning and timing in Melodyne.
People are talking about "bouncing to track(s)" as a permanent thing, where you can't make any changes after the bounce.  But when I Freeze a track (any track, vocals or instruments) to cut down on CPU usage, I can always unfreeze the track to make any additional changes.  Then re-freeze it.

I'm guessing "Bounce to track" is different than "freezing", even though freezing is basically taking a MIDI track and bouncing it to an audio track, or in the case of Melodyne, freezing is just bouncing the existing vocal track to another file (basically a hidden audio track).

Does that make any sense?  There is a difference between the two processes.  But I'm wondering why nobody mentioned freezing a Melodyne track instead of bouncing to new track?   Freezing cuts down on CPU usage and is easily undoable.  Am I missing something?

Leee
I think I might be having trouble understanding the terminology used in this thread.
People are talking about "bouncing to track(s)" as a permanent thing,

Yes their may be some terminology confusion....
Its Bounce to clips, not Bounce to tracks (they are 2 totally different process) One takes 30 seconds, the other takes 0.3 seconds.

Leee
 
I can always unfreeze the track to make any additional changes.  Then re-freeze it.

What are the advantages of freezing a Melodyne clip VS. rendering it ?
I cant make those same changes within seconds instead of unfreezing the clip, refreezing the clip.