Video summary
Mastering Signal Flow in Pro Tools (pt 1)
Main summary
Key takeaways
Main ideas / lessons
- Clip volume and track volume are not the same in Pro Tools because they affect signal flow at different points in the chain.
- Understanding the exact order of processing is crucial: boosting/lowering at different stages changes what gets pushed into later components (plugins, compressor thresholds, buses, etc.).
- Inserts, volume, panning, outputs, and sends each occur in a specific sequence and shape how dry and wet/effects mixes are built.
- VCAs are control elements (a group “volume controller”), not an additional audio-processing stage.
- Master tracks can intercept audio between a bus and its destination, changing where mastering/processing occurs in the signal path.
Pro Tools signal flow order (timeline → speakers / bus / effects)
1) Clip inherent volume (Unity gain concept)
- When a clip is placed at 0 dB (unity gain), its level is the original audio level.
- This is the baseline before any clip gain/volume automation is applied.
2) Clip Gain (clip-level gain adjustment)
Clip gain is adjusted via:
- The fader icon under the clip (drag up/down), ranging from -infinity to +36 dB
- The clip gain line (typically using the Smart Tool)
- If the clip gain line is missing:
- Enable it via View → Clip
- Ensure clip gain line / clip gain info are turned on
Returning to unity:
- Option-click the clip gain line, or
- Control + Shift + B to reset the current selection to unity
Why it matters: clip gain changes what later processing stages (especially plugin inputs) receive.
3) Inserts (plugins, in chain order)
- After clip gain, the signal goes into the track’s inserts (plugins).
- Order matters: plugins process sequentially down the chain (A → B → C → …).
Example given:
- With Pro-Q4 then Pro-C2:
- Lowering clip gain makes the signal lower inside the plugins.
- Boosting clip gain makes the signal higher inside the plugins.
Important warning:
- You can clip plugin inputs, which may cause distortion/aliasing and other unwanted artifacts.
Compressor-specific explanation:
- Threshold at 0: most signal passes, but boosting can still cause input/output clipping.
- Lowering the threshold causes more gain reduction/compression, especially if the signal feeding the compressor is louder.
- Goal: avoid clipping into the compressor before it reaches the threshold you intend.
4) Volume (track volume)
- The signal then reaches track volume (automation lane / volume control).
- Key rule: Volume comes after inserts, not before.
- Consequence described:
- Reducing volume reduces the output level after plugin processing.
- You do not change how much signal reaches the plugins—the plugin activity is determined earlier by clip gain and the inserts stage input.
5) Panner
- Next, the signal goes into the panner (stereo or multi-channel).
- Pan redistributes the signal across channels (left/right or multi-channel equivalents).
- Demonstrated behavior: panning right sends it more to the right-side meter/channel(s).
6) Track Output → assigned destination (folder/bus)
- After panning, audio goes to the track’s output destination.
- Example described: track output set to an AFX folder (receiving routing destination).
- Increasing track volume increases how much signal reaches that folder.
- Pan affects how the routed signal appears (e.g., stereo-wide vs more directional).
Parallel routing: Sends (dry + effects)
7) Sends happen in parallel with the main output
- Alongside the main output routing, the audio also goes to a send (if send level is above -infinity).
- The signal splits:
- Main path continues to the folder/output
- Send path goes to a bus destination determined by routing (via IO window buses)
Send level control logic:
- The send fader controls how much signal is sent to the effect destination.
- Example relationship noted:
- If track volume is decreased, the send amount is also reduced
- If track volume is increased, the send amount increases
Example reverb chain:
- Clip → inserts → volume → pan → (main output to folder/stem input) = dry path
- Simultaneously: send → reverb return input → reverb plugin (e.g., Altverb) → effect stem
Result:
- A parallel mix of:
- Dry (direct to the stem/folder path)
- Wet (reverb return into the same stem)
Purpose:
- Balance send level vs dry to adjust perceived distance (close/distant sound).
VCAs (control, not part of core signal flow)
What a VCA does
- VCAs are not a traditional signal path stage where audio passes through.
- A VCA is assigned to a group of tracks (created via grouping, e.g., Command+G after selecting tracks).
- It acts as a controller/trim for volume:
- The example describes a blue “delta” line showing an applied difference (e.g., “-21”).
- Functionally:
- It adjusts the effective volume of included tracks.
- It does not represent additional insert processing—it controls volume as a multiplier/offset behavior.
Master tracks (intercepting audio on the bus)
How master tracks sit in the chain
- Normally, track output goes directly to its destination (folder).
- If a master track is created (example: 7.1.2 to Master Fader), it sits on the bus, not after the destination.
- Analogy given:
- A bus is like a cable; audio travels along that bus.
- The master sits in the middle, intercepting and processing before audio reaches the folder destination.
What master processing affects
Because it intercepts on the bus:
- Master volume and inserts affect audio before it reaches the destination (e.g., the folder).
Example usage described:
- Masters used when bouncing stem deliverables:
- stems sent to bounce stems
- masters apply limiting/compression
- may also fold down (e.g., spanner + panner) to create different deliverables
Practical takeaway: clip gain vs volume
- When someone asks “Why clip gain vs volume?”:
- The difference matters because each affects signal at a different point in the chain.
Consequences:
- Using clip gain changes what hits plugins, affecting downstream behavior (including compressor behavior and risk of plugin input clipping).
- Using volume adjusts after inserts, changing final output level and bus/summing behavior without changing how plugins were driven.
Speakers / sources featured
- Matt Yokum (host/presenter, “My name is Matt Yokum”)