Stephen C. Shapiro

YouTube: Part 1 • YouTube: Part 2

Full Quality Video (MP4) 

Notes

Intro

Pro Tools LE comes standard with a single track version of Beat Detective, which is what I will be using for this video. A Multi-track version of Beat Detective comes standard with Pro Tools HD, and is also available for LE users as part of the Music Production Toolkit, which can be purchased for a couple hundred bucks. If you don’t want to spend the money and have comparable results with the standard software, here’s what you can do.

For this lesson, I have already mic’d up and tracked the drums on top of the backing tracks, and I’m ready to edit the drums.

In order to keep track of your progress, you should save multiple sessions. Since the session files themselves don’t take up much space, this is an easy way to keep track of your audio regions. After you have the takes you want to keep, save the session as [Your Session] Drums.ptf. This session will keep the drum takes completely unaltered.

Next, save another session as something like  [Your Session] Drum Edit.ptf. This is the session we will be working in to make all our Beat Detective edits.

Guide Track

Create a new audio track called Kick/Snare. Set the input of Kick/Snare to an unused bus and arm the track to record. Make sure the Input Only monitoring option is turned on. Set the output of or create a send on both your Kick and Snare track to that same bus. Play back some audio and try to set the gain of those tracks so that they are peaking at about the same level.

TIP: The Kick/Snare track will be used as a guide for Beat Detective. This will work for most of your projects, because Kick and Snare are normally the most prominent drums in keeping the rhythm of the song. But if, for instance, the toms are more prominent, you may want to bus the toms to this track, too.

Before we record to the guide track, it’s a good idea to trim the regions at some even point. Starting and ending at a whole measure is best. This just makes the regions easier to work with.

Record the guide track from beginning to end of track. Mute all the other drum tracks.

Correct The Guide Track

Go to Event > Beat Detective  [Apple 8 or Ctrl+8 on the PC]. Make sure the Kick/Snare guide track is selected, and go to the Region Separation portion of beat detective.

Click Capture Selection, then Analyze. 

As long as your don’t capture and analyze another selection, this guide track is stored in the memory of beat detective.

Expand the view of the Kick/Snare track, start to adjust the sensitivity. Set resolution to whatever you want beat detective to line up. Bars (measures) will just line up the beginning of eat measure, beats will line the track up to the meter of the song, in this case, 4/4, or sub-beats which would be 8th notes 16th notes, etc. 

For this track, I’ll use sub-beats, so most of the hits will be corrected. Next, set a trigger pad. This is the amount of time will be padded to the region before the corrected transient hit. If you leave this at 0, you might hear some clicks or pops on the track.  I usually have this at double the smoothing time. For instance, if I was planning on having a smoothing time of 5ms, then I would set the trigger pad to 10ms.

Click separate, and move on to region conform.

        Strength – how close do you want beat detective to slide hits to the corrected rhythm? Less strength will keep the feel of the drummer, and 100% strength will have perfect hits.

You can also use a groove template.

        Exclude within – this can exclude 

        Swing (if needed) – If the rhythm of your song is swung, experiment with swing strength on some type of MIDI track, then write down the swing percentage to use for the rest of the song when quantizing other parts.

After deciding on your settings, click conform. Now move on to Edit smoothing.

Fill Gaps will probably work fine, but I always like to fill gaps and crossfade. The default fade time is 5ms, which is half of my trigger pad length. Apply the smoothing.

With all the other drum tracks still muted, listen through the entire song. You can also eyeball it by comparing the Kick/Snare track to the separate Kick and Snare tracks. It will be pretty obvious when Beat Detective makes a wrong guess. You can either undo your Kick/Snare edits and start the Beat Detective process all over again and tweak the settings, or just be prepared to correct them manually.

All the settings you applied to the Kick/Snare track are stored in beat detective. Now you will apply those cuts to the individual tracks.

Select the Kick track and apply the separation. Using the P and Semicolon buttons you can select the other tracks. Apply the separations down onto all the tracks. 

Do the same with conform.

Then with smooth. The cross fades will work in the background, so don’t worry about interrupting beat detective. Check them in the Activity Monitor.

Unmute the drums, mute the Kick/Snare track and double check the track again. If there were any edits you need to do manually, do them now.

TIP: To correct skipped or misplaced hits: 

        Select the track names whole drum kit and create a new edit group (apple g)  Label it “drum edit”  When editing drums, eliminate crossfade on bad. After you are satisfied with all the drum edits, save the session. Then save it as “Drum Final.” This is were the corrected drums will be consolidated to single regions, which will make them much easier to work with.

Consolidate the tracks, by going to Edit > Consolidate Region (alt shift 3), or using the Gain Audiosuite plugin

Now you can import those tracks into your primary session, or just save this as the primary session.

That’s it. Now go on to compress, eq, augment, sound replace your drums. You’ve got the perfect take.