Before diving into plugins, mixing, or effects, it's worth understanding the actual path audio takes through a DAW (Digital Audio Workstation) from input to speakers. Once this route is clear, questions like "where do I put a reverb so every track shares it?" or "why isn't my recording being heard?" answer themselves.
The basic chain
Every DAW — whether it's Ableton, Logic, Pro Tools, FL Studio, or anything else — follows roughly the same signal path:
- Input — a microphone, instrument, or virtual instrument generates or captures sound
- Track — that input is recorded onto (or programmed into) an individual track, with its own volume, panning, and effects
- Bus (optional) — several tracks can be routed together into a shared bus — for example, all your drum tracks feeding one "Drums" bus — so they can be processed and leveled as a group
- Master — every track and bus eventually feeds into the master channel, which controls overall output level before it reaches your speakers or headphones
Why tracks aren't just "recording slots"
It's easy to think of a track only as a place a recording lives, but a track is really a channel with its own signal path: input, volume fader, pan control, and an effects chain that only affects that track. Understanding a track this way makes it obvious why adding a compressor to one track doesn't affect any other — the signal for each track is independent until it's deliberately routed somewhere shared.
What a bus is actually for
A bus groups multiple tracks so they can be treated as one unit. Two common uses:
- Grouped processing — compress or EQ an entire drum kit together, rather than each drum piece separately, so they move as one cohesive unit
- Shared sends — rather than adding the same reverb plugin to ten separate tracks (which wastes processing power and is hard to keep consistent), send a little of each track to one shared reverb bus, so every track is being processed by the same reverb, at levels you control individually per track
The master channel
Every signal eventually arrives at the master channel, which is why it's the right place for final, whole-mix decisions — overall loudness, a gentle limiter to prevent clipping, maybe tonal balance for the mix as a whole. It's the wrong place for anything that should only affect one instrument, since by the time audio reaches master, it's already blended together and can't be un-mixed.
Putting it together
Input → track → (optional bus) → master isn't just DAW trivia — it's the mental model that makes routing decisions obvious instead of guesswork. When something's not working (a track's silent, an effect isn't applying, a group of instruments won't level together), tracing the signal along this path is usually the fastest way to find where the chain broke.