Pro Tools: Audio Editing

If I had to name the single biggest reason I have been successful in this business, it would be editing. Most new clients walk into the studio thinking they will bust out a few takes, I will hit a couple of magic buttons, and the song will come out sounding like a radio hit. Four hours into the editing session, they are either asleep on the couch or pacing the room wondering what the hell is going on. Editing is the unglamorous work that nobody sees—the nitty-gritty that demands patience, obsessive attention to detail, and the determination to keep going when every instinct says “good enough.” This is what separates an average record from the spectacular sound that most people are not willing to take the time to achieve. I was willing, and it paid off.

Editing is about organizing and perfecting the recordings. It is an integral part of a “radio ready” product and lays the groundwork for the mixing process. The main objectives of editing are to:

1. Prepare the session
2. Convert MIDI to audio
3. Organize our recorded material
4. Choose the best takes and comp
5. Set basic levels
6. Strip silence
7. Reduce breaths
8. Remove any pops or clicks
9. Fix timing
10. Sample replace
11. Fix pitch
12. Add fades

So, let's begin!

Before you edit a single clip, get your session ready. Recording is done—you are no longer tracking, so your system priorities shift from low latency to maximum processing power.

1. Set the H/W Buffer to 1024 or 2048 (Setup → Playback Engine). During recording, you needed a low buffer for zero-latency monitoring. During editing and mixing, you need headroom for plugins and processing. Crank it up.
2. Enable Automatic Delay Compensation (ADC). In the Playback Engine window, set the Delay Compensation Engine to its highest value; then turn ADC on under Options → Delay Compensation (that menu item is the actual on/off toggle). This ensures plugins and inserts with different processing delays do not offset your tracks from each other.
3. Put the second monitor to work if you have one. Edit window on one screen, Mix window on the other—or keep a plugin window, meters, or the MIDI editor on the second screen. Editing involves constant zooming, scrolling, and switching between views. Having two screens cuts your editing time dramatically. I cannot imagine editing on a single monitor anymore.
4. Save As a new version (File → Save As). Name it sequentially: “SongName_v1,” “SongName_v2,” and bump the number every time you reach a checkpoint worth preserving. Higher number is always the latest. Simple, fast, hard to mess up. If it helps you track where you are in the process, append a stage tag at major handoffs—Song_v3_EDIT, Song_v6_MIX, Song_v9_MASTER—but only at the milestones; tagging every save gets tedious. If something goes catastrophically wrong during editing, you can always go back to an earlier version.

One more thing before you start moving audio: Pro Tools has four Edit modes—Shuffle, Slip, Spot, and Grid—and they are covered in detail in Step 3. Until you get there, stay in Slip, the default free-movement mode.

MIDI tracks are a gift during production—you can change notes, swap instruments, adjust velocity, and rearrange entire parts without touching audio. But MIDI is a set of instructions, not sound. Before you can edit, process, and mix, every MIDI track must become audio. I have seen students get halfway through a mix before realizing their synth bass is still MIDI and sounds completely different on someone else's system because they do not have the same plugin. Convert everything to audio first. Lock it down.

The Manual Method: Bus Routing

Route the output of each Aux or Instrument track to the input of a separate audio track using buses. Set the output of the virtual instrument track to a unique bus, then set the input of the destination audio track to the same bus. Record-enable the audio track and record. This method gives you the most control—you can process the signal through outboard gear or plugins on the way in—but it is tedious when you have dozens of MIDI tracks to convert.

The Fast Method: Commit

Use the Commit command (Track → Commit) to bounce an Instrument track to audio in place. Pro Tools renders the output directly to a new audio track without manual bus routing—sample-accurate, fast, and clean. This is how I convert most of my MIDI tracks today. The original Instrument track is hidden and made inactive by default (you confirm this in the Commit dialog), freeing CPU and keeping your session organized. If you need to go back to the MIDI version later, unhide the track and reactivate it.

I once opened a session from another studio that had 97 tracks, none of them labeled, none of them color-coded, and half of them muted with no indication of why. It took me two hours just to figure out what I was looking at before I could start editing. Do not be that engineer. Organization is not busywork—it is the foundation of every efficient editing and mixing session. It is easier to edit songs I record because I organize from the start. But when you inherit someone else's chaos, here is where to begin.

Separate Tracks

Each distinct element of the mix should be on its own track for maximum mixing flexibility—one audio track per instrument. If a part repeats, it can stay on the same track.

Label and Color-Code

Label every track clearly and assign colors by group—all drums one color, all vocals another, all guitars another. This sounds trivial until you are staring at 80 tracks at 2 AM and cannot remember which one is the second guitar overdub.

Order the Tracks

Choose whatever order gives you the greatest ease while editing. Organize similar tracks together, then place the most important or earliest-starting tracks toward the top. Here is the general order I prefer from top to bottom:

• AUX Buses (Main Groups: Drums, Bass, Instruments, Lead Vox, BG Vox, FX)
• AUX FX (Reverbs, Delays, Chorus)
• Bass / Kick / Snare / Toms / Hi-Hat / Ride / Overheads / Percussion
• Guitars / Keyboards / Winds / Brass / Strings / Sound FX
• VOX Leads / VOX BGs

Use Folder Tracks to nest related tracks—all drum tracks inside a “Drums” folder, all vocals inside a “Vocals” folder—that collapse or expand with a single click. This keeps large sessions visually manageable without affecting routing. Create one via Track → New (select Folder Track type), then drag tracks into it.

Set Up Auxes

Aux Input tracks pass audio through without recording—they continuously monitor an input and pass it to their output. A bus is an internal routing path that lets you send signal from one track to another without physical cables. The pattern: route all related audio tracks (e.g., your three vocal tracks: lead, double, ad-libs) to a shared bus. Create an Aux Input track that receives the same bus and outputs to your main output. All three vocals now flow through that Aux, where you can apply a single plugin chain or fade them as a group.

Set up at least these six Auxes: Drums, Bass, Instruments, Lead Vox, BG Vox, FX. Five is the floor—fold Lead and BG into one Vocals bus—but splitting the vocals pays off in the mix, and the denser the production, the more you subdivide (Guitars, Keys, Strings; my own run 16 auxes or more). These six organize most productions.

1. Create a stereo Aux Input track for each of the six buses (Drums, Bass, Instruments, Lead Vox, BG Vox, FX).
2. Set each Aux's input to a unique bus (Bus 1–2 Drums, Bus 3–4 Bass, Bus 5–6 Instruments, Bus 7–8 Lead Vox, Bus 9–10 BG Vox, Bus 11–12 FX).
3. Set each Aux's output to your main output (Out 1–2).
4. Route each audio track's output to the corresponding Aux's bus instead of directly to the main output.

Two fast ways to route many tracks at once: (1) select all the tracks, hold Shift+Option (Shift+Alt), click one track's Output selector, and choose the bus—every selected track is routed in one move. (2) Select the tracks, open any one's Output selector, choose new track…, and pick a stereo Aux—Pro Tools creates a named Aux and routes all the selected tracks to it. Either beats routing tracks one at a time.

