Engineering 001 | GetLife University
Time: about 90 minutes of reading and listening, plus 30 minutes of drills. No gear required beyond a computer and headphones.
Before we open a single piece of software, we're going to spend one module on the stuff underneath all of it. Not because theory is noble — because every confusing thing a DAW will ever do to you traces back to five ideas, and they fit in ninety minutes. Learn these once and Pro Tools, Logic, the LUMEN Studio, and every DAW that hasn't been invented yet will make sense on sight.
Here's the promise of this module: by the end, when a recording sounds bad, you'll know where in the chain it went bad. That single skill separates people who record from people who engineer.
Sound is air moving. That's the whole secret.
When someone speaks, their vocal cords push air back and forth. Those pushes travel through the room as waves of pressure — air squeezed a little tighter, then a little looser, over and over — until they reach an ear or a microphone. A microphone is just a machine that feels those pressure changes and turns them into an electrical signal that wiggles the exact same way the air did.
Everything you will ever do as an engineer is managing that wiggle.
Two properties of the wiggle matter, and each has a unit:
How fast it wiggles — frequency, measured in hertz (Hz).
Fast vibrations sound high. Slow vibrations sound low. A deep 808 bass sits down around 40–60 Hz. A voice lives mostly between about 100 Hz and 4,000 Hz (we write 4 kHz — "k" means thousand). The shimmer on a hi-hat lives up around 8–12 kHz. Healthy young ears hear from roughly 20 Hz to 20,000 Hz, and that range shrinks from the top down as we age. When an engineer says a mix is "muddy," they mean too much energy somewhere around 200–500 Hz. When they say it's "harsh," they usually mean too much around 2–5 kHz. You don't need to memorize a frequency chart today — you need to know that every tone has an address, and the address is a number in Hz.
How big it wiggles — amplitude, which we experience as loudness, measured in decibels (dB).
Decibels are strange at first because they don't count up from zero the way dollars do. In your DAW, 0 dB is the ceiling, and everything useful happens in negative numbers below it. A signal at −18 dB is quieter than one at −6 dB. This feels backwards for about a week and then becomes second nature. One handy anchor: a change of about 10 dB sounds roughly twice as loud to human ears, and 1 dB is close to the smallest change most people notice on normal material.
That's the physics. Frequency is which note and tone. Amplitude is how much of it. Hz and dB. If you only learn two units in your life as an engineer, it's those two — and now you have them.
Every recording ever made travels a path. Engineers call it the signal chain, and the discipline of engineering is mostly this: know every link in your chain, in order, and know what each link does to the signal.
Here is the chain for a simple vocal recording:
```
Voice → Room → Microphone → Preamp → Converter (A/D) → DAW
```
Walk it with me, link by link:
And on playback, the chain runs in reverse: DAW → converter (D/A) → headphone amp → headphones → air → your ears.
Why this matters practically: when something sounds wrong, you debug the chain in order. Recording noisy? Is it the room (air conditioner, street), the mic (cheap, or pointed wrong), or the preamp (gain cranked so high it's amplifying its own hiss)? Recording distorted? Some link got hit with more signal than it could handle. You never again have to say "it just sounds bad." You can say where.
Gain is how much you amplify a signal at any given link in the chain. Gain staging is the craft of setting the level at every link so the signal arrives at the next one healthy — strong enough to sit well above the noise, and low enough that nothing distorts.
Think of the signal chain as a relay race. Each runner (each link) has to hand the baton to the next at a good height. Hand it too low, and the next runner has to fumble around near the ground — that's a weak signal getting drowned in noise when you turn it up later. Hand it too high — over the runner's head — and the baton is dropped entirely. That's clipping, and we'll get there in the next lesson.
Here's the practical, do-this-today version for recording into any DAW:
Aim your loudest moments at about −12 to −6 dB on the track's meter, and let the average sit around −18 dB.
That's it. That's the professional target. Not "as loud as possible without going red" — that's a habit left over from tape and early digital, and it causes most beginner disasters. Modern 24-bit recording has so much clean range that a signal averaging −18 dB is pristine. Recording hot buys you nothing and risks everything.
How you actually set it: have the artist perform the loudest section of the song — not a polite soundcheck "test, test," but the real chorus at real energy — while you watch the meter and adjust the preamp gain. Set the gain so those loudest peaks land around −12 to −6. Then leave it alone. Performers get louder when the red light turns on and the take gets real; the headroom you left is what saves you.
One more distinction that will serve you for years: gain is set before recording; faders are for after. The fader on a track in your DAW changes playback level — it does not change what was captured. If the recording itself is distorted, no fader ride will un-distort it. Gain decisions are permanent. Fader decisions are always reversible. Spend your care accordingly.
In digital audio, 0 dB isn't a suggestion — it's a wall. The converter measures the signal with numbers, and 0 dB is the biggest number it can write. When a signal tries to go past 0, the converter can't represent it. It just writes the maximum, over and over, until the signal comes back down. On the waveform, the naturally rounded peaks come out flat-topped — sheared off like someone took scissors to them.
That shearing is clipping, and it sounds like a crackly, splattering distortion stuck to every loud moment. Here is the part you must internalize: the information above the ceiling was never captured. It isn't hidden in the file waiting for a repair plugin. It doesn't exist. A clipped recording is a photograph taken with the lens cap half on — you can adjust the picture forever, but the missing part was never in the camera.
(You may one day meet producers who clip things on purpose as a distortion effect — aggressive drums, certain rap vocals. That's a flavor choice made deliberately, in a controlled spot, usually with a plugin. It is a different universe from accidentally clipping a once-in-a-lifetime vocal take at the converter. Learn the rule before you learn the exceptions.)
Headroom is the space between your signal's loudest peak and that 0 dB ceiling. If your peaks hit −8 dB, you have 8 dB of headroom. Headroom is not wasted space — it is insurance you've already paid for. It absorbs the chorus the singer belts 5 dB louder than rehearsal. It absorbs the ad-lib that jumps out of nowhere. Every professional recording you love was tracked with generous headroom and turned up later, because turning up a clean recording is free, and un-clipping a hot one is impossible.
The habit to build: watch peaks, keep them under about −6 dB while recording, and treat any red clip light on a recorded take as a re-record, not a shrug.
Close your eyes in a room while someone talks as they walk around you. You can point at them the whole time. Two ears, one brain comparing the tiny differences between them — that's how humans locate sound, and stereo audio is built on that trick.
Mono is one channel of audio — one signal. Played on two speakers, the same signal comes out of both, and your brain places the sound dead center, floating between them.
Stereo is two channels — left and right — that can differ. Make a sound louder in the left channel, and it seems to sit left of center. The whole space between your speakers where sounds can be placed is called the stereo image, and the knob that places a mono sound within it is pan.
How real records use this: the elements that carry the song — lead vocal, kick, snare, bass — almost always sit in the center. Width is built around that spine: hi-hats a little off to one side, doubled guitars or keys panned hard left and hard right, background vocals spread wide, reverb filling the space between. Center = power and focus. Sides = size and interest.
Now, the professional habit that surprises every beginner: engineers constantly check their stereo mixes in mono. Every DAW has a way to collapse the mix to mono for a moment — a button or plugin on the master output. Why bother? Two reasons.
First, the real world folds your mix to mono without asking: a phone speaker, one earbud shared between friends, a Bluetooth speaker across the room, a club system summed to mono so it hits the same everywhere on the floor.
Second — and this is the physics — when left and right collapse into one channel, any place where the two channels carry opposite versions of the same wiggle (one pushing while the other pulls), those parts subtract from each other and get quieter, or vanish. Engineers call this being out of phase. A mix can sound huge in stereo and then lose its whole low end, or an entire synth, the instant it hits a phone speaker. Checking in mono is how you find out before your audience does.
Beginner rule of thumb: record single sources (a vocal, one instrument) in mono; build width in the mix with panning and effects; and flip the whole mix to mono for ten seconds before you call anything done. If it still sounds solid, you're safe everywhere.
Everything in this module funnels into a ritual — three questions answered before the red light, every session, forever. They take thirty seconds once they're habit, and they are the difference between capturing a moment and losing one.
Decision 1: What am I capturing, and where?
The source and the room. Is the artist warmed up, comfortable, close enough to the mic (for a vocal, roughly a hand-span away is a sane start)? Is the mic pointed at them, not past them? What is the room adding — echo off bare walls, a humming fridge, traffic through a window? Move the fridge plug, hang a blanket, face the mic away from the window. Sixty seconds of listening to the room itself fixes problems no plugin can. The recording can never be better than what the microphone hears.
Decision 2: How hot am I recording?
Gain staging — Lesson 3, applied. Have them perform the loudest part for real. Set preamp gain so peaks land around −12 to −6 dB. Confirm the meter moves when they perform and sits near silence when they don't (if the meter dances while the room is quiet, you're recording noise — find it before the take, not after). Then hands off the gain knob.
Decision 3: How will we hear ourselves?
Monitoring. The artist needs to hear the beat and themselves in headphones — never open speakers, or the mic records the beat bleeding in and that bleed is welded into the vocal forever. Get their headphone balance right: enough beat to feel it, enough of their own voice to control pitch. And if there's an echo-like delay between singing and hearing (latency), fix it now — smaller buffer size, or your interface's direct-monitoring switch — because nobody performs well while hearing themselves half a second late. (Buffers and latency get their full treatment in Module 2.)
Source. Gain. Monitoring. Three decisions, thirty seconds, every time. Engineers who skip them re-record. Engineers who make them keep magic takes.
Reading builds understanding; drills build reflexes. Do all three this week. Each works in any DAW — Pro Tools Intro (free), Logic Pro's 90-day trial, GarageBand, or the LUMEN Studio for drill 3. If you have no microphone at all, your laptop's built-in mic is genuinely fine for drills 1 and 2 — we're training your eyes and ears, not making a record.
Teaches: reading meters, feeling what dB numbers mean.
You now know, in your hands, what every number on a meter feels like. Most people who've "used a DAW for years" have never done this once.
Teaches: recognizing clipping by ear and by eye, forever.
Teaches: pan, stereo image, and the mono check habit.
You can name the two units that describe all sound. You can trace a vocal from lungs to waveform and point at each link. You can set a recording level on purpose, leave real headroom, and explain — from experience, not from a rule — why clipping is forever. You can hear a stereo image and check it in mono. And you have a thirty-second pre-record ritual that working engineers twice your age still skip.
Next, Module 2: the session itself — sample rate, bit depth, buffer size, and I/O — where the choices you make before you record a single sound decide how smooth everything after will be.
— GetLife University