Skip to content

Solving Complex Patch Bay Routing for an SSL Fusion and Hybrid Studio

  • by
ssl fusion patchbay routing solved

I recently had an on-site session with a client, a dance music producer based on the other side of London. He has a fantastic collection of hardware synthesisers and outboard gear and needed help integrating a new piece of equipment: the SSL Fusion mix bus processor.

The main goal was to get this new processor running correctly in his system using his patch bay. Beyond that, his studio had a common problem: wires were trailing on the floor. He wanted to get more of his hardware connected and ready to use within his Ableton Live workflow.

When I arrived, our first task wasn’t technical, but physical. We installed some wire rack trays underneath his desk. This immediately allowed us to get the wires off the floor and create a tidy, professional workspace.

As part of this process, we pulled out all the old wires and did a full audit. We found quite a few USB and jack cables that were plugged in but not actually leading anywhere. Clearing these out simplified the setup massively.Next, we got the rack units set up. We installed his patch bay, a Samson unit that I particularly like because it has switches on the front. These switches let you easily change the connections between the top and bottom rows (normalled, half-normalled, or disconnected), which is incredibly handy for a dynamic studio setup.

With the patch bay in place, we moved on to the primary goal. We used XLR to Jack leads to connect the outputs of the SSL Fusion to the patch bay.

The routing itself required a combination of software and physical connections:

  1. Software: We used the Apollo Console software and Ableton Live.
  2. Ableton Setup: Inside Ableton, we created audio tracks and configured them to send audio to specific external outputs on his interface.
  3. Signal Flow: The audio left Ableton, travelled through the patch bay to the SSL Fusion for processing, and then returned via the patch bay into a new input, ready to be recorded back into Ableton.

The client was delighted. He was hearing his expensive new compressor working in his studio for the first time. We spent some time messing around with the settings and applied a quick master to one of his tracks. He was thrilled by the boost it gave the sound. It added a fantastic punch and energy to the music.

Once the Fusion was working, we moved on to his next goal: getting more inputs into his system to connect his other gear.

To achieve this, we incorporated two more interfaces: a Scarlet 18i20 and a Scarlet Octopre. Using the Audio MIDI Setup on his Mac, we combined these with his main Apollo interface to create an Aggregate Device. This setup gave him an additional 16 inputs to work with.

I did warn him that running aggregate devices with multiple interfaces can sometimes lead to clocking problems. We experienced one minor glitch at the start, but after that, the system was stable.With the new inputs available via the patch bay, we connected more of his hardware, including an Aki-Fusion filter and his 500 series rack which contained a Neve preamp and a compressor. We tested them all; they were working perfectly.

A big part of my job is not just to fix a problem, but to ensure the client understands how it was fixed. I gave him a short lesson on the new routing system. I showed him how to route his synths into his hardware effects and then into the new inputs, all using the patch bay. This means he can now confidently connect the rest of his gear himself.

We did hit one small, frustrating snag. His Midas 500 series chassis wouldn’t fit into the rack because it had little feet on it. To remove them, we needed to undo some very unusual hexagonal screws. It’s annoying when pro studio gear uses non-standard parts, but it was a minor issue in an otherwise very successful session.

Overall, the client was very satisfied. By the time I left, he had a tidy studio, a working patch bay, his new SSL Fusion fully integrated, and—most importantly—a clear understanding of how his system worked and what he needed to do next.

I help musicians and producers solve complex hardware integration and software problems like this every day. If you’re struggling with patch bay routing, aggregate devices, or getting your hybrid studio to work, I can help you find a clear path forward.

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.

Patchbay Lesson: Demystifying Outboard Gear Routing in Cubase

Client’s Question

How do I set up my external compressor in Cubase using my patchbay?

Session Result

Producer understood patchbay normalisation and successfully routed outboard compressor as a Cubase external effect.

Read Full Case Study Report: Patchbay Lesson: Demystifying Outboard Gear Routing in Cubase
Cubase Errors After Installing Sample Libraries in OneDrive

Client’s Question

Why can’t Cubase load my Spitfire Audio libraries after using OneDrive?

Session Result

Sample libraries relocated off OneDrive to internal SSD; errors resolved.

Read Full Case Study Report: Cubase Errors After Installing Sample Libraries in OneDrive
Solving Complex Patch Bay Routing for an SSL Fusion and Hybrid Studio

Client’s Question

How do I route an SSL Fusion processor through my patch bay in Ableton Live?

Session Result

SSL Fusion and hardware successfully integrated via patch bay, with expanded inputs from a multi-interface aggregate device.

Read Full Case Study Report: Solving Complex Patch Bay Routing for an SSL Fusion and Hybrid Studio
Dawsome Novum: Solving the “Please Locate Content” Error

Client’s Question

Why does Dawsome Music Novum say “Please locate content” after I installed it?

Session Result

Missing content library located via developer, installed, and verified working.

Read Full Case Study Report: Dawsome Novum: Solving the “Please Locate Content” Error