Aux tracks earn their keep four ways: monitor the summed volume of grouped tracks; apply one plugin to many tracks at once (huge CPU savings on a session full of vocals or drums); visually identify sections in the Mix Window; and feed separate headphone cue mixes during tracking (covered in Chapter 12).

Set Up Groups

The grouping function links tracks so that changes on one apply to the rest. Open the group list at the bottom-left of the Edit Window—the default “ALL” group affects every track when active.

1. Select the tracks you want to group.
2. Hit Ctrl+G (Cmd+G), or click the triangle on the right of the group list and choose “New Group.”
3. Label the group clearly: “Drums,” “V1 Overdubs,” “Strings,” etc.

You do not need to group every set of tracks immediately. I group major sections with many tracks first (like Drums) and add the rest as I go. Groups are a fader-link convenience, not a structural commitment—you can always temporarily disable the group with the keypad.

Loop a Section

Looping a section repeats it during playback so you can audition it many times without restarting playback. Useful when checking takes, testing edits, or building a pattern from a short fragment.

1. Make sure the session tempo is set—a loop won't loop cleanly against a wrong grid—then switch to Grid mode.
2. Select the loop range precisely on the grid.
3. Right-click the Play button in the Transport and select “Loop” to enable loop playback.
4. To duplicate the loop as new clips on the timeline: Ctrl+D (Cmd+D) once, or Alt+R (Option+R) for multiple repeats. To copy clips to a later point in the timeline, highlight, copy in Grid mode, then paste at the target grid position.

Editing Modes

Before you start cutting and moving audio, you need to understand Pro Tools' four editing modes. These control how clips behave when you move, trim, or insert them—and choosing the wrong mode is one of the fastest ways to accidentally destroy an edit. I have seen students spend ten minutes carefully placing a clip, then switch to Shuffle mode without realizing it and watch their entire timeline collapse when they delete a region. Learn these modes. Know which one you are in at all times.

Shuffle (F1). When you move or delete a clip, all clips after it on the track slide over to fill the gap automatically. Powerful for assembling a sequence where you want everything to stay contiguous—podcast editing, dialogue assembly, or building a drum loop from individual hits. Dangerous if you activate it by accident, because deleting one clip shifts everything after it. But that same behavior is Shuffle's superpower for removing a whole section: in Grid mode, highlight the entire section across all tracks (say, a second verse or a post-chorus), switch to Shuffle, and delete—everything downstream slides up to close the gap with no silence left behind. Switch back to Slip immediately after.

Slip (F2). The default mode and your home base. Clips move freely without affecting anything else on the track. You can place audio wherever you want, overlap clips, and leave gaps. This is where you will spend most of your editing time. When in doubt, switch back to Slip.

Spot (F3). When you move a clip, Pro Tools asks for a specific timecode or bar/beat location. Essential in post-production, where sound effects must land at exact timecodes to sync with picture. In music production, you will rarely use Spot mode, but knowing it exists is important.

Grid (F4). Clips snap to the nearest grid line based on your grid resolution (bar, beat, 1/4 note, 1/16 note, etc.). This is the mode you switch to when fixing timing—every cut and move lands precisely on the beat. You can also hold Ctrl (Cmd) in Slip mode to temporarily snap to grid without switching modes.

You will switch between these constantly. Grid mode with a 1/16 note resolution is my default for timing work, and I keep one eye on the mode indicator at all times.

With your session organized, it is time to make the first creative decisions of the editing process: which takes are keepers and which are not. This is not a technical step—it is a musical one. You are listening for pitch, energy, rhythm, tone, and emotion. A technically perfect take with no feeling is worth less than a slightly imperfect take that gives you chills. Pay close attention, trust your instincts, and do not be afraid to combine the best moments from different recordings.

There are two ways to comp in Pro Tools, and which one you use depends entirely on how the session was recorded. If the takes are on separate playlists of a single track—use playlists. If the takes are on separate audio tracks—use multitrack comping. Honestly, I only use playlists if the session was recorded that way. I do not go set up playlists from scratch when the takes are already on separate tracks; that is more friction than it is worth.

Method 1 — Multitrack Comping (Takes on Separate Tracks)

The session arrives with ten takes of the lead vocal on ten audio tracks. None of them on playlists. This is how I receive most sessions and how I prefer to comp. Here is the workflow:

1. Mute every take track except one. Start with whichever take you think is the strongest—instinct is fine.
2. Loop a section (verse, chorus, phrase). Right-click the Play button in the Transport → Loop.
3. Cut and keep what you like. As the loop plays, separate (Ctrl+E / Cmd+E) the moments that work in this take. Mark them visually with track color, or by leaving them at full volume while muting the rest of the take.
4. Mute this take, unmute the next. Loop the same section again. Cut-and-keep pass on the new take.
5. Cycle through every take for that section. By the time you have looped through all of them, you have identified the best moments from every pass.
6. Move the keepers to a single consolidated track. Drag (or copy / paste in Slip mode) the chosen pieces onto a new audio track named “Lead Vocal Comp,” “Guitar Comp,” or whatever fits.
7. Add fades and crossfades across every comp seam so the joins are inaudible.
8. Hide and make inactive the source take tracks. Right-click the track header → Hide and Make Inactive. The takes are still in the session if you need them, but they stop costing CPU and they stop cluttering the screen during the rest of the edit.

The advantage: you can A/B between takes by toggling mute as you build the comp, and the visual layout in the Edit window matches how the takes were tracked. The disadvantage: it eats more vertical space than playlists. I tolerate it because it matches how my brain works during comping—I want every take laid out at once, not stacked in one column.

Method 2 — Playlist Comping (Takes on the Same Track)

If the session was recorded with each take on its own playlist of a single track (Chapter 12 covers how this is done), the playlist system is built for comping.

1. Switch to Playlist View. Click the Track View Selector (the waveform/clips dropdown) and choose “Playlists.” Every take appears as a lane underneath the main track.
2. Audition takes. Solo individual playlists with Shift+S; navigate between them with P and ; (Commands Keyboard Focus on, or hold Control on Mac / Start on Windows).
3. Highlight the best section of a playlist with the Selector tool.
4. Promote it to the main comp with the up-arrow on the selection, or Start+Alt+V (Ctrl+Option+V).
5. Add fades and crossfades across the seams so the joins are inaudible.

Whichever method you use, the goal is the same: assemble the best performance the session can deliver. I comp every lead vocal I edit. A verse from take two, a chorus from take four, a single word from take seven—whatever serves the song best. Comping is where editing stops being technical and starts being artistic. You are not just fixing problems—you are assembling a performance that never existed in a single pass but sounds like it did. Maserati's first day on the Mary J. Blige record? All comping. The “best take” is rarely a single take.

