Article Type: Review

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.

The update landed on a Tuesday, and by Tuesday night my interface was gone. Not dead, exactly. Device Manager said it was there. The DAW disagreed. No inputs, no outputs, and a driver panel that opened to an empty window. If you are reading this after a 24H2 update flattened your rig, you already know the feeling. Here is the order I worked through before I touched the rollback button, and what actually fixed it.

First: stop trusting Device Manager alone

Device Manager is a liar with a clean conscience. It will happily show your interface sitting there, named and undrivered, and call the situation fine. What matters is whether the audio service can see it.

Open Sound Settings and check the input and output device lists, not the control panel. If your interface vanished from those lists while showing up in Device Manager, the driver did not load against the current build. That is a driver-side problem, not a hardware failure. Your preamps and converters are almost certainly fine. The software handshake is what broke.

This is the first thing to establish, because it decides everything downstream. A device that has dropped off the audio stack can usually be recovered. A device that has dropped off the USB bus entirely is a different investigation.

Check the connection before you blame the OS

USB-C and Thunderbolt interfaces are compact and reversible, which is nice, but they are also fussy about what they are plugged into. The connection has to sustain low latency and high sample rates on a stable driver, and a flaky port or a tired hub will sabotage that even on a healthy Windows build.

So before any deeper surgery:

• Move the interface to a different USB port, ideally one on the motherboard rather than a hub.
• Swap the cable if you have a spare. Cheap USB-C cables fail quietly.
• Unplug every other USB device you do not strictly need, then reconnect the interface alone.
• If your interface is bus-powered, try a powered hub or its own supply if it has one.

If the device reappears in the audio stack after this, you never had a 24H2 bug. You had a port or a hub problem that happened to show up the same week. Frustrating, but cheap to fix.

The driver reinstall, done properly

A plain reinstall usually does nothing, because Windows keeps the broken driver package and just reinstalls the same mess. You need to remove it first, and removal means more than clicking uninstall in the driver panel.

What works, in order:

• Uninstall the interface driver through its own uninstaller, not just Device Manager.
• Open Device Manager, tick Show hidden devices, and delete any greyed-out entries for your interface under Audio inputs and outputs and under Sound, video and game controllers.
• Reboot with the interface unplugged.
• Install the latest driver from the manufacturer, pulled fresh rather than from your downloads folder, since 24H2 may need a newer build than the one you had.
• Plug the interface back in only when the installer asks for it.

Drivers are the whole game here. A good audio interface lives or dies on well-maintained drivers that keep working across OS updates, and a major Windows feature update is exactly the moment those drivers get stress-tested. If the manufacturer has not shipped a 24H2-ready build yet, no amount of reinstalling will help. Check their support page for a known-issues note before you spend an evening on it.

ASIO and the sample rate trap

Here is one that catches people who did everything right. The driver installs, the device shows up, audio plays, and then your DAW refuses to open the interface at all. Look at the sample rate.

Windows and your DAW can end up requesting different rates from the same device. If the Windows sound settings are pinned to one rate and your project is set to another, the ASIO driver may hand exclusive control to whichever asked first, and the other one gets nothing. Set both to the same value, typically 24-bit / 48kHz for most tracking and mixing work, and see if the conflict clears.

Higher rates are useful for sound design and classical recording, but they are rarely necessary for everyday production, and they multiply the chances of a mismatch after an update resets your audio settings. Start conservative. Get the device talking. Raise the rate later once things are stable.

The obvious fix nobody tries: roll back the update

You can roll back a feature update within a limited window after it installs. Settings, Windows Update, Update history, then Uninstall updates. If 24H2 is listed there and your rig is dead in the water, this gets you working again in minutes and buys you time to solve it properly.

Do it as a stopgap, not a lifestyle. The rollback window closes, and you will face the update again. Use the breathing room to check whether your interface maker has published a fixed driver. If they have, install it and re-take the update. If they have not, you now know exactly which vendor is dragging its feet.

