Hi all,
What is the purpose of MIDI Time Code, apart from syncing the arpeggiator of the external synth?
I have been using Cubase and a few hardware synths for a decade without syncing MIDI Time Code, have I been doing it wrong?

 

I guess you mean the midi clock

it's basically used if you wanna send the tempo track to the external synths. For example in case you wanna sync the internal arpeggiator or LFOs or FX/delay of the synth with cubase's tempo trACK

 

MTC is MIDI Time Code and when people talk about it in a setup like this, they usually mean MTC sync. It’s different from MIDI Machine Control: MMC is just transport messages like play, stop, rewind. MTC is SMPTE-style timecode and tells devices what time the timeline is at, so they can lock position.

For hardware synths and arpeggiators, that’s not what you want anyway. those use MIDI Clock, which is tempo based. That’s why you’ve been fine for ten years without MTC. MTC is only needed when you’re syncing to something that requires positional time, like an external recorder, a second sequencer, or video.

Good example of when you would need this are any of the later (like ~2000) Roland Grooveboxes connected to one another, or that bastard vs1680.

 

You haven’t been doing anything wrong. Most bedroom/studio producers never enable MTC and live very happy lives.

Spoiler: Source: Grok KI

MIDI Time Code (MTC) is not something you must use in every setup, and the fact that you've been happily making music for a decade without it means you haven't been "doing it wrong" at all. Most people who use Cubase + hardware synths never touch MTC in their daily work, and that's perfectly fine.

Main purposes of MIDI Time Code (MTC)
MTC is basically SMPTE timecode (hours:minutes:seconds:frames) sent over MIDI instead of audio or dedicated LTC lines. Its real jobs are:

1. Precise synchronization of devices that need to know the exact song position at all times
   • Video playback software (so picture stays perfectly in sync with your DAW)
   • Lighting consoles, show-control systems, theater automation
   • Tape machines or older digital recorders (in the past)
   • Some drum machines or sequencers that can chase timecode (e.g., old Akai MPCs, Roland MC-50, etc.)
   • External hardware sequencers that need to start at the exact bar/beat when you press play in the middle of a song
2. Locking multiple DAWs or computers together (one acts as master, others slave via MTC → converted to MMC or internal chase)
3. Syncing tempo-based effects or arpeggiators that can slave to timecode This is the one you already mentioned. Some synths (especially Roland, Korg, or older stuff) can lock their arpeggiator or internal sequencer to incoming MTC + MIDI Clock, so the arp speed follows Cubase even if you change tempo mid-song or locate to a different position.

When you probably DON’T need MTC at all (your current situation)

• You trigger your hardware synths with normal MIDI notes from Cubase tracks
• You use MIDI Clock (Start/Stop/SPP + Clock) for arpeggiators or sequencers that support it
• You’re not working with video, live show control, or multiple synced machines
• You always start songs from the beginning or don’t mind if an external arp starts at its own phase

In this very common setup, MIDI Clock + Song Position Pointer (SPP) is enough 99% of the time, and Cubase sends both automatically when you enable MIDI Clock output to the port.

When MTC actually becomes useful or necessary

• You work with video and need frame-accurate lock
• You have hardware that can only chase timecode (some older drum machines, lighting desks, etc.)
• You want external arpeggiators/sequencers to stay perfectly in sync when you locate to bar 57 or change tempo in the middle of the song (MIDI Clock + SPP alone can drift or re-phase on some devices)
• You’re running a second computer or iPad with apps that only understand MTC

Bottom line
You haven’t been doing anything wrong. Most bedroom/studio producers never enable MTC and live very happy lives. MTC is a specialized tool for specific synchronization needs (mainly video and complex live rigs). If your external arpeggiators already lock nicely with MIDI Clock, you’re golden.

If one day you notice that an arp loses phase when you jump around in the arrangement or after a tempo change, then you can try sending MTC (Cubase → MIDI → MIDI Timecode) to that synth and set it to “external sync” or “timecode slave.” But until it’s a problem, don’t worry about it.

You’ve been doing it exactly right for a decade.

 

So i went down the rabbit hole of external clocks I first purchased the retrokits rk-006 and it just didn't work well for me .. I then purchased the ERM multiclock .. and it's pretty amazing.. pricey but you essentially need to measure your latency in real time via a output on your audio interface because if your clock isn't routed to your output you could have 2 or 20 plugins or a large project .. "but doesn't have to be anything can set off the wrong time values but usually it's the strain on your cpu .. but as long as you have a clock that routes to ur output . I had to Frankenstein the multi clocks hardware with the midronome plugin because the multiclocks plugin didn't work with fl studio.. I could legit write a mini book on the issues of syncing.