Pro Tools sums in 64-bit floating point, so the combined level of your tracks can pass 0 dBFS on the internal mix bus without distorting—but the instant that signal reaches a hardware output or a fixed-point bounce, anything over 0 dBFS clips. Plenty of plugins clip at 0 internally too. (Rumsey & McCormick, 2021) So the working rule stands: no single track should be anywhere near 0 dBFS. Yet I still consistently receive sessions from other engineers where the beat is at 0 dBFS and the vocals are being pushed up by +6 on the faders to compensate. The result is complete distortion—and people wonder why their mixes sound bad. The answer is that they have exceeded the headroom.

Clip Gain

The right way to set levels during editing is with Clip Gain, not the fader. This distinction matters and will come up again in the mixing chapters: Clip Gain controls the input volume—it adjusts how loud the signal is before it hits any plugins on the track's insert chain. The fader controls the output volume—it adjusts how loud the processed signal is in the mix after all inserts. During editing, leave your faders at unity (0 dB) and use Clip Gain to bring levels into the right range. Click on the bottom-left corner of any clip and drag to adjust—the waveform visually grows or shrinks. This keeps your faders clean and untouched for the mixing stage, where they belong.

Go through each track and use Clip Gain to bring levels down until the Aux peaks around −12 dBFS (where the green meets the yellow). Do not touch the Aux or Master faders—only adjust Clip Gain on the audio clips at this point. These are rough starting points—some elements naturally run hotter or cooler (drums a touch hotter, vocals around −10, effects around −14). The mixing chapters give specific targets; for now just keep everything well clear of 0 dBFS. At this stage it is not important to be exact—that is the mixing engineer's job. We just want to avoid overloaded signals while editing.

Clip Effects: Beyond Gain

Pro Tools extends Clip Gain into a broader feature called Clip Effects—non-destructive, clip-based processing that applies directly to individual audio clips without using insert slots. Clip Effects include pitch correction, gain adjustments, and EQ that travel with the clip wherever it is moved. The Clip Effects tab is detachable—you can pull it out into its own floating window for a more flexible editing layout.

The use case where Clip Effects pays off most at the editing stage is fixing a single problem spot—turn down a popped plosive, tame a harsh breath, or lift one too-quiet word—on just that clip, without touching the rest of the track. Surgical, fast, and reversible. (Heavier moves like EQ and compression are better left to the mix stage; Clip Effects can do them, but during editing keep it to cleanup.)

With levels set, clean up the empty and unnecessary regions on each track. Every track has noise between the parts that matter—bleed, room tone, hiss, handling noise. Leaving it in clutters the session visually and can add up to a noticeable noise floor when dozens of tracks are playing simultaneously.

Pro Tools has a built-in tool called Strip Silence (Ctrl+U / Cmd+U, or Edit → Strip Silence).

1. Highlight the clip you want to strip.
2. Open Strip Silence (Ctrl+U / Cmd+U).
3. Adjust the Threshold until the areas you want to keep are highlighted in the white box. Audio below threshold gets removed.
4. Fine-tune with Min Strip Duration so brief noises do not split into separate clips.
5. Adjust Clip Start Pad and Clip End Pad to ensure no desired audio is cut. After tweaking these, you may need to readjust Min Strip Duration. I usually leave Clip Start Pad at default (for VocAlign purposes) and only slightly adjust Clip End Pad.

Go through each track with Strip Silence, then—and this is critical—manually review every single track to make sure no audio is cut abruptly. Be careful not to cut too much. Strip Silence is smart, but it is not perfect. I have seen it chop off the tail end of a sustained guitar note, clip the beginning of a soft vocal entrance, and cut a drummer's ghost note clean in half. Trust but verify.

Special note on breaths. Vocal breaths often carry the emotion of a performance—a singer gasping into a chorus, a rapper's exhale before a punchline. Removing them entirely makes the performance sound robotic and inhuman. Sometimes breaths are important to keep—just turn them down. The next step (Breaths) covers exactly that.

Breaths are a natural part of a vocal take. They can show emotion and add a nice rhythmic element. However, some performers pack too many words into their lines and sound like they are dying when they finally take a breath. Once a recording is compressed, breaths tend to be magnified.

I don't recommend ever completely removing breaths unless a client specifically requests it. Better to turn them down.

1. Find the breath in the vocal take. Zoom in.
2. Highlight the breath region with the Selector tool.
3. Separate it (Ctrl+E / Cmd+E) so it becomes its own clip.
4. Turn it down with Clip Gain to a level that still feels natural—usually 6 to 10 dB below the surrounding vocal.

Waves makes a DeBreath plugin that automatically detects and reduces breaths by a specified amount. It saves time, but manually turning them down ensures the best results.

A single click in the middle of a vocal take can ruin an otherwise perfect recording. It might be a lip smack, a cable bump, a digital glitch, or a stray noise that snuck in during tracking. Whatever the cause, the listener will hear it—especially after compression amplifies it in the mix. If re-recording is not possible (and it usually is not, because the magic of the performance is irreplaceable), you need to fix it surgically:

Clip Gain. Highlight the pop, separate it with Ctrl+E (Cmd+E) to make it its own clip, then use Clip Gain to reduce its volume. Depending on the amount of gain reduction, this can greatly diminish the audibility.

Redraw the waveform. Use the Pencil tool. Zoom in until you can see the individual sample peaks and troughs as a single line. From this view, the Pencil becomes active. Draw a line completing the waveform without the click, following the natural peak-and-trough pattern.

iZotope RX (advanced). For more demanding noise repair, iZotope RX Spectral Editor now works directly in the Pro Tools timeline via ARA2 integration. You can visually identify and surgically remove clicks, pops, hum, and other noise artifacts without leaving your session or bouncing audio—a significant upgrade from the traditional AudioSuite workflow. For routine clicks and mouth noise, the iZotope RX De-click module (AudioSuite) is a one-pass fix I run on nearly every vocal—highlight the clip, render, done. The Spectral Editor is for the stubborn stuff the automatic De-click misses.

Timing is what makes a record feel tight or sloppy, and fixing it is where most of the real editing work happens. A drummer who rushes the fills, a bassist who drags behind the beat, a guitarist whose chord changes are late by a fraction of a second—these problems are invisible to most listeners, but they feel them. A tight track feels professional. A sloppy one feels amateur. The difference is often measured in milliseconds.

Start by switching to Grid mode (1/16 note to start). A click track helps for reference. The goal is not to make everything robotic—some songs breathe better with slight timing imperfections. The goal is to make sure the timing feels intentional. I use the grid as a reference, not a rule—I line things up to it as a starting point, then leave (or pull) hits slightly off-grid wherever the song wants a human feel. Tight is the goal; mechanical is not.

No Click? Build the Tempo Map from the Performance

Half the real sessions I have edited arrived without a click track. A band tracked live to tape, a singer wrote a song with just a guitar, a producer laid down a beat that drifted. The moment you switch to Grid mode and the waveforms do not line up with a single bar line, you have a choice: manually nudge every clip by hand ignoring the grid entirely, or spend fifteen minutes once and grid the grid to the band. Do it once, and every grid-based tool in Pro Tools—Beat Detective, Elastic Audio quantization, delay time sync, loop duplication—works on the actual performance. Skip it, and you fight the grid for the rest of the session.

