![]() |
Re: Freeze vs Commit
Quote:
|
Re: Freeze vs Commit
Hi,
For me the CPU hit is minimal; it's more about how to retain as much memory as possible. |
Re: Freeze vs Commit
Quote:
|
Re: Freeze vs Commit
I use Freeze as a strictly temporary thing and unfreeze when the session is ready to close. I can always re-freeze the next time, or I will COMMIT, and leave the original track inactive but showing if I think I will need to make changes. With Melodyne, I will select "Do Nothing" to the original track and move the .cm audio file back to the original track on a new Playlist and make Melodyne inactive(or remove it). You have many options, so find what suits you best;)
|
Re: Freeze vs Commit
Thanks Steve, for reminding me of the commit up to insert feature.
I'll have to read up since I'm just getting back into everything. |
Re: Freeze vs Commit
Quote:
Steve |
Re: Freeze vs Commit
Quote:
|
Re: Freeze vs Commit
When using Freeze or Commit what is the impact if I use any Automation on the track?
|
Re: Freeze vs Commit
Quote:
Automation will be visible on the frozen track as its just rendering the audio in place. Commit will print the automation onto the newly rendered file if you tick the boxes. Otherwise you can choose to not have the volume, pans, mutes etc. printed. Have you tried either? A dialog box will pop up when you go to commit and you can see all this stuff pretty clearly. Sent from my iPhone using Tapatalk |
Re: Freeze vs Commit
Thanks! I haven't tried either yet as I am in the middle of a project but I expect I'll try both out very soon.
|
All times are GMT -7. The time now is 01:48 PM. |
Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com