Two years. That’s how long the Console 1 has been sitting on the desk, and I can tell you exactly where the romance dies. It’s not the fader. That fader is fine. It’s the point, at some interval or other, where something in the software layer decides it doesn’t want to talk to the hardware anymore and you spend an evening unplugging a USB cable instead of finishing the mix.
So this isn’t a review. It’s a reckoning. What the Console 1 actually earns its keep on, and what still makes me reach for the mouse.
The fader, the knobs, and why the hardware survives
Let’s get the obvious out of the way: the tactile argument holds up. After two years I still adjust gain on the desk itself without thinking. My eyes stay on the speakers. The pitch is the product, and that pitch holds up.
The knobs are where the design actually shows its age versus newer gear. They aren’t touch-sensitive in the way some of the newer control surfaces push, but the mapping is deep enough that muscle memory takes over for the compressor and EQ sections quickly. What frustrates me is the way some functions still want a double-press or a shift combo. Do that on a session at 2 AM and you’ll curse. Other manufacturers have shown you can just write the function on the surface in tight spaces instead of hiding it behind a symbol. I wish Softube had taken that lesson.
The fader itself has held up mechanically. No scratchiness, no drift on automation so far. That’s the one part of the package I have zero complaints about.
Where the plugin layer saves the unit
The reason Console 1 keeps its spot is not the hardware, it’s the channel strip behind it. And the single biggest shift in two years of use is that the Softube Tape module earned a permanent place in my master chain, not just my mix chains.
The Tape plugin does what good tape emulation should: subtle harmonic distortion and gentle compression, and it cleans up the low end. On a master I keep the saturation low (tape type B does the job without plastering the mix) and push the speed to 30 inches per second when I want a cleaner top and slightly attenuated lows. That combination just worked better on the mixes I was finishing. In the crosstalk section, a touch of boost does something useful: it nudges the two channels slightly out of step, which fans the mix outward toward the speakers. It’s a small, cheap width trick that doesn’t sound like a width trick.
Whether that matters depends on how you set up the rest of the chain. The way it sits in the typical mastering order matters: subtractive EQ first, then de-essing and high-end control, then saturation, then the tape stage, then loudness enhancement, then additive EQ. Softube Tape lands around the fourth insert in the chains I trust. Once you hear the console’s emulated saturation in that spot, the hardware starts to feel less like a gimmick and more like a shortcut to the plugin you’d have reached for anyway.
The driver problem nobody warns you about
Here’s the unglamorous part, and the part that actually matters for anyone running this on a Windows box.
The Console 1 lives or dies on its software layer. When it works, it’s invisible. When it doesn’t, you get the classic cascade: the hardware stops responding mid-session, then the plugin host complains about the device, then you’re reinstalling the Console 1 software and the driver bundle and hoping the firmware doesn’t need a separate flash. I’ve had one Windows audio session killed outright by a driver update that silently changed how the unit was enumerated. Reboot, replug, reinstall, and the fader came back like nothing happened.
A few things I now do as routine:
- Pin the driver version once a build is stable. Don’t take a “minor” update mid-project. The upside is rarely worth the risk.
- Don’t stack audio driver updates on the same day you touch the ASIO buffer or your interface firmware. One change at a time, always.
- Keep a known-good installer for the Console 1 software and its driver bundle on a separate drive. Not in Downloads. Downloads lie.
- Watch the enumeration order. If your audio interface is set as the primary device, the Console 1 wants to sit behind it, and the order they come up at boot matters more than it should.
None of this is unique to Softube. It’s the same software-underneath-the-studio tax we all pay. But the Console 1 raises the stakes because the hardware is useless without the software, so every driver hiccup costs you the whole point of the purchase.
What it does not do
Two years in, I want to be honest about the edges. Console 1 is not a DAW controller in the general sense. It won’t give you fader-bank control over every track in a big session the way a dedicated surface will. It’s a channel strip controller, and it wants you to work within that idea. If your workflow is “scroll through forty tracks and touch each one,” you’ll fight it.
It also won’t fix a bad monitoring chain. If your interface drivers and buffer settings are already a mess, the Console 1 just adds another device to the pile. Get the ASIO side sorted first. That’s the layer that actually decides whether you can track with it at low latency.
Would I buy it again
Yes, though the reason would be the tone, not the rotary controls. The shortlist of reasons I keep it: the Tape module doing real harmonic work on masters, a fader that hasn’t drifted, and a mental shortcut that gets me to decisions faster. The shortlist of annoyances: driver updates that require a ritual, shift-combos I still fumble, and a software layer that needs babysitting on Windows.
If you run a lean setup and you have your driver routine nailed down, the Console 1 rewards you. If your studio PC is the kind of machine where you install an update because it popped up in a notification, this unit will teach you patience the hard way.
Buy it for the sound. Then treat the software like studio infrastructure, because that’s what it is.