Method 1: Identify Beat (manual, precise). The Identify Beat command (Event → Identify Beat, Ctrl+I/Cmd+I) lets you declare a specific audio moment as a specific bar and beat. You are telling Pro Tools: “this point in the audio is bar 2, beat 1”—and the session grid snaps accordingly.

1. Find a clean downbeat near the top of the song. Use Tab to Transients to land on the first kick or snare attack you are confident is the one. Zoom in to confirm.
2. Set a selection from that point spanning exactly one bar (or one phrase you can count). The selection length tells Pro Tools the tempo of that span.
3. Go to Event → Identify Beat. Enter the bar and beat of the selection start (e.g., Bar 1, Beat 1) and the selection end (e.g., Bar 2, Beat 1). Pro Tools inserts a tempo event at that point and adjusts the grid to match.
4. Advance to the next downbeat using Tab to Transients. Repeat: select the span, Identify Beat, declare the bar|beat. Work your way through the song section by section—verse, chorus, bridge—adding a tempo event wherever the band's tempo shifts. Most live bands drift by a few BPM between sections; a handful of events handles the whole song.
5. Check your work: with the tempo map built, the kick should now sit close to the bar lines in Grid view. It will not be sample-perfect—that is what Beat Detective is for next—but the grid should track the groove rather than fighting it.

Method 2: Beat Detective Bar|Beat Marker Generation (batch). For a full-length song with many tempo shifts, the manual Identify Beat approach works but is slow. Beat Detective's Bar|Beat Marker Generation mode—the same mode selector you met in the standard workflow above—does the same job automatically. Select the entire kick or snare region, set the mode to Bar|Beat Marker Generation, hit Capture Selection, and Analyze. Instead of cutting audio, Beat Detective detects each transient; click Generate to place tempo and bar|beat markers in the Tempo ruler at every one. The grid rebuilds itself to follow the performance. This is the batch version of Identify Beat—faster on a full song, though you will still want to audit the markers at any section that dragged or pushed significantly and correct outliers by hand.

Payoff. Once the tempo map matches the recording, the entire Pro Tools toolkit unlocks: Beat Detective Separation and Conform land on the right beats, Elastic Audio quantize snaps to the actual bars, delay time plugins sync to tempo in milliseconds, and loop-duplicate repeats land in the right place. Everything downstream assumes a valid tempo map. Without one, grid-based tools are guesswork.

When to skip it. If the track is deliberately rubato—a solo piano ballad, a spoken-word piece, a film cue meant to breathe freely—building a click-accurate tempo map serves no purpose and may actually damage the session by implying a metric structure that was never there. For those projects, leave the grid at a nominal BPM and edit purely in Slip mode. Film and post-production scoring uses cue-point markers and SMPTE sync instead of bar|beat grids; that workflow is covered in Chapter 20.

Pro Tools gives you several tools for fixing timing, from fully automatic to fully manual. Which one you reach for depends on the material and how much control you need.

Tab to Transients

The simplest way to fix timing manually is using the Tab to Transients button on the toolbar. Press Tab to skip to the next transient on the track. At the desired transient, hit Ctrl+E (Cmd+E) to cut. Use the Grabber to move the region until it snaps to grid. This is fast, intuitive, and gives you complete control over every edit.

Beat Detective

Beat Detective is the power tool. Where Tab to Transients is a scalpel, Beat Detective is a bulldozer—it can quantize an entire drum performance to the grid in minutes. I have used it to rescue drum takes that were so far off the beat they sounded like the drummer was playing a different song. It is not subtle, but when you need an entire track tightened up fast, nothing else comes close.

Open Beat Detective with Ctrl+8 (Cmd+8). Here is the workflow I use on every drum session—once you have done it a few times, the whole process takes under five minutes per track:

1. Prepare. Solo the kick track and select its entire region starting from bar 1 exactly. Delete any existing fades (Edit → Fades → Delete Fades)—Beat Detective needs clean transients to work with.

2. Analyze. Set Operation to “Clip Separation,” Contains to 16th note, hit Capture Selection, then Analyze. Beat Detective scans the audio for transients and places break points at each one. Adjust the Sensitivity fader until the lines land exactly on the hits—too high creates phantom cuts on bleed, too low misses quiet hits. Drag a stray line with the hand tool; hold Alt to delete one. Getting sensitivity right is the most important step. Spend an extra minute here and the rest goes smoothly.
3. Separate and Conform. Go to Clip Separation and click Separate—Beat Detective cuts the audio at every break point. Then go to Clip Conform and click Conform to snap each piece to the grid. The Strength parameter controls how aggressively regions move (100% = perfectly on grid, lower = looser feel). Exclude Within leaves hits that are already close enough alone. Swing adjusts the feel to 1/8th or 1/16th note swing percentages. I usually conform at full strength first, then listen—if it sounds too robotic, I undo and try 85% with a slight swing.

4. Smooth. The final step—do not skip this or your track will be full of clicks from the cuts. Select Fill and Crossfade, set crossfade length to 10 ms, and hit Smooth. This fills gaps between regions and adds tiny crossfades at each edit point. If Fill Gaps causes artifacts, manually create fades on the problem spots.

Beat Detective works beautifully on close-mic'd drums because of their sharp, clear transients. Other sources—electric guitar, vocals, drum overheads—have softer transients and more sustain, which makes detection less reliable. For those, use Tab to Transients or Elastic Audio instead. I use Beat Detective almost exclusively on kick, snare, and toms.

Editing Drums as a Phase-Locked Group

Here is the trap that has caught me more than once: I run Beat Detective on the kick, conform it to the grid, then run it separately on the snare and conform that. Everything looks tight. I hit play—and the kit sounds thin, blurry, and wrong. The overheads and room mics I left untouched are now slightly out of phase with the close mics I moved. The drummer recorded an entire performance with every mic capturing the same acoustic moment in time. The instant I move the close mics without moving the overheads, that relationship breaks. This is the same physics discussed in the sample replacement discipline below—transient alignment is not optional, and it is not just a close-mic concern. The whole kit is a phase system.

The fix is to stop treating the drum kit as a collection of individual tracks and start treating it as one edit unit. Every move on the kick must propagate to every other drum track—snare, toms, hi-hat, overheads, rooms, underheads, triggers—simultaneously. Pro Tools gives you two mechanisms to enforce this.

Edit Groups for drum timing work. An Edit Group propagates trimming, nudging, slip moves, and fades across every member track. Before you touch a single drum transient:

1. Select all drum tracks in the Edit Window—kick, snare, every tom, hi-hat, overheads, rooms, any room triggers or samples already in the session.
2. Hit Ctrl+G (Cmd+G), name the group “Drums Edit,” and make sure the Group Type is set to Edit (not Mix, not Edit and Mix—just Edit so you are not accidentally ganging faders during this pass).
3. Verify the group is active—the group name should be bold in the Groups list at the lower-left of the Edit Window. The keyboard shortcut to toggle any group on and off is its assigned letter; you can also click the group name directly.

