Bouncing To Memory Overload!!!

  • Thread starter Thread starter Dr. Varney
  • Start date Start date
Dr. Varney

Dr. Varney

Pimp
I wasn't sure where to put this because my question is about 'bouncing' tracks in a DAW. About how to do it properly and looking for tips on keeping the load down. Though in essence, it's probably more of a computer issue.

First up, just to be sure... 'bouncing' is when you take a pattern made with a VSTi and discard all the note data in exchange for a WAV recording... right?

That's what I've done, anyway. I did it to save on CPU power... but all it's done is slowed my computer down about ten times slower!

Figuring that it might be the long silences in the WAVs that was adding to the load, I edited the silence out of each one. This certainly runs faster but despite placing markers in my playlist to help with cueing, it's hell trying to line up the WAVs to sound as the project did, before the bounce.

I'm in a bit of a mess. Any quick solutions to this?

Okay - I need a dual core system (probably) with a gig more RAM, perhaps. I have the motherboard waiting for a dual core processor but the rebuild will have to wait until after Xmas.

In the meantime - does anyone have any suggestions? Specifically, do you edit the silence out or leave them whole? Do you bounce tracks together; or in groups? Or do you bounce each track to end up with the same number of tracks as when you started? If so, is there any point?

Basically, on a typical song - what is your proceedure?

Dr. V
 
Dr. Varney said:
I wasn't sure where to put this because my question is about 'bouncing' tracks in a DAW. About how to do it properly and looking for tips on keeping the load down. Though in essence, it's probably more of a computer issue.

First up, just to be sure... 'bouncing' is when you take a pattern made with a VSTi and discard all the note data in exchange for a WAV recording... right?
Click to expand...
For me, bouncing is when you combine tracks onto a single or stereo track. For example, say you've recorded 8 tracks of drums and you want to combine that lot down to just two tracks ~ the way you do that is through bouncing. Or, say you have recorded a solo in sections but across 4 different tracks and you want one complete unbroken track for your solo. You bounce the 4 down to one open {that is, unused} track. Bouncing is a staple of analog reel to reels and cassette based portastudios, where you are limited in the number of tracks you have, often 4 or 8. On some DAWs this is the case too, especially the 8~12 track standalones, sometimes, even the cats on 16 tracks will bounce. In the 60s it was known as "reduction mixing" and "ping~ponging". On analog, the sound quality reduces after each generation of bouncing. One of digital's initial selling points was that no quality is lost in the process, the theory being you can bounce down ad infinitum. But aside from the fact that many computer DAWs have a huge number of tracks which moreorless eliminates or at the very least, reduces, the need to bounce, I'm not certain that it's even true.
 
more importantly, what software are u using? If you bounce something, you need to get rid of the orginal track otherwise you will have 2 copies of the same thing. If there is a freeze function in your daw, you should use that..
 
You must log in or register to reply here.
Back
Top