• SONAR
  • Huge track file sizes 30GB plus
2017/11/17 21:47:59
broh
After saving a tune, I noticed that most of my hard drive was eaten up. Turns out a single track in a song was written out to 30+ G. After a few saves, the drive was loaded. 
 
The track was a comp, the empty takes and such removes. Normalization was the only process run.
 
The rest of the tracks, even with more extensive recording are all under a Gig... 
 
Anything would be helpful, or if I missed it in the threads somewhere please point the way. Using Platinum, the latest.
 
Thanks,
2017/11/17 21:57:14
scook
Wav files sizes are a function of the "running time" x "bit depth" x "sample rate" x "number of channels." It does not matter if the file is completely silent, normalized or anything in between, the size will be the same based on the four variables. Here is a  file size table from the help.
2017/11/17 22:06:52
Cactus Music
You might have neglected to hit stop after recording and Sonar kept on going. Check the end of the track and make sure it ends with the song. 
Your not using 192 Hz are you?  As Steve said if you use a higher sample or bit depth the file will grow. 
2017/11/17 22:59:25
broh
Precisely! All the things you guys mention make sense: more data for ya
88.2khz - single track
under a 6 minute track - total
Only 8 tacks in the song total at this stage but a lot of comping.
all other tracks in the audio file are what I would call "normal" sized, - then  one big audio file 39.9 Gig for the lead guitar flattened, then normal sized files again. 
 
I mentioned normalized because other than flatten the comp, thats all I did...
 
I have an earlier copy, redid the comp and it cleaned up - back to normal.
 
So I moved the file to another disk now it's out of use. This was recoded in sequence with all the other stuff. I dont screw with bit bates mid song. In the end the 1st flatten and comp resulted in a 39.9 GB file of 5:25 second. The redone comp - and other than reloading Platinum and the song I have made no changes, is 110MB.
 
I'm rollin again, but that was interesting
 
2017/11/18 05:12:32
Anderton
Did a lot of comps, eh?
2017/11/18 11:14:29
THambrecht
That makes no problems. We have projects with up to 400 GB (50 hours recorded). And this is no problem for SONAR. Sometimes I forgot to stop a recording and it records 20 hours. So I get also single files with 30GB.
 
To clean up - apply trimming to all clips - then run for exampel an equalizer-plugin over all clips. The equalizer must be disabled (in the effect bin), so it renders actually nothing. But this forces SONAR to make each clip to a single file. After cleaning the audiofolder, the total size is lower.
 
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account