With the Drums Edit group active, every trim, nudge, and crossfade you make on any member track ripples to the rest. A manual Tab-to-Transients fix on the kick repositions the identical frame on every other drum track at the same instant. Phase relationships stay intact because everything moves together.

Beat Detective Collection Mode. Collection Mode is how Beat Detective handles a multitrack kit in a single automated pass. The strategy: analyze trigger detection only on the tracks with the sharpest, most reliable transients—typically kick and snare—then apply Separation and Conform across every drum track including the overheads and rooms.

1. Analyze your trigger track. With Operation on Clip Separation, select the kick clip, Capture Selection, Analyze, and adjust Sensitivity until the break points land cleanly on every hit.
2. Add the triggers to the collection. In the Detection section, set the mode to Collection Mode and click Add All to copy the kick's break points into the collection. To fold in the snare, select and analyze it, then click Add Unique—this adds only the snare hits the kick analysis missed, combining both tracks' triggers into one reliable set with no duplicates.
3. Select all drum tracks in the Edit Window (kick through rooms). The selection must span the same bar range as your original analysis.
4. Click Separate. Beat Detective cuts every selected track at every break point in the collection. The overheads and rooms—which have softer transients Beat Detective could not reliably detect on their own—are cut at the same grid positions as the close mics.
5. Click Conform to snap every piece of every track to the grid at your chosen Strength setting.
6. Click Smooth with Fill and Crossfade enabled (10 ms) to seal every cut on every track simultaneously.

After the Conform pass, un-solo the kit and do the same check the sample replacement section teaches: listen to the full drum bus. The overheads should open the kit up—not make it smaller or weirder. If something smeared, one of the room tracks moved by a slightly different amount due to a stray break point; find it, nudge it back, and re-crossfade.

When not to grid-lock a performance. Some drummers play with deliberate push and pull—the snare leans back on the two and four, the kick rushes slightly into the chorus. That is feel, not sloppiness, and Beat Detective at 100% Strength will sand it flat. If the performance already grooves, either lower Strength to 70–80% (tighten without erasing the pocket) or skip Beat Detective entirely and use the Drums Edit group for targeted Tab-to-Transients fixes only on the hits that are genuinely problem timing outliers. The grid is a reference, not a verdict.

VocAlign for Vocal Timing

If you have ever tried to manually align twenty stacked background vocal tracks syllable by syllable, you know it can take an entire day. VocAlign by Synchro Arts does it in seconds. When it comes to lining up multiple vocal overdubs, this is the tool I reach for first. It analyzes a lead vocal take (Guide), then matches any overdub's (Dub) rhythm to that lead. It does not change pitch or tone—only timing. VocAlign supports ARA2 integration—alignment happens directly in the timeline without AudioSuite bouncing. Common uses:

• Verses with emphasis or harmony tracks underneath the lead—tightens up syllables with sharp transients like P's, T's, K's, and B's.
• Choruses with many stacked vocal tracks—though over-aligning can reduce the “bigness” of the hook. Sometimes going through manually yields better results.
• ADR (Automated Dialogue Replacement)—lining up re-recorded lines to the original production audio.

The workflow:

1. Click Guide, select the lead vocal clip, hit Capture.
2. Click Dub, select the overdub to align, hit Capture.
3. Hit Process. Done—the aligned region shows “VOAL” in its name.

The Alignment Rule dropdown controls how aggressively VocAlign stretches the dub—options run from Low to High Flexibility, plus Maximum Compression and Maximum Expansion. I keep it on Normal Flexibility for most work. The first time you see twenty background vocal tracks snap perfectly to the lead in under a minute, you will wonder how you ever lived without it.

Important VocAlign guidelines:

• VocAlign does not itself make things on beat—it only matches timing. If the guide is off beat, the dub will be too. Fix the guide first.
• Fade all regions before applying VocAlign (Ctrl+F / Cmd+F).
• Guide and dub must match word for word. Missing even one word confuses the algorithm. Go piece by piece if necessary.
• If you do not have VocAlign, do not worry—I went many years without it. It saves time, but everything it does can be done manually.

Revoice Pro and Waves Sync Vx

Synchro Arts also makes Revoice Pro, now also available via ARA2 in Pro Tools. Like VocAlign, it aligns timing, but it can also match pitch across multiple tracks and create synthetic doubles. This can be a major time saver—instead of tuning every background track, get the lead perfect, then Revoice the backgrounds. The drawback: as tracks become too tight, they start sounding like one voice. For a big sound, sometimes the old-fashioned way is best—get amazing takes or edit them manually.

Waves Sync Vx is a multitrack alignment tool that aligns up to 16 tracks simultaneously using up to 4 reference vocals. It handles both pitch and timing alignment with per-region or global settings, includes an internal DeNoise function that cleans the reference tracks during analysis (not the separate Clarity Vx plugin), and works non-destructively via ARA2 directly in the Pro Tools timeline.

Time Compression/Expansion and Time Shift

Sometimes you need to stretch or compress a specific region rather than moving it to the grid. Maybe a guitar part was recorded at the wrong tempo, or a vocal phrase needs to be shortened by 50 milliseconds to land before the downbeat. Pro Tools offers two AudioSuite tools for this: Time Compression Expansion (AudioSuite → Other) and Time Shift. Both change the duration of audio without affecting pitch. TCE is simpler—move the ratio bar left to compress, right to expand. Time Shift offers more control over transient handling and different audio types. Both are destructive—always save a copy of the original before processing.

Elastic Audio

Elastic Audio changed my workflow more than any other Pro Tools feature. Before it existed, every timing correction required cutting, moving, crossfading, and praying the edits were smooth. Elastic Audio makes timing correction real-time and non-destructive—you can warp, stretch, and quantize audio without rendering, and undo everything with a single click. It enables changing an audio file's tempo or timing without altering pitch. Chapter 13 introduced Elastic Audio in the production context; here is the full algorithm reference for editing work. The modern engine is élastique Pro by zplane, which beats the legacy modes for most uses. Click the Elastic Audio tab on a track and pick a mode by source type:

Monophonic is optimized for single-voice content—lead vocals, bass lines, solo instruments. Best when there is one pitch at a time.

Polyphonic handles complex, multi-pitched material: chords, full mixes, stacked instruments, choir, orchestra.

Rhythmic is the right call for percussion, drums, and rhythmic loops. Preserves transient attacks while stretching the sustain portions between hits.

Varispeed changes speed and pitch together, like speeding up or slowing down a tape machine. Useful for creative effects and lo-fi production.

X-Form is the highest-quality offline algorithm. Renders rather than playing in real time, using the iZotope Radius engine at maximum quality for transparent time-stretching and pitch-shifting with formant preservation. Use this when artifacts must be minimized—critical vocal or instrument processing where quality matters more than real-time playback.

