Lumen Grid audio setup: ASIO, WASAPI and loopback

Audio setup is the step that decides whether the rest of the session is pleasant or infuriating. On Windows there are three ways in, and picking the right one per track solves most problems before they happen.

This is part of the complete Lumen Grid guide.

The three input types

Native ASIO

The driver your audio interface manufacturer wrote — Roland, Focusrite, or ASIO4ALL as a generic fallback.

Use it when: you have an interface and you are playing hardware in real time.

Why: lowest latency and the most reliable timing. ASIO bypasses the general Windows audio path, which is exactly what you want when the delay between playing a note and hearing it matters.

Trade-off: ASIO devices are usually exclusive. While Lumen Grid has the device, other applications may not.

Lumen Grid provides shared per-driver hubs so several tracks can use the same ASIO device without fighting over it, plus a route to the driver’s own control panel for buffer settings.

WASAPI

The standard Windows audio path.

Use it when: you are using ordinary Windows devices, or you need to share the device with other software.

Trade-off: higher latency than ASIO. Fine for recording a source that is already in time; less pleasant for playing along.

System loopback

Captures what Windows is currently playing, with no cable.

Use it when: you want to record a software instrument, a browser, a video, or another application straight into a clip.

Watch for: it captures everything going to that output, including notification sounds. Silence your system alerts before recording.

Choosing per track

Each track picks its own input pair. That is the feature that makes multi-device sessions work.

A realistic setup:

Track	Source	Input type
1–2	Hardware synth via interface	Native ASIO
3	USB microphone	WASAPI
4	Software instrument in another app	Loopback

All four record into the same grid, and the shared output mixer sums them with true track and master metering.

Setting levels

The IN meters are logarithmic, which means quiet signals remain visible rather than sitting invisibly at the bottom. That is helpful, and it makes it easy to leave the trim too low without noticing.

1. Arm the track.
2. Play the loudest thing you intend to play.
3. Set input trim so that peak sits comfortably below the top.
4. Leave room — you can raise a clip later, but you cannot un-clip it.

This is headroom at the input stage, and the same logic applies: turning down costs nothing, and running out costs the take.

Latency, and what to do about it

Latency is the delay between playing a note and hearing it. It is a function of the buffer size and the driver type, not of Lumen Grid.

To reduce it:

1. Switch to native ASIO if you are not already on it.
2. Open the driver panel and lower the buffer.
3. Keep lowering until you hear crackles or dropouts.
4. Go back one step.

When to raise it again: if you add heavy CLAP racks and start hearing dropouts, raise the buffer. Recording needs low latency; mixing and rendering do not.

Format mismatches

If a device is running at a different sample rate from the session, Lumen Grid redirects rather than failing silently. When you see that, the fix is to set the device to the session rate in the driver’s own control panel — matching rates avoids any conversion in the path.

Output

One shared output mixer handles the final sum, with real track and master metering.

Choose the output device and latency in settings; both persist between sessions, along with the driver selected automatically at startup. Set it once and it is there next time.

A setup checklist

• Driver type chosen per track.
• Sample rates matched between session and devices.
• Input trim set from the loudest playing, with headroom left.
• Buffer low enough to play comfortably.
• System sounds muted if using loopback.
• Output device and latency confirmed in settings.
• Tempo set before recording anything you intend to loop.

That last one is not an audio setting, but it saves the most time — see loops and scenes.

When something is wrong

No input signal: wrong input pair on the track, or the device is held exclusively by another application.

Crackling: buffer too low, or CPU load too high. Raise the buffer, or resample a heavy chain to audio — see CLAP racks.

Delay while playing: buffer too high, or you are on WASAPI where ASIO is available.

Recording too quiet: input trim, not the fader.

Loopback recording extra sounds: it captures the whole output. Mute everything else.

Once this section is right, you rarely think about it again — which is the point of doing it carefully once.