Lumen Grid: MIDI clock sync and getting stems out

Once the loops are right and the racks are set, two jobs remain: keeping the hardware in time, and getting the audio out.

This is part of the complete Lumen Grid guide.

MIDI Clock, briefly

MIDI Clock is a stream of timing pulses — 24 per quarter note, which is the standard every piece of hardware agrees on. Whichever device sends it sets the tempo; whichever devices receive it follow.

Alongside the pulses are three transport messages:

• Start — begin from the top.
• Continue — resume from where you stopped.
• Stop — halt.

Lumen Grid implements all of it.

Master or follower?

Rule of thumb: the least flexible device should be the master.

Lumen Grid as master — it sets the tempo and forwards clock out to everything else. Use this when the arrangement lives in the grid and the hardware is providing sounds.

Lumen Grid following — it locks to a single MIDI input. Use this when a groovebox, drum machine or another sequencer is driving the session and is awkward to slave.

Follow mode listens to one input deliberately. Multiple clock sources arriving at once is the most common cause of unstable tempo in a hardware rig, and accepting only one removes that whole category of problem.

Forwarding to several devices

Clock can go out to multiple USB and DIN outputs at the same time, so a synth, a drum machine and a pedal can all be locked to the same tempo from one place.

Practical points:

• Turn clock off on devices that do not need it. Fewer clock streams means fewer opportunities for confusion.
• Decide once which device is the master and leave it. Changing the master mid-session is where drift and double-tempo problems appear.
• Start everything from the master’s transport, not individually.

Getting the audio out

Three routes, for three situations.

1. Drag into FL Studio

OLE drag and drop moves a WAV clip straight into FL Studio.

Fastest path when you have one idea worth developing further. No export dialog, no file management — grab the clip and drop it.

2. Render stems

Per track or from the master, at 48 kHz, sample-aligned and cancellable.

Scene and bar arrangements are persisted, so the render reflects the performance you set up rather than an arbitrary loop. That means you can build an arrangement across scenes, render it, and open a DAW project that already has the structure.

Before rendering:

• Check the loop seams — the same XFADE is used for rendering as for playback, so what you heard is what you get. See loops and scenes.
• Decide whether to resample tracks through their racks first, or render with the racks live. See CLAP racks.
• Leave headroom on the master — see what is headroom.

Stems or a stereo master? Stems if the track is going into a DAW for further mixing. A master render if the performance is the piece.

3. Save the session

Session save and load is atomic: it either completes fully or does not happen, so you never end up with a half-written session file.

Save before every performance and before every large structural change. There is 50-step undo covering structural, audio and FX changes, but a saved session is the reliable backstop.

Handing off to a DAW

Once stems are in your DAW, normal rules apply:

• Route them to buses — see what is a bus in mixing.
• Balance with faders first — see what is mixing.
• Run the mixing checklist before you master.

The advantage of arriving from Lumen Grid is that the material is already committed: real recordings of real instruments, in time, with the seams already designed. That is a much better starting point than a project full of unresolved decisions.

A performance-to-release workflow

1. Set the clock relationship and confirm every device follows.
2. Build scenes and rehearse the transitions.
3. Save the session.
4. Perform the arrangement, using scene launch and the loop-end stop.
5. Resample any track whose sound is finished.
6. Render stems.
7. Take the stems into a DAW, or master the stereo render directly — see how to master a track.

Troubleshooting sync

Tempo drifts: two clock sources are active. Turn one off.

Double or half tempo: a device is interpreting the clock at a different division. Check its own clock settings.

Devices start at different times: use Start from the master transport rather than starting each device by hand.

Nothing follows: the receiving devices are not set to external clock. This is on the hardware, not on Lumen Grid.

Back to the start

That completes the advanced path. The complete Lumen Grid guide ties all four parts together, and the product page is at SPC Lumen Grid.