Audient iD24 Routing in Logic Pro: A Case Study Fix
The Client’s Challenge
It’s a scenario familiar to many producers: you’ve invested in a wonderful piece of outboard equipment—in this case, a coveted Hypnosis boutique reverb unit—and you’re eager to integrate it into your Logic Pro workflow. The process should be straightforward. You connect your hardware, set up an I/O utility in Logic, and assign the audio to a spare pair of outputs on your interface. Simple.
My client, however, had hit a wall. His Audient iD24 interface, a superb piece of engineering, was refusing to cooperate. While Logic Pro dutifully showed audio being sent to outputs 3 and 4, the physical outputs on the back of the unit remained stubbornly silent. The creative flow was broken, replaced by that sinking feeling of technical frustration. When a tool that’s meant to be transparent becomes an obstacle, it’s not just an inconvenience; it’s a direct challenge to the artistic process. The client had followed every logical step, yet the connection failed. This is precisely the kind of perplexing ‘edge case’ where the manual offers no comfort.
The Investigation
When the expected behaviour of a system fails, the first principle of diagnostics is to question your assumptions. My initial assumption was that, like most audio interfaces, the iD24’s software outputs would map directly to its physical hardware outputs. When this proved false, my investigation turned towards Audient’s own control software.
The Audient iD24, we discovered, doesn’t operate on a simple one-to-one basis. Instead, it places a powerful but initially invisible software mixer between your DAW and the physical world.
The Core Issue: A Hidden Routing Layer
Think of it like a telephone exchange. Logic Pro was dialling the correct number (Output 3-4), but an invisible operator at the Audient exchange needed to be told to physically connect that call to the corresponding line out. This extra layer provides tremendous flexibility for tasks like creating zero-latency headphone mixes for performers, but for a simple external effects loop, it’s an unexpected and undocumented hurdle.
Compounding the issue was a significant piece of UI ambiguity. The main control panel for the iD software shows routing options, but not the mixer itself. The key to unlocking the entire system—the ‘View Mixer’ command—was hidden away in a menu accessible only by clicking the small ‘iD’ logo in the macOS menu bar. This is not a user error; it’s a classic case of critical functionality being placed in a non-obvious location.
The Solution: Reconnecting the Lines
Once we’d uncovered the hidden mixer, the solution was a logical, multi-step process of explicitly telling the Audient software how to handle the audio from Logic Pro. Here is the precise workflow we followed.
Reveal the Hidden Mixer
With the Audient iD application running, navigate to the macOS menu bar at the top-right of your screen. Click on the ‘iD’ icon and, from the dropdown menu, select ‘View Mixer’. This will open the crucial software mixer window that was previously hidden.
Configure a Dedicated Cue Mix
In the mixer’s master section (top right), you’ll see options for ‘MAIN’, ‘CUE A’, and ‘CUE B’. Click on ‘CUE A’ to select it. Now, look at the mixer channels below. You need to send Logic’s specific output channels to this cue mix. Find the channels labelled ‘DAW 3-4’ and raise the fader to 0dB. Ensure all other channel faders in the CUE A mix are down.
Assign the Cue Mix to Physical Outputs
Go back to the main iD software window (not the mixer). In the ‘System Panel’ section, find the routing matrix for ‘Line Outputs 3-4’. Assign its source to ‘CUE A’. This is the final step in our virtual patchbay: connecting the CUE A mix bus to the physical jacks on the back of the interface.
Configure the Logic Pro I/O Plugin
In your Logic Pro session, place the ‘I/O’ plugin on the desired track. Set the ‘Output’ to ‘3-4’ to send signal to your effects unit, and set the ‘Input’ to whichever inputs your effects unit is returning to (e.g., ‘1-2’). The circuit is now complete, and you should hear your glorious hardware reverb in real-time.
Additional Reflections: Feature, Not a Fault
It is easy to become frustrated when technology behaves in an unexpected way, but it’s often valuable to understand the design philosophy behind the behaviour. The complexity of the Audient iD mixer is not a flaw; it’s a powerful feature designed for professional studio scenarios. The ability to create independent, low-latency cue mixes for artists without affecting the main control room mix is a cornerstone of professional recording workflows.
However, for the user in a smaller setup focused on mixing or integrating a single piece of outboard gear, this complexity can feel like a barrier. The problem was not the technology itself, but the ‘contextual conflict’ between a powerful, professional feature and a simpler, more direct user goal. The hidden nature of the mixer control exacerbated this, turning a configuration task into a forensic investigation. It serves as a potent reminder that the most elegant hardware can be let down by unintuitive software design, and validates the need for expert guidance to navigate these specific, high-level technical challenges.
If you are seeking professional help with this particular Audient iD24 external hardware routing issue in Logic Pro, one-on-one remote support services are available from Audio Support.
Not sure it’s the same problem? Ask a question first
