When to Use Plugin Presets and When to Build Your Own Sounds From Scratch
By Written by Peter McVeigh
You loaded a CLA preset on your kick drum and wondered why it sounded nothing like the reference. Here is why: the preset was built on a different kick, in a different room, with a different mic, played by a different drummer. Presets are not plug-and-play solutions. They are, at best, a starting point for people who already understand what they are looking at. This article will tell you exactly when presets are useful, when they are actively holding you back, and what it actually takes to develop a sound that belongs to you. =
The Problem With EQ Presets Is That Your Kick Drum Is Not Their Kick Drum
Load a stock EQ preset labelled "kick drum" and you are applying someone else's solution to someone else's problem. The engineer who built that preset was working with a specific drum. Probably a 22-inch kick with a single-ply batter head and a felt beater, mic'd up about three inches inside the port hole. If your kick is a 24-inch shell with a double-ply Remo Powerstroke and a wood beater, mic'd at the front head, the two signals share almost nothing in common beyond the label "kick drum."
The fundamental resonant frequency of a 22-inch kick typically sits somewhere between 50 and 80Hz. A 24-inch shell will push that lower, often into the 40 to 60Hz range. A 26-inch kicks even further down. Apply a preset built to cut at 60Hz and boost at 100Hz to the wrong kick, and you are not treating the drum in front of you. You are applying a solution to a ghost.
This is why EQ presets are only genuinely useful if you already understand what an EQ does. The visual shape of a preset, the curve on the graph, can be instructive. It tells you roughly what a working engineer thought needed cutting or boosting on a similar source. That is valuable as a learning tool. It is not valuable as a production shortcut.
Do this: before you load any EQ preset on a source, identify the three most prominent frequency problems in that source by ear first. Sweep a narrow band, find the honk, the mud, the harshness. Then load the preset and compare what it does against what you already identified. If it is not addressing the same problem, it is not your preset.
An EQ preset is a map of someone else's room. You are standing in a completely different one.
Compression Presets Are Slightly More Forgiving, But Only Once You've Found Your Threshold
Compression is less source-specific than EQ, but only to a degree. The ratio, attack, and release settings on a well-built preset can translate reasonably well across similar sources, because the dynamic behaviour of, say, a snare hit follows a recognisable shape regardless of what snare you are using. That is the one area where presets hold up better.
The threshold, however, is completely useless as a preset value. It does not transfer. The threshold is set relative to the input level of your specific signal, and that signal will be hitting the plugin at a completely different level to whatever session the preset was built in. A threshold at -18dBFS in one session might be catching almost every transient. In your session, it might not be touching the signal at all, or it might be absolutely crushing it.
This means every compression preset you load requires you to reset the threshold manually before any of the other settings mean anything. Find the point where the gain reduction meter is doing something musical, something that corresponds to what you want the compression to actually achieve, and then assess whether the attack and release settings feel right for your source. Only then does the preset become a useful reference point.
The broader issue is that compression requires you to listen to what it is doing over time, not just look at the settings. A preset gives you numbers. Numbers without ears are just numbers. If you are relying on a preset because you find compression confusing, the honest answer is not to load more presets. The honest answer is to spend a week putting a compressor across a drum loop with the ratio at 4:1 and moving nothing but the attack, and listen to what changes. That one exercise will teach you more than any preset library ever will.
Delay Presets Are a Different Story Entirely
Delays are the one area where a well-designed preset can be genuinely creative without requiring significant adjustment. The reason is that delay is a compositional effect as much as it is a corrective one. When someone builds a preset for a tape slap delay at 127ms with 35% feedback and a slight high-frequency roll-off on the repeats, that preset is encoding a musical idea, not a solution to a specific technical problem. Musical ideas translate.
That is not to say you can drop a delay preset on a vocal and walk away. You cannot. The delay time still needs to be tempo-synced to your session, the mix level needs to sit correctly in the context of your arrangement, and in most cases you will want to EQ the return channel so the delays do not compete with the dry signal. A delay preset gives you a character to work with. Placing that character in a song is still your job.
Where delay presets genuinely shine is in sparking ideas you would not have arrived at through methodical programming. Setting a ping-pong delay by hand with precise mathematical values is fine. Loading a preset that someone built to sound like it was recorded through a spring reverb unit and then taped over twice gives you something odd and specific that you would probably never have dialled in from a blank slate. That is a legitimate use of a preset.
The practical distinction is this: use delay presets as creative starting points, use EQ and compression presets as educational references, and be clear in your own process about which mode you are in at any given moment. Confusing the two is where people go wrong.
If Everyone Uses the Same Presets, Everything Starts to Sound Like the Same Record
There is a reason a large proportion of modern commercial records share a recognisable sonic texture. Part of that is genre convention. A significant part of it is that a relatively small number of widely distributed plugin bundles, Waves, FabFilter, iZotope, UAD, come loaded with presets built by a small group of well-known engineers, and those presets are being applied, largely unmodified, across hundreds of thousands of sessions.
Knowing the rules is necessary. Understanding why a high-pass filter at 80Hz on a guitar track keeps the low end clean, or why a slow attack on a compressor lets the transient through before the gain reduction kicks in, gives you a vocabulary. But the engineers who built the sounds people actually remember were the ones who then broke those rules with intention.
Nigel Godrich recorded the string arrangements for Travis's "The Slideshow" in the back of a moving car, using the acoustic properties of the vehicle's interior as the reverb environment. The result is a texture that no reverb plugin preset will ever reproduce, because it did not come from a plugin. It came from a decision to use an implausible space and commit to it. Similarly, Trent Reznor and Atticus Ross have spoken about recording through broken equipment, tape machines running at wrong speeds, and microphones placed in rooms nobody would describe as suitable for recording. The Beastie Boys built a significant portion of their sonic identity around a cheap Casio sampling keyboard that professional engineers of the time would have dismissed entirely.
Developing your own sound means making decisions that cannot be encoded in a preset. It means understanding the tools well enough to misuse them on purpose. Start by identifying one deliberate rule-break per session and document what it produces. Over six months, that log becomes a methodology.
Working With a Producer Who Has a Sound Means Understanding Why Their Presets Won't Save You
If you are an artist who has decided to work with a producer specifically because of their sonic signature, you need to understand what you are actually signing up for. That producer's sound is not in their plugin folder. It is in thirty years of decisions about what to reach for and when, what to leave alone, and which happy accidents to keep rather than undo.
A producer's preset library is, at best, a trail of breadcrumbs leading back to decisions that made sense in specific contexts. When Rick Rubin strips a record back to almost nothing, that is not a setting on a compressor. It is a philosophy about where tension lives in music. When Brian Eno generates an approach using oblique strategies and accident, that is not replicated by loading his name in a reverb plugin.
This matters practically for artists who are self-producing. If you are drawn to a particular producer's output, the useful exercise is not to find out what plugins they use. The useful exercise is to identify the three or four consistent decisions they make at arrangement level: how much space they leave, where the low end sits relative to the midrange, how much room sound is present on the drums. Those are learnable. Those are things you can build towards with your own tools, your own room, and your own judgment. A preset with a famous name on it is a logo. It is not a process.
Your Room Is the One Variable No Preset Can Fix
For anyone recording at home, the single largest factor affecting the sound of your recordings is not your plugin selection. It is your room. An untreated domestic room will typically have standing waves in the 80 to 200Hz range that cause certain bass frequencies to pile up or disappear depending on where you are standing. It will have early reflections from parallel walls that smear the stereo image and make precise EQ decisions almost impossible, because what you are hearing is not what is on the recording.
No EQ preset corrects for a room problem, because the preset cannot hear your room. What it can do is compound the problem. If your room is making the kick drum sound thin at 80Hz because of a room null at that frequency, and you load a preset that boosts 80Hz to compensate for what you are hearing, you are not fixing the kick. You are adding boost that will translate as excessive bass on any system that is not afflicted by the same null.
The productive approach is to accept your room's character rather than fight it. Learn where the bass piles up. Learn where the reflections arrive. Make those factors part of your workflow rather than anomalies you try to compensate for with processing. Many significant records were made in rooms that a studio designer would have condemned. The Beatles recorded at Abbey Road in rooms that would not meet modern acoustic standards. Bon Iver's "For Emma, Forever Ago" was tracked in a hunting cabin in Wisconsin with no acoustic treatment at all.
Do this: before you apply any processing to a mix element, listen to it on at least two different playback systems. Earphones, a Bluetooth speaker in another room, your car. The differences between those playback environments will tell you far more about what is actually happening in your recording than any meter or preset ever could.
A Famous Name on a Preset Means Nothing If You Don't Know What You're Looking At
The marketing logic behind signature presets is straightforward. Attach a name that engineers respect to a plugin setting, and buyers will believe that loading it brings them closer to that engineer's output. CLA. Andrew Scheps. Tony Maserati. These are serious, accomplished engineers whose work spans some of the most commercially and critically significant records of the last thirty years. Their names on a preset mean something about their work. They mean nothing about yours.
If you do not understand what a compressor's knee setting does to the character of gain reduction, loading an Andrew Scheps preset is not going to produce an Andrew Scheps result. It is going to produce a signal that has been processed by settings you do not understand, applied to a source he never heard, in a room he has never been in. The plugin cannot bridge that gap. Only your understanding can.
That said, presets do have a legitimate and specific use that is worth naming clearly. The YouTube video embedded below is a precise illustration of the point. Press the preset & make a song. David Albarn found something to work from to create a track, he used a pre set on the omnichord and made a full scale hit with it. But the difference is he worked from the preset & added himself and his sound on top of it.
[https://www.youtube.com/watch?v=RILRBOK5THg]
Presets are a vocabulary, not a voice. The voice is yours to develop, and no library of named settings will do that work for you. Load the preset. Understand every parameter it has changed. Then ask whether those changes are actually serving your source. That question, repeated across enough sessions, is how you develop a sound. There is no faster route.