élastique Pro is the modern default. Real-time, formant-preserving, sample-accurate stretching with inter-channel phase coherence on both monophonic and polyphonic audio. For most users, this is now the best choice across the board—the legacy Polyphonic and Monophonic modes survive mostly for backward compatibility.

When Elastic Audio is enabled, clips can be warped, stretched, and quantized in real time without rendering. You can even conform imported audio to your session tempo: enable Elastic Audio on the track, right-click the clip, and select Conform to Session Tempo. A drum loop recorded at 85 BPM will instantly play back at your session's 120 BPM without changing pitch. This is incredibly powerful for working with samples, loops, and stems from other sessions.

The trade-off is CPU usage—Elastic Audio processes in real time, which adds load to your system. If your CPU can handle it and you have many timing corrections on a track, Elastic Audio is the best choice. For isolated corrections on one or two spots, TCE or Time Shift may be lighter on resources. My recommendation: use élastique Pro as your default Elastic Audio algorithm, use Rhythmic for drums, and reserve X-Form for critical vocal or instrument work where quality is paramount.

Sample replacement is one of the most common techniques in modern production—and one of the most misunderstood. The idea is simple: substitute a recorded sound with a different sample. The instruments most often replaced are drums: kick, snare, toms, and sometimes crash cymbals. But sample replacement is not about throwing away what the drummer played—it is about enhancing or reinforcing it.

I use sample replacement on nearly every session that involves live drums. Even in a great-sounding room with great microphones, a kick drum sample blended underneath the original can add low-end weight and consistency that the raw recording lacks. A snare sample can add crack and brightness without replacing the character of the original performance. The key word is blend—I rarely replace a drum sound entirely. I layer the sample underneath the original and mix them to taste.

The manual approach:

1. Import the sample you want to layer (a kick sample for kick reinforcement, a snare sample for crack).
2. Duplicate the sample for every hit on the original track.
3. Line each duplicate up to the transient of the original hit. Get it close visually first.
4. Zoom in. Way in. Drop to the sample level until you can see the individual peaks and troughs of both waveforms. Phase matters here more than almost anywhere else in editing: the transient of your replacement needs to land within a few samples of the original. If it does not, the two signals partially cancel each other (phase cancellation) and the kick sounds thinner, not fuller—the opposite of what you wanted. Nudge the replacement by tiny amounts until the leading edges of both transients align cleanly. Sometimes that means five or six samples earlier or later before the phase locks in. Eyeball the polarity too—if the original transient pushes positive and the sample pushes negative at the same instant, flip the sample's phase (AudioSuite → Other → Invert) before aligning.
5. Blend with Clip Gain or mute the original entirely depending on how aggressive you want the replacement. Solo the layered hit while you check; un-soloing should make the drum sound bigger, not weirder.

This works but is tedious on a three-minute song with hundreds of hits. Dedicated tools like Slate Digital Trigger, SPL DrumXchanger, and Avid SoundReplacer (included with Pro Tools as an AudioSuite plugin) automate the process—they detect transients on the original track and trigger the sample at each hit with velocity sensitivity. These tools handle the phase alignment for you, which is half the reason to use them.

One workflow tip even with the automated tools: audition the result with the original muted, then with the original blended back in. A sample trigger that sounds great in isolation can sound weird in context—phase relationships with the rest of the kit (overheads, room mics, hat bleed) matter more than the trigger itself. Always check the full drum bus after replacement, not just the solo track. If the kit suddenly feels smaller or stranger after replacement, the sample is fighting the room mics. Flip the sample's polarity, or nudge the timing by a sample or two, and listen again. The goal is reinforcement, not replacement—when it works, no one in the room knows you did it.

Pitch correction has become so ubiquitous that it is hard to find a contemporary record that does not use it. But pitch correction is not just about fixing bad singing—it is about perfecting a performance. A vocalist might deliver an emotionally stunning take with one flat note in the chorus. Without pitch correction, you either live with the flat note, ask for another take (risking the emotional magic), or piece together a comp from multiple takes. With pitch correction, you fix the note and keep the magic. That is why it exists.

Pitch correction applies to all instruments, not just vocals. Drums can be out of tune with the key of the song. Guitars can drift sharp over the course of a take. Bass notes can wobble. Ideally, tuning is checked during recording—but when mistakes slip through, Pro Tools gives you several tools to fix them.

Pitch Shift (AudioSuite)

The simplest pitch tool in Pro Tools. Highlight a region and open AudioSuite → Pitch Shift (or Pitch II). Coarse adjusts in semitone increments (12 semitones = 1 octave). Fine adjusts in cent increments (100 cents = 1 semitone). With the Time Correction box checked, Pitch Shift adjusts pitch independently of time. Works well for a few changes or larger chunks that need transposition, but not ideal for many intricate changes throughout a song.

Elastic Audio for Pitch

Enable Elastic Audio on a track, select the clip, right-click, and choose Elastic Properties. Adjust semitones or cents. Changes are non-destructive and can be altered infinitely without audio degradation. A step up from AudioSuite, but for major changes across an entire track, dedicated pitch correction tools provide better results.

Melodyne (ARA2 Integration)

Melodyne is the Swiss Army knife of pitch editing—it can do things no other tool can. Pro Tools supports it via ARA2 (Audio Random Access), allowing pitch and timing editing directly within the Pro Tools timeline—no separate plugin window or audio bouncing required.

Auto-Tune

Auto-Tune by Antares uses autocorrelation to detect pitch, then shifts it to the nearest note in the chosen scale. It made its first noticeable mark on pop music as an effect in Cher's 1998 hit “Believe.” In the late 2000s it was made famous again by T-Pain. Today, it is hard to find a contemporary song that does not use pitch correction in some form.

The current products are Auto-Tune Pro—which offers both a real-time Auto Mode and a Graph Mode for note-by-note editing—and Auto-Tune, a streamlined real-time version with Modern and Classic correction modes. Both are available as AAX plugins. The walkthrough below uses Auto-Tune Pro; work in Auto Mode when possible so changes stay non-destructive. There are two ways to use it.

Auto Mode — The Quick Fix

Open Auto-Tune on a vocal track and set three things:

1. Input Type (Soprano, Alto/Tenor, Low Male, Instrument, or Bass Instrument).
2. Key of the song. This tells Auto-Tune which notes are valid—gray keys on the keyboard become off-limits.
3. Retune Speed. The soul of Auto-Tune. At zero, every pitch snaps instantly to the nearest note—this is the “T-Pain effect,” the robotic sound that defined an era of hip-hop. At 50 or higher, the correction is gentle and nearly invisible—the singer sounds like themselves, just more in tune. I usually start around 30 and adjust from there. The Humanize control adds natural pitch drift so the vocal does not sound artificially perfect.

Auto Mode is fast and works well as an effect or when the vocalist is already close to pitch. But it is a blunt instrument—it corrects everything the same way, whether a note needs heavy correction or none at all. For serious vocal editing, Graph Mode is where the magic happens.

Graph Mode — The Professional Standard

This is how records are actually tuned.