A cheap insurance policy: image your system drive before any major Windows update. It turns a ruined session into a twenty-minute restore. I learned this the hard way, and I now do it every time Microsoft pushes a feature update.

When it is genuinely not your interface

Sometimes the device is fine and the rest of the chain is the problem. If your interface works but your DAW still stutters, watch your CPU and buffer settings. A 24H2 update can shuffle background services and power plans, and a power plan that throttles USB or the CPU mid-session will produce dropouts that look like a driver fault.

Set the power plan to high performance, disable USB selective suspend, and raise your buffer size one notch to see if the crackle disappears. If it does, you were chasing a latency and scheduling problem, not a dead interface. Nothing about your converters or preamps changed. The machine just got greedier about power management.

What I actually did

For the record: a clean driver removal, a fresh vendor build published two weeks after 24H2, and a matched 48kHz setting across Windows and the DAW. That was it. The interface came back and has been solid since. The rollback was never needed, but I kept it on the table until the new driver proved itself over a full tracking day.

If your device is still missing after all of this, stop reinstalling and start reading your manufacturer’s support page like it owes you money. The answer is usually there, in a changelog nobody reads, dated after the update that broke you.

Two in the morning is the only honest time to cut a master. The room is quiet, the phone has stopped, and you can finally hear what the mix actually is instead of what you hoped it would be.

I spent years doing this on WIR Records. Not as a mastering engineer with a plate on the door and a Buchla in the corner, but as the label hand who ended up with the last stage because nobody else wanted to sit there at 2 AM arguing with a LinnDrum that keeps poking through a vocal. What follows is the unglamorous stuff. The processing order I stopped fighting, the software that broke on me, and the things about mastering I wish someone had said flat out instead of dressing up as a framework you can steal.

Mastering with intention, not with a preset list

You can memorize a hundred plugin chains and still ruin a track. A mastering chain is a set of decisions, not a shopping list. According to the framework laid out at mastering.com, the whole job comes down to three goals: make the track louder, make it sound better, make it translate across systems. Everything on the bus should serve one of those three. If it doesn’t, cut the plugin loose.

That framing saved me more wasted nights than any specific tool. At 2 AM your ears are tired and the temptation is to add, add, add. The three rules push back. Why is this EQ move here? Which of the three goals does this limiter earn? Most of my worst masters were the ones where I broke those rules and processed because I could.

The chain I actually landed on

Order matters less than purpose, but I keep coming back to a sequence that mirrors what mastering.com calls intent-driven processing. Cleaning EQ first, then glueing compression, then the limiter stage, with treatment in between that I’ll get to.

Cleaning EQ before anything else

The first EQ is not for tone. It’s for removing what shouldn’t be there. Broad Qs, small moves, transparent plugin. If the high mids bite, pull them back a little. If the sub is heavy in one spot, shave it. This is maintenance, not art. Get it wrong and everything downstream magnifies the mess.

I keep a de-esser in reserve for this stage too. When the Ss poke or the cymbals get glassy, a dedicated de-esser reacts to peaks that a static EQ can’t. But keep it subtle. You’re working on the whole file, and one over-eager de-ess can dull a top end that took the artist three days to get right.

Glue before color

A glueing compressor is what separates a mastered track from a pile of stems that happen to be in key. The telltale sign of an unmastered mix is a lack of glue, the mastering.com guide nails that. I run a slow, gentle setting, maybe 1 to 2 dB of movement, just enough to make the low end and the vocal breathe together. Makeup gain handled by the plugin itself gives me a fuller result than pushing the output manually.

You do not need two compressors. The guide is honest about this: there are no hard rules, and two only makes sense if you’re splitting clean glue from a colored one. I usually split them anyway because I like a clean glue stage and a separate color stage, but I’ve cut plenty of records with one good compressor doing both jobs.

