To sync external gear to your DAW, send MIDI clock out of your audio interface, put every hardware device into external sync mode, and then dial in a per-device delay so recorded takes land on the grid. The clock handshake takes ten minutes. The delay calibration is what actually makes the timing tight, and that is where most sessions go wrong.
Most “my synth is out of sync” problems are not a broken clock. They are a device starting a fraction of a second late, or an audio path adding delay the DAW cannot see. Once you split those two apart, this becomes a boring checklist.
Table of Contents
- What You Need Before You Start
- How to Sync External Gear to Your DAW: Step by Step
- Quick answer: how to sync external gear to your DAW in eight moves
- 1. Identify which devices need to sync
- 2. Choose MIDI clock or audio clock
- 3. Connect the timing signal correctly
- 4. Configure the DAW as the master clock
- 5. Set external devices to receive clock
- 6. Start playback and measure the timing
- 7. Adjust latency and save the setup
- Common Mistakes
- Frequently Asked Questions
- What is the difference between MIDI clock and word clock?
- Do I need MIDI on my audio interface, or is a separate MIDI interface fine?
- Why does my hardware synth record late in the DAW?
- How do I sync modular or Eurorack gear to my DAW?
- Why does my drum machine drift from the DAW over long tracks?
What You Need Before You Start
You need four things, and only the first is optional to buy.
- A MIDI source from the DAW. Either MIDI ports on your audio interface or a small standalone MIDI interface. Two outputs is enough for two devices; four is comfortable.
- Clock cables. DIN MIDI cables for hardware DIN ports, USB-MIDI cables for hardware that only speaks USB. Cheap ones work, but a damaged pin shows up as mysterious jitter.
- Audio inputs. Every hardware voice needs a line input on the interface. Record-arm one input per device, leave a couple spare.
- Access to your gear’s sync settings. Each device needs an external or slave sync mode, and transport receive switched on separately from clock receive.
A MIDI thru box is optional until you own more than three devices. A dedicated master clock is optional until you play live or own several sequencer-equipped boxes.
One more decision belongs here, because it changes the cabling: monitor through the interface mixer rather than through the DAW. Several people running Ableton with an RME interface report that switching to TotalMix removed a large share of their timing problems, because the DAW monitoring path adds latency that the DAW does not fully account for.
MIDI clock or audio clock? For a synth, drum machine, groovebox or modular case, MIDI clock is the right answer almost every time. Word clock and S/PDIF exist to keep digital audio converters locked to a sample rate, not to keep a sequencer in step with your bar 7. Reach for audio clock when you are chaining digital recorders or a mixer that has no MIDI input at all.
How to Sync External Gear to Your DAW: Step by Step
Quick answer: how to sync external gear to your DAW in eight moves
- Decide which box is the master clock.
- Patch each device’s audio into the interface.
- Run MIDI clock output to every device.
- Turn on clock send for that port in the DAW.
- Set each device to external or slave sync.
- Enable transport receive, then play.
- Measure each device’s delay and set the offset.
- Record a loopback test and save the template.
Now the long version, with the parts that actually take experimentation.
1. Identify which devices need to sync
Sort every piece of gear into one of three groups: the DAW, MIDI-only devices with no timing to share (pads, controllers, expression pedals), and everything that generates sound on its own timeline. Only the last group matters here.
Within that group, split again. A synthesizer that the DAW plays notes into has no internal tempo of its own, so the clock just needs to keep its arpeggiator and tempo-synced effects aligned. A drum machine or groovebox running its own pattern is a different problem, and step 7 explains why the fix is not the same.
Write the list down with the port each device sits on. Cable confusion at setup time is the most common reason a device that worked yesterday is silent today.
2. Choose MIDI clock or audio clock
MIDI clock, also called MIDI beat clock, is a stream of tiny timing pulses sent over a MIDI cable at 24 PPQN, twenty-four pulses per quarter note. Alongside it come transport messages: Start, Stop and Continue, plus the Song Position Pointer that tells a device where it should be in the bar. Because the pulse rate scales with tempo, tempo changes and automation follow automatically.
| Sync type | What it locks together | What it cannot do |
|---|---|---|
| MIDI beat clock (24 PPQN) | DAW transport with sequencers, arpeggiators, tempo-synced effects | Nothing about sample rate or digital converter timing |
| Word clock (BNC or coaxial) | Digital audio devices to a sample rate | Sequencer tempo or bar position |
| S/PDIF or ADAT | Digital audio between converters and recorders | MIDI transport; carries no tempo grid |
| SMPTE / MTC timecode | Absolute position in time for film and video | Normal studio tempo sync; it needs a frame reference |
| DIN sync | Legacy Roland and Korg gear on a dedicated pin | Anything that only speaks MIDI or USB |
So MIDI clock is a relative signal. It tells a device “the beat is here” continuously, but not “you are at 2 minutes 13 seconds”. Anything that needs absolute position, such as a film cue or a video edit, wants SMPTE timecode instead.
3. Connect the timing signal correctly
MIDI is directional and it is picky. Clock leaves the interface and enters a device, so trace the OUT port on the interface to the IN port on the synth. If the device’s sync LED never blinks while the DAW plays, you have them reversed or you are on the wrong port.
For USB-MIDI, plug the device into the computer directly rather than through a hub where you can. Powered hubs add scheduling delay, and users chasing jitter in a USB-MIDI setup often find the hub is the culprit. Skip Bluetooth MIDI entirely; the jitter is severe and not worth troubleshooting.
Audio goes separately. Line out from each device to a line input on the interface, with no processing in between if you can help it. If the gear offers a clock-thru or MIDI-thru jack, note it now; you will want it at step 7.
4. Configure the DAW as the master clock
One device broadcasts, everything else listens. In the studio the DAW is almost always the right choice, because it is the only device that knows about your automation and arrangement. A hardware master is better for a live rig where a crash would otherwise kill everything.
Open your DAW’s MIDI preferences, find the output port each device is on, and enable clock send on that port only. Enabling sync on every port by habit creates a second master by accident, which is one of the common mistakes below.
Menu names shift between versions, so here is where each major DAW keeps the setting.
| DAW | Enable clock output | Per-device delay |
|---|---|---|
| Ableton Live | Preferences > Link, Tempo & MIDI, then Sync on each output port | MIDI Track Delay on the track or device |
| Logic Pro | Settings > MIDI > Clock, per MIDI output port | Track delay on the software instrument track |
| Cubase | Studio > MIDI System Setup > MIDI Ports, tick Sync on the output | Track Delay in the Track Control Panel |
| FL Studio | Options > Settings > MIDI, enable sync on the MIDI out device | Channel routing and per-channel offset |
| Studio One | Preferences > MIDI > MIDI Sync, enable the output port | Track Delay plus MIDI offset on the track |
| Reaper | Options > Preferences > MIDI, per-device clock output | Item and track timing offsets |
| Bitwig Studio | Settings > MIDI > Clock Output, per port | Timing offset on the note segment or track |
Two of those deserve extra care. In Ableton, the per-track MIDI Track Delay field is the one that matters and it lives on the track itself. In Cubase, people often forget that Sync is a column you tick per port inside MIDI System Setup, not a global preference.
If you would rather the hardware drive the DAW, that is a supported direction too. Set the project clock source to external rather than internal, and the DAW will follow incoming clock. Just know that Logic and Cubase have both been reported refusing to slave to an incoming MIDI clock in the past, usually until the external source was reselected or the cable reseated.
5. Set external devices to receive clock
Every hardware box needs two separate switches turned on, and this is where most setups stall. Clock receive is usually labelled External Sync, Ext Clock or Slave. Transport or MIDI sync receive is often a different menu entirely.
Devices split on transport receive, and the split explains a common report: hardware that ignores Start and Stop but still lines up on tempo. The clock is arriving, the transport message is not. Turn both on and test again.
Leave every device except your chosen master in external mode. A drum machine still set to internal will run its own tempo, ignore everything you send, and quietly pull the mix out of time.
6. Start playback and measure the timing
Put a click or a repeating drum pattern on a software track and record a minute of your hardware audio while the DAW plays. That single take tells you which of three problems you have.
Consistent but early or late by the same amount on every hit is latency, and you fix it with a delay offset. A slow slide where the hardware falls behind over the length of the take is drift, and you fix the clock path. Random early and late hits are jitter, and you fix the cable, the hub or the buffer size.
Zoom in on the waveform with both the software track and the hardware track visible. Good sync looks like two transients lined up within a few samples. Seeing that shape in the editor beats guessing by ear, and it takes under a minute.
7. Adjust latency and save the setup
Now set the offset per device. Use the hardware’s own clock delay field where it has one, since that shifts the device’s response to incoming clock before anything reaches the recorder. Otherwise use the DAW’s track delay or MIDI track delay for the same effect.
The numbers people report are small and device specific. In a long Gearspace thread on syncing Ableton with external hardware, per-synth MIDI track delay values ranged from 2 ms to 16.75 ms, and one setup settled on -9 ms for two Elektron boxes. A separate r/synthesizers thread has a user running -25.5 ms on a drum machine to line it up with Ableton. Treat these as a starting range rather than a fixed rule, because each figure belongs to a specific cable, interface and buffer size.
Buffer size matters more than most people expect. Driver error compensation is measured against a buffer size, and one user reports around 1.04 ms at a given setting on a MOTU interface on PC. Change the buffer and that calibration is stale, so write your offset values next to the buffer size you set them at.
Keep plugins off the monitoring path while you calibrate. Anything adding delay there moves the audio the DAW records without telling the DAW, and you end up chasing your own tail.
Then save the whole thing as a session template with your routing, port assignments, clock toggles and delay values baked in. Label the cables. Write the buffer size on the interface itself. This is the difference between a session that opens ready to record and one that starts with twenty minutes of re-patching.
Gear with its own internal sequencer is the exception. If a device is playing its own pattern and only listening to tempo, DAW track delay cannot compensate the fact that it started late on its own. That is why one user on the same Gearspace thread found a Roland TR-8 impossible to fix inside Live. A dedicated master clock box, such as an E-RM Multiclock or an Expert Sleepers USAMO, can apply a start offset per device, which is the one thing the DAW has no field for.
Common Mistakes
These account for most failed sync sessions, and each has a specific fix rather than a ritual of replugging everything.
- Two devices claiming master. The drum machine is still in internal mode, or a second DAW instance is sending clock. Every device except one stays in external sync.
- Clock sent to the wrong port, or reversed. OUT to IN, and check the port index in the DAW preferences against the label on the device.
- Transport receive left off. Clock receive and Start/Stop receive are separate settings on most hardware. Devices that follow tempo but ignore Stop are telling you exactly this.
- Uncompensated latency. Record a minute of hardware audio and measure the offset instead of nudging every take by hand.
- USB MIDI through a hub, or over Bluetooth. Plug into the computer directly. Hub scheduling delay is a common source of random jitter.
- Calibration invalidated by a buffer size change. Re-measure and re-enter your delay values whenever the buffer moves.
- Monitor plugins in the path. Move monitoring to the interface mixer while calibrating, then decide what to live with.
- Expecting track delay to fix a self-sequencing device. That needs a hardware master clock with per-device start offset, not a DAW field.
- Daisy-chaining too far. Chaining works comfortably for two or three devices. Beyond the fourth or fifth, accumulated thru-hop delay turns into audible drift and you want a multi-port interface or a proper sync box.
| Symptom | Likely cause | Fix |
|---|---|---|
| Device never starts with the DAW | Transport receive off, or wrong port | Enable MIDI sync receive, re-pick the output port |
| Plays in time but ignores Stop | Start/Stop receive disabled | Turn on transport sync receive on the device |
| Every hit late by the same amount | Fixed latency | Set a negative clock delay or track delay |
| Slips behind over a long track | Clock drift through thru boxes or cheap cables | Shorten the chain, swap cables, re-patch directly |
| Random hits early or late | Jitter from USB hubs or a buffer size that is too high | Bypass hubs, lower the buffer size |
| Sync lost after unplugging USB | Song position pointer not resent | Jog or seek in the DAW transport to resend position |
| Fine at 90 BPM, off at 140 | Device ignoring tempo changes or smoothing pulses | Check for a pulse smoothing or averaging setting on the device |
Test sync for a full minute, not five seconds. Drift is invisible early and obvious later, and a short test is exactly how a slow slip gets shipped.
Frequently Asked Questions
What is the difference between MIDI clock and word clock?
MIDI clock carries tempo and transport at 24 pulses per quarter note, telling instruments where the beat is. Word clock carries the sample rate reference that keeps digital audio converters aligned. They solve different problems: MIDI clock lines up sequencers and arpeggiators, word clock lines up recorders and converters. Your hardware synth needs MIDI clock.
Do I need MIDI on my audio interface, or is a separate MIDI interface fine?
A separate one is completely fine, and plenty of people run a small dedicated MIDI interface alongside their audio interface. What matters is output count: one clock-enabled output per device you want to sync. Many interfaces let you enable clock on only some ports, so check that per-port toggle before assuming your setup is broken.
Why does my hardware synth record late in the DAW?
Almost always a fixed latency rather than a clock fault. The device receives the note and its own processing adds delay before audio reaches the interface. Record a minute of audio, look at the waveform against the MIDI track, and enter the gap as a negative clock delay or a positive track delay. Monitor through the interface mixer while you measure, since DAW monitoring adds its own delay.
How do I sync modular or Eurorack gear to my DAW?
You need a clock module in the rack and a way to get MIDI clock into it. Most clock modules accept a DIN or gate input, so feed them from a MIDI interface output with a suitable level converter, or use a module that takes MIDI clock directly. Send clock from the DAW as usual, ignore the tap or reset the module when the DAW stops, and expect to dial the module’s own division settings by ear.
Why does my drum machine drift from the DAW over long tracks?
Drift usually means the clock is being regenerated along the way. Every MIDI thru hop adds a small delay, and those stack, so a drum machine at the end of a daisy chain lands progressively later. Patch it directly, shorten the chain, or move to a multi-port interface. Cheaper cables and unpowered USB hubs cause similar slow slip and are worth ruling out first.
Begin with one device, not four. Patch it directly, enable clock send on that one port, put it in external mode, record a minute, and write down the delay value that lined it up. Once you can repeat that measurement, adding the second and third device takes minutes instead of an evening, and a saved template means you never redo it.
