Bouncing to clips makes the file huge

Author
Post
Essentials Only Full Version
revnice1
Max Output Level: -69 dBFS
  • Total Posts : 1082
  • Joined: 2007/09/21 14:43:56
  • Status: offline
2011/05/15 13:10:42 (permalink)

Bouncing to clips makes the file huge

I had a 500k clip at the beginning of the song and I copied it to the end and Bounced to Clips.

The resulting wav was 72 meg! Can this be right?

These results suggest that you could drastically reduce the size of a file by trimming all the little bits and leaving them as little bits.

I thought Sonar knew how to combine the audio in such a way that silence didn't add size when clips were combined?

Thanks - rev
#1

5 Replies Related Threads
    Kalle Rantaaho
    Max Output Level: -5 dBFS
    • Total Posts : 7005
    • Joined: 2006/01/09 13:07:59
    • Location: Finland
    • Status: offline
    Re:Bouncing to clips makes the file huge 2011/05/15 13:36:53 (permalink)
    I do believe  if there's a two bar clip at the start of a 10 minute song and another in the end, and you bounce them to clips, you get a 10 minute audio track. Silence requires just as much data as audible stuff.

    SONAR PE 8.5.3, Asus P5B, 2,4 Ghz Dual Core, 4 Gb RAM, GF 7300, EMU 1820, Bluetube Pre  -  Kontakt4, Ozone, Addictive Drums, PSP Mixpack2, Melda Creative Pack, Melodyne Plugin etc.
    The benefit of being a middle aged amateur is the low number of years of frustration ahead of you.
    #2
    paulo
    Max Output Level: -13 dBFS
    • Total Posts : 6218
    • Joined: 2007/01/30 05:06:57
    • Status: offline
    Re:Bouncing to clips makes the file huge 2011/05/15 13:40:40 (permalink)
    Not sure if that's right or not, but I would assume that adding the silent passages is bound to have some effect on file size. Personally I always remove all silence anyway. I only ever link clips in that way to make it easier if I'm exporting the track wav to send to someone else to make them easy to line up. Don't really see the benefit of storing all the silence.

      Paulo @ soundclick
    #3
    revnice1
    Max Output Level: -69 dBFS
    • Total Posts : 1082
    • Joined: 2007/09/21 14:43:56
    • Status: offline
    Re:Bouncing to clips makes the file huge 2011/05/15 15:28:51 (permalink)
    My experiment says Kalle is right. Silence is data and adds size.

    I thought some kind of technical trick was used by Sonar to connect clips without that happening - apparently not.
    #4
    daveny5
    Max Output Level: 0 dBFS
    • Total Posts : 16934
    • Joined: 2003/11/06 09:54:36
    • Location: North Carolina
    • Status: offline
    Re:Bouncing to clips makes the file huge 2011/05/15 17:59:14 (permalink)
    How long is the piece? 72MB would be a 7minute song. 10MB/minute for a WAV file. 

    Dave
    Computer: Intel i7, ASROCK H170M, 16GB/5TB+, Windows 10 Pro 64-bit, Sonar Platinum, TASCAM US-16x08, Cakewalk UM-3G MIDI I/F
    Instruments: SL-880 Keyboard controller, Korg 05R/W, Korg N1R, KORG Wavestation EX
    Axes: Fender Stratocaster, Line6 Variax 300, Ovation Acoustic, Takamine Nylon Acoustic, Behringer GX212 amp, Shure SM-58 mic, Rode NT1 condenser mic.
    Outboard: Mackie 1402-VLZ mixer, TC Helicon VoiceLive 2, Digitech Vocalist WS EX, PODXTLive, various stompboxes and stuff. 
    Controllers: Korg nanoKONTROL, Wacom Bamboo Touchpad
    #5
    jm24
    Max Output Level: -54 dBFS
    • Total Posts : 2127
    • Joined: 2003/11/12 10:41:12
    • Status: offline
    Re:Bouncing to clips makes the file huge 2011/05/16 09:19:41 (permalink)
    And: bouncing to tracks/clips will create a file that uses the processing bit level.

    Mine is set to 32 bit, conseqently big files.
    #6
    Jump to:
    © 2024 APG vNext Commercial Version 5.1