Batch Audio Clip Bouncing in Cubase

Batch Audio Clip Bouncing in Cubase

Why Batch Bouncing

This is a handy technique I discovered out of necessity when dealing with a potentially laborious situation in a recent project.

A while back I was commissioned to do a mastering job. The client however could only supply me with a single wave file containing all 30 tracks. I wasn’t in the mood to bounce each clip individually after slicing and thought it worth while to find a simpler approach with future projects in mind.

Cubase is more than capable in dealing with sliced audio, clips and audio events, but there are pitfalls I wanted to avoid. When processing audio events referring to a single wave file, your options for dealing with shared events can lead to problems.

If for instance, you want to normalize a shared event, you will be given the option of applying the process directly to the wave file, or creating a new version with your process applied. This still leaves you having to repeat the same process 30 times over. In this particular case I’m also not a fan of processing the wave file directly via audio events. On the off chance that your project file becomes corrupt, or saving was unsuccessful, you are left having to do some pretty fidgety editing to determine where different processes were applied to split events as they were.

Should you try to apply an audio process to all shared events at once, your options change to “skip doubles” and “new version”. With “skip doubles”, only the first selected event is processed. “New version” might seem like an option, but there is a downside. Initially the new version still refers to the original wave file, but once you decide to commit to your processes by freezing the edits, it makes a full duplicate of the original file with processing only applied to the event region.

30 x 700 Mb is not a cost effective use of hard drive space for normalizing and DC offset correction.

How it’s Done

1. Select all shared events you want to bounce individually.
2. On the audio menu, click Advanced => Event or Range as Region.

3. You will be presented with a small dialogue box where you can make changes to region names and decide where the region count will start.

4. Open the audio pool and locate your file. Alternatively select one of the events and click Audio => Find Selected in Pool.

5. Click the “+” next to your audio clip to show the newly created regions. Select all the regions, do a right click in the pool and select Audio => Bounce Selection.

Regions

End Result

 

6. Next you’ll see a file dialogue to select a directory where you want the clips saved. It defaults to the project folder, so you have to specifically select the audio folder if you so choose. On clicking “OK” the clips will start saving and you’re done.

Other Uses

  • Trimming for Sampler: Even though plugins like Halion and Groove Agent have functions for slicing and trimming when saving or exporting programs, I sometimes prefer trimmed samples before going into patch building. Especially when slicing drum beats, you can end up with very short samples. Having the full audio file overhang outside the sample regions affects zoom performance and region marker drag accuracy.
  • Stripping Silence: When dealing with recordings containing large silent spaces, or using the “Detect Silence” function, this can also be a way to make the resulting clips more manageable. This, again, saves disk space and affords bulk processing of the resulting clips without fuss.
  • Isolate VariAudio: When treating a vocal or soloist recording, you sometimes only want to apply VariAudio to specific parts. When applying VariAudio to an audio event, analysis occurs throughout the whole file. I don’t like any more processing done than needed in a project so this comes in handy.

What it Doesn’t Do

This process does not apply any event based fades, envelopes or non-destructive volume/gain changes to the resulting clip.

I hope this will be of benefit to some. It has saved me valuable time by reducing repetitive tasks down to a few click.

Leave a Reply