The Client’s Challenge
It’s a moment of pure studio frustration that every producer knows well. You have a new synthesizer, the cables are correctly plugged in, your DAW track is armed, but… silence. This was precisely the situation for a recent client using a MOTU UltraLite Mk5 audio interface with Logic Pro.
He was attempting to connect a hardware synthesizer to the rear line inputs, specifically inputs 3 and 4. In Logic Pro, he had created the corresponding audio tracks, but no signal was registering. The maddening part of the puzzle, and the clue that this was an unusual problem, was that he *could* get a signal on Logic’s channels 3 and 4, but only by plugging his synth into the combination microphone/guitar inputs on the *front* of the interface.
This kind of logical contradiction—where the physical connections don’t match the software’s behaviour—can be deeply confusing. It suggests the problem isn’t a broken cable or a faulty input, but something more subtle in the digital routing. The client had, quite rightly, reached the point where the equipment’s internal logic seemed to defy reality.
The Investigation: A Case of Mistaken Identity
My first suspicion was that this wasn’t a hardware fault. The fact that audio *could* be routed into Logic, albeit from the wrong physical sockets, pointed directly to a configuration conflict. The interface itself was working, but its internal map—the directory that tells the computer which physical socket corresponds to which software channel—had been scrambled.
The investigation began in the MOTU’s own control software, CUEMIX 5. This is the master control panel for the interface, and it’s where the fundamental routing rules are set, long before the signal ever reaches Logic Pro. After a careful review of the settings, the culprit came to light: a single, unassuming dropdown menu for the ‘Loopback’ feature.
Decoding ‘Loopback’
Think of Loopback as a virtual audio cable inside your computer. Its job is to ‘capture’ the sound being played by one application (like a YouTube video or system audio) and send it back into another application (like Logic Pro or OBS) as if it were a microphone or line input. It’s an essential tool for streamers and content creators. By default, this virtual input is usually assigned to high-numbered channels (like 9 and 10) to keep it out of the way of your physical microphone and line inputs.
In this case, the Loopback input had been assigned to channels 1 and 2. This seemingly small change had a significant domino effect. It effectively ‘reserved’ the first two input channels for this internal, virtual source. The MOTU interface, trying to make sense of this, shifted its entire input map. The physical inputs on the front, which should have been 1 and 2, were now being ignored by Logic, and the subsequent inputs were all misaligned. The rear input labelled ‘3’ was no longer talking to Logic’s ‘Input 3’.
The Fix: Restoring the Digital Order
The solution was to return the Loopback setting to its default state, which instantly restored the logical connection between the physical inputs and their corresponding channels in the DAW. It was a simple fix, but one that was hidden deep within the interface’s configuration.
Close Logic Pro to ensure the audio driver can be reset without conflict.
Open the CUEMIX 5 application, the dedicated control software for the MOTU UltraLite Mk5.
Navigate to the Device tab to access the main hardware configuration settings.
Locate the ‘Loopback’ dropdown menu. In our client’s case, this was set to ‘Mix 1-2’.
Change the setting back to the default, which is ‘Loopback 9-10’. This frees up channels 1 and 2 to function as standard physical inputs again.
Relaunch Logic Pro. The physical inputs on the MOTU interface will now correctly align with the software inputs in your DAW.
Additional Reflections
The Ghost in the Machine
It’s important to state that this was not a user error. We never discovered precisely why the setting was changed from its default; it could have been an accidental click, a consequence of a software update, or a conflict with another piece of audio software. Modern device controllers are immensely powerful, but their user interfaces can be dense and complex. It’s easy for a single setting in an obscure menu to have wide-ranging, unpredictable consequences.
This case highlights a core principle of our diagnostic work: always validate the fundamentals. Before you start questioning your DAW, your cables, or your sanity, it’s crucial to confirm that the hardware’s own internal configuration is set to its expected, default state. It’s often there, in the quiet background settings, that the most baffling problems hide.
If you are seeking professional help with a MOTU UltraLite Mk5 experiencing input routing errors in Logic Pro, where physical inputs do not match the software channels, a misconfigured Loopback setting is a likely cause. For expert diagnosis of these and other complex audio architecture conflicts, one-on-one remote support services are available from Audio Support.
Not sure it’s the same problem? Ask a question first