1. Click Graph to enter Graph Mode, then hit Track Pitch (in Pro Tools the trace follows the session automatically—just roll the transport and it lines up with your playhead).
2. Play the entire vocal. Auto-Tune traces the pitch as red lines in real time.
3. Stop playback and click Make Notes. The squiggly pitch data snaps into clean, editable note blocks.
4. Drag notes to the correct pitch. Up to raise, down to lower. You are moving the note blocks Make Notes created, not the original pitch trace—the red line stays put as your reference.
5. Set retune speed per note. Fast correction on the obviously flat chorus note; slow and gentle on the verse where natural vibrato is part of the emotion. Disable correction entirely on notes that are already perfect.

The green line shows the corrected output overlaid on the red original—you can see exactly what you are changing and by how much.

This is the level of control that separates a demo from a record. Professional vocal editors spend 30–60 minutes per song in Graph Mode, going note by note, shaping the pitch correction to serve the performance rather than replace it. The drawback: once you commit the processing, the audio cannot be moved in the timeline without losing alignment. Record the tuned track to a new audio track by bussing the output to lock it in.

Waves Tune and Other Alternatives

Other popular pitch correction plugins include Waves Tune Real-Time and Melodyne. The controls are similar, but their sounds differ. For my money, Melodyne is the most capable and convenient of the three—ARA2 integration, deep functionality, and the easiest workflow—so it is my main tool. Waves Tune is arguably the most natural and transparent-sounding when I want the correction invisible. Auto-Tune I use mostly as an effect (the audible, stylistic kind). Different jobs, different tools—but Melodyne does the most. Melodyne can also break apart chords and offers audio timing quantization in addition to pitch correction.

Waves Tune and Melodyne can also create harmonies. Dedicated harmony plugins like Antares Harmony Engine and Eventide Octavox are useful for this as well. Remember: pitch correction is not just for vocals—make sure drums and instruments are in tune with the key of your song.

This is the step most beginners skip, and it is the reason their edits click and pop. Every time you cut audio, the waveform is interrupted at whatever sample value it happens to be at—which is almost never zero. That sudden jump from signal to silence (Pohlmann, 2010) (or from one clip to another) creates an audible click. Fades solve this by gradually ramping the volume to or from zero, ensuring smooth transitions.

A fade-in is a gradual volume increase placed at the start of a region. A fade-out is a gradual volume decrease at the end. Together, they eliminate the clicks that occur when audio is cut off abruptly. Every single clip in your session should have fades on both ends—no exceptions. I have received sessions from other engineers with hundreds of unfaded edits, and the entire mix crackles like a vinyl record. Five minutes of batch fading would have prevented it.

To add a fade:

1. Select the fade area at the start or end of a clip.
2. Hit Ctrl+F (Cmd+F). The fade is created at the default curve.
3. Or use the Smart Tool: hover the top corner of a clip and click-drag to draw the fade visually.

A crossfade fades two overlapping files so the first fades out while the second fades in. Add crossfades by selecting the transition area and hitting Ctrl+F (Cmd+F), or use the Smart Tool on the bottom corner of connecting regions and drag.

Different fade types and curves work better in different scenarios, and knowing which to reach for is the difference between a crossfade that is truly inaudible and one that dips in level or sounds hollow. The two principles that matter:

Equal-gain (linear) crossfades. The outgoing clip fades down at a constant rate while the incoming clip fades up at the same constant rate. At the midpoint, each clip is at −6 dB. When the two signals are phase-coherent (Rumsey & McCormick, 2021)—the same take, the same instrument, highly correlated audio—those two half-level signals sum back to 0 dB and the level through the crossfade stays constant. This is the right choice for: drum edits on the grid (the audio on both sides of the cut is essentially the same performance a few milliseconds apart), comps of the same take (adjacent phrases from one continuous recording), and Beat Detective conform splices where the material is continuous and phase-matched. Short equal-gain crossfades—5 to 10 ms—are what the Smooth step in Beat Detective applies by default, and they work because the audio is correlated.

Equal-power crossfades. Each curve sits approximately −3 dB at the midpoint, so the power of the combined signal stays constant rather than the level. When the two signals are uncorrelated—different performances, different rooms, a scene change from one ambience to another—equal-gain crossfades produce an audible level dip at the midpoint because the two −6 dB signals do not sum coherently. Equal-power curves compensate by keeping each signal at −3 dB at the crossing point, maintaining a consistent loudness through the transition. Use equal-power for: section joins between different performances, ambience or room tone crossfades, comps stitched from multiple takes, and any edit where the audio on either side of the cut is not from the same continuous recording moment.

In the Pro Tools Fades dialog. When you press Ctrl+F (Cmd+F) on an overlap to create a crossfade, the Fades dialog opens. The left curve is the fade-out shape; the right is the fade-in—and the Link setting between them is where the math above lives: choose Equal Power or Equal Gain and both curves follow the chosen law together. The shape presets—Standard and S-Curve (slow start, fast middle, slow end, useful for gradual room transitions)—set the curve contour on top of that, and the curves are also user-draggable. The default fade shape Pro Tools uses for batch fades (when you close the dialog without customizing, or use Smart Tool drags) is set under Setup → Preferences → Editing in the Fades section. Set your default to equal-gain for drum-editing sessions; switch to equal-power when doing vocal comping and section assembly across different takes.

Practical defaults. Short equal-gain (5–10 ms) on Beat Detective conform splices and drum grid edits. Equal-power (20–50 ms) across section changes, room-tone joins, and comps stitched from different takes. The listen test is always final: solo the crossfade point, loop it, and if there is any dip, bump, or tonal color change through the transition, swap to the other curve type. It is crucial that every separate audio region has fades at the beginning and end—the crossfade shape question only arises at the joins between two clips, but the no-exceptions rule on all clip boundaries stands.

Batch Fades

Select all clips on a track (or across multiple tracks), then hit Ctrl+F (Cmd+F) to apply fades to every selected region at once. This is a major time saver when finalizing an edit—instead of fading each clip individually, you can batch-process an entire session in seconds.

A few years ago I finished editing a record, zipped the session folder, and sent it to the mix engineer the same afternoon. He called me two hours later. Half the tracks had no fades, the tempo was undocumented, and three of the virtual instrument tracks were still MIDI—they played completely differently on his system because he did not have my synths installed. We lost a day. The session was not ready; I just thought it was. Since then I follow the same preparation protocol every time, whether the mix engineer is across town or across the country, and whether that engineer is someone else or a future version of me picking the session up six months later.

Consolidate every clip to a common start point. Before anything else, every audio track in the session must begin at exactly the same position—bar 1, beat 1. Select all clips on a track, set your selection to start at bar 1 and extend to the end of the song, and use Edit arrow Consolidate Clip (Shift+Option+3 on Mac / Shift+Alt+3 on Windows). Pro Tools renders the selection—including all edits, fades, and Clip Gain adjustments—into a single continuous file. Do this for every track. The result: the mix engineer drops all files into a new session, lines them up at the top, and everything sits in perfect sync without a single grid offset to chase. If a track does not start until bar 17, bar 1 through bar 16 is silence. That silence is intentional and load-bearing.

