Skip to content

Korg Kronos Audio Routing Fixed in Logic Pro

  • by
connecting synth to logic pro solved

When integrating a powerful hardware instrument like a Korg Kronos 2 into a DAW like Logic Pro, it’s common for audio and MIDI routing to become a point of frustration. The setup is rarely plug-and-play, and a small oversight can stop the creative flow completely.

A client recently booked a remote session with Audio Support because he couldn’t hear his Kronos 2 when recording into Logic. He knew his equipment was working, but the final connection between the synth and the DAW was a mystery.

The client, a seasoned producer, wanted to record the internal sounds of his flagship workstation, the Korg Kronos 2, directly into Logic Pro. His system was built around a Mac running Logic, using a reliable Focusrite Scarlett 18i20 as the primary audio interface.

The problem was simple: he had the Kronos connected and the MIDI was working, but no audio was audible or recordable on a new Logic track. This left him stuck, unable to capture his sound design work and move forward with production.

My approach to any hardware integration issue is to trace the signal path step-by-step, starting with the physical connections and ending inside the DAW.

First, I confirmed the MIDI connection. We checked Logic’s MIDI Environment window, and the incoming MIDI signal from the Kronos was registering correctly. This confirmed that the computer and the Kronos were communicating, which ruled out a common class of problems.

Next, we focused on the audio signal. I asked the client to confirm which physical ports on the back of his Scarlett 18i20 he had used to connect the audio outputs from the Kronos. He had correctly used a pair of balanced cables, but they were plugged into Inputs 3 and 4 of the Focusrite.

This was the key insight. The client was expecting to see the audio on Input 1/2 in Logic—the default for most new audio tracks—but the physical cables were in a different location

The solution was simple and immediate: a routing correction within Logic Pro.

  1. I created a new stereo audio track in Logic.
  2. In the track’s Inspector window, I navigated to the Input selection menu.
  3. We switched the track’s input from the default Input 1-2 to the corresponding physical ports: Input 3-4 (Stereo).
  4. I then ensured the Record Enable button was active on the track.

As soon as he played a sound on the Korg Kronos 2, the meters on the Logic track sprang to life. The audio was instantly audible and ready for recording. The entire process of diagnosis and fix took just a few minutes of our scheduled time.

With the primary technical hurdle cleared, we used the remainder of the session to explore some workflow optimisation in Logic Pro. The client was keen to learn some intermediate features that would enhance his creative process.

Take Folders and Overlapping Recording: We discussed Logic’s powerful Overlap Recording feature. This is an essential tool for producers, as it allows multiple takes to be captured quickly into a Take Folder, making it easy to audition and compile the best parts later.

Input Monitoring and Effects: I showed him how to enable Logic’s input monitoring feature, which allowed him to hear his Kronos with Logic’s built-in effects—such as compression or reverb—before the signal was recorded.

This case is a classic example of a misaligned expectation rather than a true fault. The hardware and software were both working perfectly, but the user’s assumption about the default routing was incorrect.
I find that many frustrating issues in a home studio come down to a basic but hidden routing mismatch. It highlights why an external piece of mind is so valuable: a fresh set of expert eyes can quickly trace the signal flow and identify the single point of failure. You don’t need to be a technical expert; you just need to know which menu to check, and when.


I help musicians and producers worldwide solve problems like this every day. If you’re struggling with audio routing or getting your hardware instruments connected in your DAW, I’ll help you find the real cause and get you back to creating.

No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

I usually reply to enquiries within a few hours during UK weekday daytime.

Once you make an enquiry, I’ll read it personally and reply with initial advice or a link to book a remote session if needed.

For booked sessions, you’ll receive a secure AnyDesk link and we’ll talk via WhatsApp or voice chat. Sessions last up to an hour — long enough to diagnose the cause and apply a practical fix.

How soon can you help me?

Usually within 1–2 days. Use the booking system below to find the next available slot.

How do remote sessions work?

We connect via AnyDesk for secure screen sharing and talk via WhatsApp or Google Meet. I guide you live.

What does it cost?

£90 per hour for remote troubleshooting (approx. $110 / €120). Paid securely via SimplyBook.

What if the problem isn’t fixed in one session?

You’ll get a clear plan: next steps, parts to order (if any), and an estimate for follow-up.

Recent problems solved for real clients.

Resolving the Ghost Plugin: Drum Synth Validation Error in Logic Pro

Client’s Question

Logic Pro plugin validated but not showing in menu, what’s wrong?

Session Result

AIR Drum Synth plugin file conflict resolved, instrument loading correctly.

Read Full Case Study Report: Resolving the Ghost Plugin: Drum Synth Validation Error in Logic Pro
AI Co-Pilot: Generating a Vintage Soul Track with Suno

Client’s Question

How can I use Suno AI to generate professional-sounding music demos quickly?

Session Result

AI-generated 70s Soul track created from original lyrics via detailed style prompt.

Read Full Case Study Report: AI Co-Pilot: Generating a Vintage Soul Track with Suno
Korg Kronos Audio Routing Fixed in Logic Pro

Client’s Question

Why can’t I hear my Korg Kronos 2 in Logic Pro?

Session Result

External synth located, audio signal successfully recorded.

Read Full Case Study Report: Korg Kronos Audio Routing Fixed in Logic Pro
Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks

Client’s Question

How do I send my guitar pedal sound and a backing track clearly on Zoom?

Session Result

High-quality, mixed guitar, microphone, and backing track successfully routed into Zoom.

Read Full Case Study Report: Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks