Routling Wiki Features FAQ Join the Waitlist

Several local microphones, remote guests over a call app, everyone recorded separately, and nobody hearing their own echo.

What you need#

  • An interface with as many inputs as you have local mics
  • A call application for remote guests
  • A DAW or recorder for separate tracks - see DAW Integration

The mix-minus problem#

Remote guests must hear everyone except themselves. Send a guest their own voice back and they hear themselves delayed, which is unusable.

Routling handles this naturally, because you decide every connection: build the guest's feed from everything but their own return.

Build it#

1. Open your interface#

Open Device, pick your interface. Buffer 256 or lower - people are monitoring themselves live.

2. Local microphones in#

Right-click → ASIO Channels → Input for each mic. Rename them - double-click the name - to Host, Guest A, and so on. On a busy canvas this matters.

3. Process each mic#

One FX Module per mic: high-pass, gate, compressor.

4. Remote guests in#

Right-click → App Capture → your call app. This is everyone on the call, mixed - call applications do not expose guests separately.

5. Headphone feeds#

Right-click → ASIO Channels → Output for each headphone output.

Connect into each local person's headphones:

  • Every local mic including their own (local monitoring is direct, so no meaningful delay)
  • The remote guest feed

6. The mix-minus for remote guests#

Route into the call app via Routling I/O:

  1. Right-click → Routling I/O → Outputs (Routling → apps)To Routling 1.
  2. Connect only the local processed mics into it.
  3. Do not connect the App Capture of the call app into it.
  4. In the call application, set its input device to that Routling device.
Host micGuest A micGuest B micTo Routling 1Call appCall app captureHeadphones

That single omission is the mix-minus. The remote guests hear the room; they do not hear themselves.

7. Separate tracks#

Right-click → Mixing & Effects → Virtual ASIO, then connect each source to a distinct To DAW channel:

ChannelSource
1Host mic, processed
2Guest A mic, processed
3Guest B mic, processed
4Remote guests

Arm four tracks in the DAW. Each participant is now independently editable.

Recording checklist#

Before you start:

  1. Every mic's meter moves when that person speaks.
  2. Every participant hears everyone else in their headphones.
  3. Remote guests confirm they do not hear themselves.
  4. DAW tracks are armed and each is receiving the right source.
  5. Toolbar latency is low enough that live monitoring feels natural.
  6. Save the session - toolbar ⋮ → Save, name it Podcast.

Gotchas#

  • Feedback: anything routed back to its own source echoes. The call app's capture must never reach the Routling output feeding the call app.
  • Headphones, not speakers, for anyone with an open mic.
  • Sample rate consistency between Routling, the call app and the DAW.
  • Free tier limits shape this - one FX Module and 4 Virtual ASIO channels.