Helpful ReplySave As > Created a folder consuming more space

Author
gswitz
Max Output Level: -18.5 dBFS
  • Total Posts : 5694
  • Joined: 2007/06/16 07:17:14
  • Location: Richmond Virginia USA
  • Status: offline
2017/04/02 13:33:30 (permalink)

Save As > Created a folder consuming more space

As part of my back-up routine, 
1. open project to be backed up
2. click save as
3. change the folder name to have _arch at the end of it
4. check Copy all audio with project and create one file per clip.
5. click save.
 
In my experience, this has almost always given me a folder for my project with _arch in the folder name that includes everything I need to back-up. The folder has also never been bigger than the original.
 
Today, I took a folder that is 23.9 GB and did Save As and ended up with a folder that is 137 GB. The original has 87 items in the audio folder and the _arch version has 134.
 
It looks to me like the clips were not trimmed. So for example, in the _arch copy, sections split and normalized are the same size as the entire original track.
 
This caught me by surprise.
 
I'm on Sonar Platinum version 23.3.0 Build 51 x64.
 
Looking at help about it says valid through 12/24/2037. What's special about 2037? As I have a lifetime membership, is this maybe the date of my future death? Worried :-/
 
 

StudioCat > I use Windows 10 and Sonar Platinum. I have a touch screen.
I make some videos. This one shows how to do a physical loopback on the RME UCX to get many more equalizer nodes.
#1
jpetersen
Max Output Level: -61 dBFS
  • Total Posts : 1499
  • Joined: 2015/07/11 20:22:53
  • Status: offline
Re: Save As > Created a folder consuming more space 2017/04/02 15:25:51 (permalink)
I was surprised to find normalizing multiple files at once creates one huge file with all clips inside.
 
Normalizing single files is OK.
#2
jpetersen
Max Output Level: -61 dBFS
  • Total Posts : 1499
  • Joined: 2015/07/11 20:22:53
  • Status: offline
Re: Save As > Created a folder consuming more space 2017/04/02 15:38:47 (permalink)
I wonder if "Create on file per clip" might help?
#3
brundlefly
Max Output Level: 0 dBFS
  • Total Posts : 14250
  • Joined: 2007/09/14 14:57:59
  • Location: Manitou Spgs, Colorado
  • Status: offline
Re: Save As > Created a folder consuming more space 2017/04/02 16:01:04 (permalink) ☄ Helpfulby gswitz 2017/04/02 18:45:54
It sounds like you have several things going on:
 
Any time you destructively process just part of a clip, a new file is written for that section of the track to reference. The original file remains intact, and that section is just ignored. If you go to Associated Files in clip properties, you'll see the clip referencing more than one file, and nothing is done to consolidate files when you Save As unless they aren't referenced at all in the project, in which case they wont be copied to the new location.
 
Similarly, if you have un-bounced, non-destructive slip-edits that cause SONAR to ignore parts of files during playback, those non-destructive edits are preserved in the copy of the project and the files will not be any smaller.
 
But the above won't make a copy of the project bigger than the original project. I'm guessing where that's happening is that when you Split a clip, you end up with two slip-edited clips referencing the same file. If you then Save As to a new location with 'one file per clip' enabled, you're going to get a full-length copy of the file for each clip with slip-editing preserved in the clip properties. If you've done a lot of comping or other splitting, that's going to create a lot of redundant file content.
 
'One file per clip' is disabled by default, and should really only be used if all the edits have been applied destructively, and you have a need to handle clips as separate files (e.g. you're going to import individual parts into some other app).

SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
#4
Jump to:
© 2024 APG vNext Commercial Version 5.1