Just Because You Can Doesn’t Mean You Should: Cable Choices and Signal Reality
One of the recurring challenges my students face when setting up their studios has nothing to do with microphones, plugins, or synths—it’s cables.
There are so many types, formats, levels, adapters, and “almost works” solutions that it’s easy to feel overwhelmed. This post is not about listing cable types or explaining what each one does. That would be a very long post.
Instead, this is about something a little more subtle:
Just because a connection works, does that mean it’s a good idea?
I should say upfront: if you’re looking for clear, final answers, this post may not help. In fact, it may create more questions. And that’s kind of the point.
When “It Works” Isn’t the Same as “It’s Right”
While planning my monitoring setup, I ran into an issue I hadn’t really thought about before—not cable types, but signal levels.
My goal was simple:
I wanted my Mackie Big Knob monitor controller to feed two destinations:
- one output going to my studio monitors
- another output going to a headphone amplifier
I wired it up, turned it on, listened—and it sounded fine. No distortion, no obvious problems. So I assumed it was fine.
Out of curiosity, I ran the setup through ChatGPT, just to check it. What I got back was a detailed explanation of why, although this setup works, it’s not ideal. The Big Knob outputs a level that the headphone amp isn’t really designed to receive, which can lead to volume mismatches, coloration, and other less obvious issues over time.
Nothing was “wrong” in the immediate sense—but the signal wasn’t being used the way the equipment was designed to expect.
The Y-Cable Temptation
This line of thinking led me to another idea.
I wanted to use a single pair of headphones with two different audio interfaces. Only one interface would be on at a time, so I thought: why not use a stereo Y-cable?
- One leg into the Volt 476 headphone output
- The other into the Zoom L-20 headphone output
- The combined end into my headphones
Once again, it worked. It sounded fine. There was no signal blending, no noise, and no obvious problem.
Once again, I ran it past ChatGPT.
Once again, I got a long explanation about impedance, back-feeding, unintended electrical interactions, and why this kind of solution is generally discouraged—even if it seems harmless in practice.
After some back-and-forth (and yes, some arguing), I was pointed to articles and technical documents that backed it up.
Reluctantly, I had to accept the original premise:
Just because you can do something—and it seems to work—doesn’t mean you should.
A Familiar Analogy
This isn’t unique to audio.
You can daisy-chain power bars together. Will things turn on? Yes.
Is it recommended? No.
Is it potentially dangerous? Absolutely.
(Mandatory disclaimer: don’t plug power bars into each other.)
Audio is full of similar situations—adapter chains, creative routing, clever workarounds—that technically function but quietly introduce problems that aren’t obvious until later.
When Creativity Meets Signal Flow
To be clear, I’m not saying experimentation is bad. Quite the opposite.
I often use ChatGPT as a thought experiment tool to test creative routing ideas before committing to them. But I’ve learned that it’s important to:
- be very specific in how questions are asked
- challenge the answers
- ask for sources
- and verify information elsewhere
Used carefully, it’s been helpful—but it doesn’t replace understanding signal flow fundamentals.
What I’ve come to appreciate is just how easy it is to miss small but important details in audio signal chains. Levels, impedance, intended use—all of these matter more than they appear to on the surface.
Final Thought
A cable might fit.
A signal might pass.
Everything might turn on and make sound.
But it’s still worth asking:
Is this how the system was meant to work?
Sometimes the answer matters more than we expect.
Happy processing.