Clipping, stacking limiters and the loudness lie

Here’s the thing nobody told me until I’d already learned it the hard way. Slamming a single limiter is not how you get loud without damage.

A studio-floor tip from a Studio One forum thread that stuck with me: shave 2 to 4 dB of transients with a clipper before the limiter, then let the limiter push the level. The poster’s point was that taking the clipper out and compensating with the limiter gets you pumping or distortion. I’ve heard that exact difference on my own bus more times than I care to count. The clipper takes the peaks the limiter would otherwise fight, so the limiter works less and sounds cleaner.

The forum also suggests stacking two limiters to reduce the load on each. I resisted that for years because it felt like a hack. It isn’t. Splitting the same amount of gain reduction across two stages keeps each one out of its worst range, and you get the timbre of both units. The sageaudio chain agrees, using a FabFilter Pro L2 on its modern setting for the clean final catch. That L2 is transparent enough that I stopped arguing with the second limiter and just left it in.

The loudness war is over in the sense that the streaming platforms are fighting back. The mastering.com guide says it plainly: you can no longer just throw a limiter on and shove the output as hot as it will take. For WIR, the target was never maximum LUFS. It was the point where the track stopped getting better and started getting louder. That point arrives earlier than your ego wants.

The color stage I kept coming back to

Saturation at 2 AM is a mood, not a spec. I used a tube stage for fill, particularly when a mix had a gap in the mid range that EQ couldn’t fix without carving. The Saturn 2 tube setting is what I reached for on the masters that needed body, and the sageaudio chain confirms the choice: the tube algorithm fills in the spectrum with harmonic distortion and compression that feels natural on a full mix. Splitting it into three bands gives control over which range takes the color, though the modulation and filters stay on the middle band and don’t follow to the new low and high bands. That’s a limitation, not a bug, and it suits mid-range work anyway.

The linear phase option is worth the extra CPU if you’re on a deadline that has minutes to spare. It keeps the distortion out of the artifacts. And if a master’s highs were harsh but I still wanted them present, a warm tape saturator at 30 ips was my fallback. The faster speed keeps the sound clean and pulls the lows down a touch, which is exactly the trade I wanted on thin pop masters.

Stereo, phase and the wide-but-wrong trap

Widening the master is one of the most tempting moves and one of the easiest to get wrong. The mastering.com chain warns that most stereo expanders use the Haas effect, and pushing them too far creates phase issues. I’ve heard records that sound enormous on headphones and collapse to nothing on a mono club system. That collapse is phase cancellation, and it comes from a wide move that felt good at 2 AM.

My rule: check mono before you commit. If the track loses anything important, back the width off. A great mix will already be wide. Your job is to protect it, not to re-imagine it.

The software layer nobody writes about

WIR ran on borrowed time and old drivers. Half the 2 AM sessions weren’t about the chain at all. They were about a plugin that loaded but didn’t pass audio until the ASIO buffer was reconciled, or an interface that needed a driver version pinned to a specific firmware before the meters behaved. If your audio interface drivers are out of step, no amount of Pro L2 top-end will save the session. The software layer underneath is where masters die.

My suggestion, born of too many failed print attempts: before you build a chain, verify the boring stuff. Confirm the driver version matches the interface firmware. Set the buffer where you actually want it and check the latency reading, not just the slider. Then leave the machine alone. Half the instability I chased was caused by tweaking a working system at 1 AM because I couldn’t hear the difference I wanted and blamed the platform. It was never the platform.

What I’d tell the next person in the chair

Know why you’re processing before you process. Use the three goals. Clean before you color, glue before you compress for color, clip before you limit, and stack limiters rather than asking one to do everything. Check mono. Leave the drivers alone once they work.

And print the mix that sounds right, not the one that hits the loudness target you set at midnight. The 2 AM ear lies about loudness. Trust the version you’d play for a friend the next morning, when the room is bright and the coffee is fresh. That’s the master.