The Console Workflow: Why Processing Every Track Beats Fixing the Bus
Here is a question that reveals a lot about how records are made: why do mixes made on classic analog consoles sound so cohesive and expensive, even before anyone touches the mix bus? The answer is a workflow principle that most in-the-box producers get backwards, and understanding it can transform how your mixes sound.
How consoles actually worked
On a large-format analog console, every single channel the audio passed through added a little something. Each channel strip had its own preamp, its own EQ, its own line amp, its own transformers. None of it was perfectly transparent. Every channel imparted a tiny bit of harmonic coloration, a touch of saturation, a subtle character.
Multiply that across forty or sixty channels, all summed together, and the cumulative effect was enormous. The console was not adding a lot of color anywhere in particular. It was adding a little everywhere, and the sum of all those small colorations was the rich, cohesive, glued sound that defined records made on those desks. The magic was distributed across every track, not concentrated in one place.
What in-the-box producers do instead
When we moved into the DAW, we got clean, transparent summing, which is technically superior in that it adds nothing unwanted. But we lost the distributed coloration that made consoles sound the way they did. And most producers, trying to get that sound back, do the opposite of what the console did.
They leave every channel clean and then slam a single processor on the mix bus, one big saturator, one big compressor, trying to add all the character in one place at the end. And it does not sound the same, because concentrating all the processing on the summed mix is fundamentally different from distributing a little across every source.
When you saturate the sum, all the sources interact and intermodulate with each other through the same nonlinear process, which can create mud and harshness. When you saturate each source a little on its own, each one is colored independently and cleanly, and the sum of those independently colored tracks is far closer to the console sound: cohesive, rich, and natural, without the intermodulation of smashing the whole mix at once.
Why a little on every track wins
There are concrete reasons the distributed approach sounds better.
It is gentler per instance, so no single processor is working hard enough to introduce obvious artifacts. A tiny bit of saturation on each of thirty tracks is inaudible as an effect on any one track, but the sum is unmistakable.
It avoids intermodulation. Processing sources separately means their harmonics are generated independently, rather than a single nonlinear stage generating intermodulation products between the kick, the vocal, and everything else at once.
It is how the references were made. The records you are chasing were often made this way, so matching the workflow gets you closer to the sound than any single-plugin shortcut.
The catch, and the reason most people do not do it, is management. Putting a processor on every one of forty channels and then adjusting them all is a nightmare. Change your mind about the amount of saturation and you are opening forty plugins one at a time. This is exactly the friction that stops people from working the way consoles worked.
The fix: Console Remote
Several Process.Audio plugins, including Spicerack and Rockruepel COMP.TWO, include a feature called Console Remote, which solves the management problem directly. It links every instance of the plugin across your session into a single control window. You can put the plugin on every channel, adding a little distortion, saturation, or compression to each, and then control them all from one place.
With Spicerack, that means a touch of the same distortion character on every track for cohesive, console-style harmonic color, adjustable globally without opening forty windows. With COMP.TWO, it means managing tube compression across many channels at once, so you can dial the whole session's glue from one place rather than nudging each instance separately.
This brings the console workflow into the box without the misery that normally kills it. You get the distributed, everywhere-a-little coloration that made analog desks sound cohesive, with the recall and convenience of software.
Step by step: work like a console
- Choose the character you want to distribute, harmonic saturation with Spicerack, or gentle glue compression with COMP.TWO.
- Put an instance on every relevant channel, or on your subgroups if forty is too many to start.
- Set a small amount on each, so subtle it is barely audible on any single track. You are seasoning, not cooking.
- Use Console Remote to audition and adjust all instances together. Bring the whole session's coloration up and down as one gesture and find the sweet spot.
- A/B the whole mix against bypassing all instances. The distributed coloration should make the mix sound more cohesive, richer, and more finished, without any single track sounding processed.
FAQ
Why do mixes made on analog consoles sound so cohesive? Because every channel on a console added a little harmonic coloration through its preamp, EQ, and transformers. Across dozens of channels, those small colorations summed into a rich, glued sound. The character was distributed across every track rather than concentrated in one processor.
Is it better to process every track or just the mix bus? Distributing a little processing across every track often sounds more natural and cohesive than concentrating it on the bus, because each source is colored independently and cleanly, avoiding the intermodulation and mud that can come from saturating the whole summed mix at once. It mirrors how console records were made.
Why does saturating the whole mix bus sound muddy? Because a single nonlinear stage on the summed mix generates intermodulation between all the sources at once, kick harmonics colliding with vocal harmonics and everything else, which can produce mud and harshness. Saturating each source separately generates their harmonics independently, avoiding that intermodulation.
How do I manage processing on every track without it being a nightmare? Use a plugin with a console-style remote that links all instances into one control window, so you can add a little processing to every channel and adjust them all together. Process.Audio's Console Remote in Spicerack and COMP.TWO is built for this distributed workflow.
Bring the console into your DAW
Stop slamming the bus and start coloring every track a little. Try Spicerack and Rockruepel COMP.TWO with Console Remote and mix the way the classic records were made.
Explore the free trials. No credit card required.