Track naming and color conventions. Every track must have a clear, descriptive name before delivery: KickDrum, SnarTop, BassGtr, LeadVox, VoxBG_Chorus, GtrRhythm_L, GtrRhythm_R. No Audio 1, no Instrument 7. Color-coding by section (all drums one color, all vocals another, as covered in Step 3 of this chapter) should be preserved in the delivered session—the mix engineer's first job is orientation, and your color scheme is the map. A well-organized session is a form of professional courtesy that gets you called back.

Stem Bounce Specifications

Stem — A bounced audio file representing one group of related tracks: all drums summed to one stereo file, all guitars to another, lead vocal on its own, and so on. Stems give the mix engineer a clean, plugin-free signal that can go through any processing chain without carrying your edit-stage inserts.

Bounce specs are non-negotiable: match the session's bit depth and sample rate exactly. If the session is 48 kHz / 24-bit, every stem bounces at 48 kHz / 24-bit. Do not convert. Do not upsample. Do not deliver 16-bit WAV to a 24-bit session. Use Pro Tools' Bounce Mix dialog (File arrow Bounce to arrow Disk; the dialog was renamed from Bounce to Disk, Ctrl+Alt+B / Cmd+Option+B), selecting each group's bus as the Mix Source and bouncing offline, with Bit Depth set to match the session and Sample Rate set to match the session. Every stem starts at bar 1. File names follow a consistent scheme: SongTitle_Drums.wav, SongTitle_Bass.wav, SongTitle_LeadVox.wav, SongTitle_BgVox.wav, SongTitle_Guitars.wav, SongTitle_Keys.wav, SongTitle_FX.wav. Descriptive, unambiguous, and alphabetically sortable.

Print or document outboard gear and critical automation. Any hardware insert in the signal chain—a hardware compressor on the drum bus, a tube EQ on the vocal—produces a sound that lives nowhere in the session file. Either print it: route the hardware insert output to a new audio track and record a real-time pass with the hardware in the chain, then bypass the hardware insert going forward. Or document it in full: make, model, and every knob setting, photographed and included in the session notes file. Critical automation—a volume ride on the lead vocal, a filter sweep that defines the drop—should be rendered if the mix engineer is working in a different DAW; if staying in Pro Tools natively, the automation playlists travel with the session as long as you deliver the .ptx file. When in doubt, print it. A printed move can always be undone; an undocumented hardware setting cannot be recalled from memory six months later.

The Session Notes File

Include a plain text or PDF file in the session folder named SongTitle_SessionNotes.txt. At minimum it contains:

• Tempo (BPM) and any tempo changes with their bar locations.
• Key and mode of the song (e.g., “A minor, natural”).
• Reference track: artist, song title, and what you are referencing it for (low end, vocal level, overall loudness).
• Plugin list: every third-party plugin used in the session, with version number. The mix engineer needs to know if they are missing something.
• Outboard list: any hardware processor in the chain and its settings, even if you printed the pass.
• Any notes about the edit: a comp seam that still feels rough, a timing correction that might be too tight, a sample replacement that needs blending adjustment.

One paragraph of honest editorial saves hours of guesswork. I write mine as if I will not be available to answer questions—because sometimes I will not be.

Exchange Formats: Cross-DAW vs. Native

AAF (Advanced Authoring Format) — The modern interchange standard for moving a session between different DAWs, including timeline position, track names, clip gain, and volume automation. When the mix engineer is working in a different DAW (Logic, Nuendo, Studio One, Resolve), export an AAF from Pro Tools: File arrow Export arrow Selected Tracks as OMF/AAF, which carries the timeline, track names, clip gain, and volume automation into the receiving DAW. AAF retains more metadata than OMF (Open Media Framework), the older format that loses track names and volume automation on export. Use AAF over OMF whenever the receiving DAW supports it.

When the mix engineer is on the same DAW—Pro Tools to Pro Tools—skip the interchange format entirely. Deliver the native .ptx session file plus all audio via File arrow Save Copy In arrow check “All Audio Files” and “Session Plug-In Settings Folder.” The receiving engineer opens a complete, self-contained folder with every referenced file present. This is always cleaner than an AAF when both ends are Pro Tools.

Delivery and Integrity Check

Zip the session folder before sending. After the zip completes, unzip a copy and open it on your own machine—or a second machine if you have one—to confirm the session opens without missing files and that every stem plays back cleanly from bar 1. A corrupt zip or a missing audio file discovered after delivery costs credibility. Catching it yourself costs nothing.

Session Handoff Checklist

1. Every MIDI / Instrument track committed to audio (Track arrow Commit).
2. Every ARA2-edited track (Melodyne, VocAlign, RX) committed or consolidated—uncommitted ARA edits do not print to stems.
3. All clips consolidated from bar 1 to song end on every track.
4. All tracks named descriptively; color-coding preserved.
5. All fades and crossfades applied to every clip (Ctrl+F / Cmd+F).
6. Stems bounced at session bit depth and rate, named consistently, all from bar 1.
7. Outboard hardware passes printed to audio; automation printed or documented.
8. Session notes: tempo, key, reference track, plugin/outboard lists, editorial notes.
9. Exchange format chosen: AAF for cross-DAW, native .ptx + Save Copy In for Pro Tools-to-Pro Tools.
10. Session folder zipped; integrity verified by reopening on a clean machine before delivery.

With organization, levels, cleanup, timing, pitch, and fades all done, the song is edited. It has come a long way from the recording stage.

Editing is the work that nobody talks about at parties. Nobody asks “who edited that record?” the way they ask who produced it or who mixed it. But every great record you have ever heard was edited—meticulously, painstakingly, and often for longer than the recording and mixing combined. The drummer's fills are tight because someone spent an hour in Beat Detective. The vocal sounds effortless because someone comped forty takes into one flawless performance. The guitars lock with the bass because someone nudged every chord change by 10 milliseconds.

The discipline you build in this phase—the patience to go through every clip, every transient, every breath—is what separates engineers who deliver professional results from those who deliver “good enough.” Good enough is not good enough. Not in this business.

One more thing: save your edited session as a new version before you start mixing. I save every major checkpoint as a sequentially numbered version—“SongName_v3,” “SongName_v4,” and so on. Higher number is always the latest, and I never have to remember which milestone-name I used last time. If the mixing engineer (even if that is you) needs to go back and re-edit something, the earlier version is preserved exactly as you left it. If a client changes their mind about a comp or wants a different take, you can roll back without undoing hours of mixing work. This habit has saved me more times than I can count.

The song is now ready for the next stage: equalization, dynamics processing, and the art of mixing. Everything that follows—every EQ move, every compressor setting, every reverb send—depends on the quality of the edit you just completed. A perfectly mixed song built on a sloppy edit will never sound right. A well-edited song can survive even a mediocre mix. The edit is the foundation. Make it count.