You open a new effect, choose a preset and the track immediately sounds more expensive. Before announcing a breakthrough, turn it down a little. If the improvement disappears, you have discovered a volume control. Those are useful too.
Give the comparison a job
Write down what you want to change before adding the plugin. “The vocal gets lost in the chorus” is useful. “Make it professional” leaves you auditioning indefinitely. Choose a passage where the problem happens and include a few seconds before and after it.
Keep the original available. Save a new project version or duplicate the processing chain, making sure you hear only one version at a time. Playing both together tests their combined sound, not which one works better.
Match the level after the effect
Set the effect for the change you want, then adjust its output to bring the processed and bypassed versions close in perceived volume. Use a meter to help, but listen across the complete phrase. Matching one peak does not ensure the sustained parts feel equally loud.
Use the output trim for this comparison. Reducing the input can change how a compressor or other level-dependent processor behaves. FabFilter documents this distinction in its input and output controls: input adjustment precedes processing, while output adjustment changes the final level.
Check any automatic gain feature rather than assuming it has made the decision for you. The Pro-C documentation, for example, explains that its automatic make-up gain is an estimate, not a loudness measurement. That does not make it useless. It means your ears are still employed.
Run a short comparison
- Listen to the original. Identify one detail: the consonants, the kick attack, a harsh note or the space behind a phrase.
- Switch to the processed version. Ask whether that detail improved, and what changed elsewhere.
- Return to the whole mix. A beautiful solo sound can take up space that another part needs.
- Try a smaller amount. Compare the chosen setting with a restrained version before committing.
- Close the window. Listen once without watching the controls or meter animation.
Change one important control at a time. If you adjust drive, tone, stereo width and output together, you may like the result, but you will not know what caused it. Save the useful version before continuing.
Decide what stays
Keep processing that solves the original problem without creating a worse one. If the two versions seem equally useful, choose the simpler chain or leave the original. You do not have to justify the plugin's existence in every session.
For an EQ and compressor comparison, read how the order changes the result. If the processing feels late rather than different, check plugin latency and buffer size before judging its tone.
Common questions
Should I match peak level or loudness?
Use perceived level across the same passage as your main comparison. Peak readings help catch clipping, but two sounds with matching peaks can still feel very different in volume.
Does bypass always make a fair comparison?
Check the plugin's manual when it adds latency or has its own bypass control. Start playback before the comparison passage and allow effects with tails to settle. A click or a timing jump is not a tonal improvement.
