Matching reference tracks with a spectrum analyser
Producers in Brisbane bedrooms and Sydney warehouses reach for the same tool when they want their music to sit alongside the tracks they admire: a spectrum analyser. The visual it paints across your screen - frequency on the horizontal axis, amplitude on the vertical - becomes a map of how a finished record breathes. When you load a reference mix next to your own draft, the differences stop being abstract. You can see exactly where your low end rolls off too quickly, where the mids feel pinched, or where the top end loses the shimmer that makes a track feel expensive.
The trick is treating the analyser as a translator rather than a teacher. It won't tell you what to do, but it will show you the shape of what you're aiming for, and once you recognise that shape across enough genres you stop chasing random EQ moves and start sculpting with intention. The rest of this guide walks through how to read the visual, position the plugin in your signal chain, and translate what you see into specific EQ decisions for your own music.
What a spectrum analyser actually shows you
A spectrum analyser reads the audio passing through its input and splits it into frequency bins using a fast Fourier transform. The result is a real-time graph where each vertical slice represents how much energy exists at that frequency in a given moment. The horizontal axis spans roughly 20Hz to 20kHz, the range of human hearing. The vertical axis shows amplitude in decibels, usually on a logarithmic frequency scale so that octaves spread evenly across the screen and match how we actually perceive pitch.
Display style matters more than most producers realise. Bar graphs give you a punchy, moment-to-moment read of where energy is concentrated. Line graphs with averaging give you the broader tonal character of a track. For tonal matching you almost always want the averaged view, because that's what your ear remembers. A momentary peak at 4kHz from a snare hit isn't what gives a reference its tone - it's the average energy in that region across thirty seconds that matters. Most plugins offer both views, often toggleable with a single click.
In a Melbourne studio I visited last year, an engineer had two analysers open on the same screen - one set to peak hold for catching transients, the other averaging over six seconds to track long-term balance. The pairing is a useful habit because it lets you see both the punchy peaks that define a kick and the sustained energy that defines the overall vibe. You stop chasing ghosts in the analyser when you remember that you are looking at two different stories happening at once.
Setting up your visual workflow
Where you insert the analyser changes what you see. Placing it on the master bus after every processor means you are analysing the final shape of your mix, including the effect of any limiters, saturators, or stereo wideners you have added at the end. Placing it earlier, on a bus or individual track, gives you a read on the raw signal. For tonal matching against a reference, you typically want both - one analyser watching your master output and one watching the reference playback so you can compare them in real time.
Calibration is where most producers get lazy and pay for it later. The reference and your own track need to be playing back at matched loudness before you compare spectra, otherwise the louder signal will look bigger in every frequency region just because it is louder. Aim to match perceived loudness rather than peak level. A quick trick is to drop both files into a utility channel, invert the phase on one, and adjust until the combined signal is as quiet as possible. That gives you a real loudness match across the full bandwidth, not just the peaks. Once matched, the visual differences you see are actual tonal differences rather than volume artifacts.
A useful starting point is pulling a few loops or samples from a shared library like the community samples section and using them as quick references. Because loops are short and stylistically consistent, they are easier to analyse than full mixes - the spectrum stays predictable, which makes it easier to train your eye. Once you can read a simple loop's tonal shape on sight, full mixes become much easier to interpret because you already know what each region is supposed to feel like.
Reading the low end curve
The bottom third of the analyser screen, covering roughly 20Hz to 250Hz, is where most tonal mismatches show up first. Commercial mixes almost always have a controlled sub region below 40Hz with a gentle slope downward into the deepest frequencies, then a small lift in the 60-100Hz range to give kick and bass weight, then a smooth taper into the lower mids. When your own mix has a sharp drop below 50Hz or an uncontrolled bump at 200Hz that muddies everything above it, the analyser makes the problem visible immediately. You stop guessing and start measuring.
Sub bass is particularly tricky to read because monitors and headphones reproduce it differently. A pair of small nearfields in a Sydney home studio simply will not give you the same low-end impression as the subwoofer in a mastering suite, so the analyser becomes the only honest reference. If your analyser shows a strong peak at 35Hz and the reference is smooth down there, your sub is probably fighting your monitors instead of working with them. A high-pass filter just above the deepest note your bass plays is often the right move, but the analyser tells you exactly where to set it.
The 100-250Hz zone is where mud lives, and where Australian club music tends to behave differently from acoustic genres. A house or techno track playing through a system in Brisbane's Fortitude Valley can stack multiple bass layers in this region without sounding cloudy, while the same arrangement in a folk recording would feel boxy and congested. Knowing which genre reference you are comparing against matters here. The analyser does not care about genre, but your interpretation of what the visual is telling you has to account for the context.
Translating reference to your mix
Once you have a stable visual comparison, applying what you see is mostly subtractive EQ work. If your track has a 3dB lift at 250Hz compared to the reference, cut a touch at 250Hz. If it has a dip at 8kHz where the reference sparkles, add a gentle shelf above 7kHz. The movement is rarely large - one to three dB is the typical range for tonal matching - and broad strokes work better than narrow surgical moves. A wide Q boost at 4kHz mimics the energy of cymbals and vocal air, while a narrow cut at the same frequency only affects one tiny element.
Work from the bottom up. Lock in your low end first, then move to the lower mids, then upper mids and top end. The reason is simple: changes lower in the spectrum have a knock-on effect on everything above, so adjusting the sub first gives you a stable foundation. If you start tweaking the top end and then carve the lows, you will often find yourself redoing the high-frequency work you just finished. Three passes through the spectrum is usually enough: one for balance, one for fine tuning, one for sanity-checking against the reference.
Studying finished project files alongside analysis is a fast way to internalise the relationship between visual shape and EQ choices. The FL Studio projects archive lets you open other producers' sessions and see exactly where they placed their EQs, what curves they used, and how the analyser looked at various stages of the build. It is the kind of shortcut that would have taken an entire apprenticeship to learn fifteen years ago. Open a project, play it through the analyser, then open your own and play it the same way - the visual difference becomes a study guide.
Common pitfalls and how to avoid them
Loudness matching is the trap that catches almost everyone on their first attempt. A reference that plays back five decibels louder than your mix will look brighter, fuller, and more detailed in every region of the analyser, even when the actual tonal balance is identical. Always match perceived loudness first, either by ear against a familiar monitoring level or by using a meter to align integrated LUFS values. Once both signals are at the same perceived level, the spectrum comparison becomes meaningful.
Another common error is using the wrong reference entirely. A ballad reference will not tell you much about how to balance an electronic dance track, because the production priorities are completely different. Pick references that share the genre, tempo range, and instrumentation of your own project. If you are producing indie rock in Adelaide and your reference is a Nashville country mix, you will spend hours chasing differences that do not matter for your style. The analyser is honest about what is different, but it cannot tell you which differences are worth chasing.
Finally, do not let the visual override your ears. The analyser is a confirmation tool, not a decision-maker. If your mix sounds right to you on three different playback systems and the analyser still shows a discrepancy with the reference, trust your ears and ask why the reference sounds the way it does. Sometimes the reference itself has been pushed past taste in pursuit of loudness, and matching that would be the wrong move for your music. The visual is a starting point, not a destination.
Load a reference you trust into your DAW, route it alongside your current project, and write down three specific frequencies where the two spectra do not agree. Open an EQ on your master bus and make a single narrow move at the first frequency. Listen. Listen again. Then move on to the next one.