Transport menu -> Project synchronization setup
Send MIDI clock out to the port that the effect is on (effect must be able to receive MIDI clock messages).
There are other options as well that you may want active.
Look at page 499 of the operation manual (Synchronization chapter)
You are confusing the MIDI clock settings, which send MIDI clock as Master to your extrnal device, with the MIDI Timecode settings. Unless you’ re not slaving Cubase, to an external timecode signal, that option needs to be internal
I am easily confused! The project sync setup page gives 4 options: internal timecode (the default), midi timecode, ASIO Audio Device and System VST.
You said: “Unless you’ re not slaving Cubase, to an external timecode signal, that option needs to be internal” I would have thought you meant ‘unless you’re slaving Cubase.’ Was that a typo, or am I totally lost?
So doesn’t selecting ASIO Audio Device slave Cubase to my RME interface?
If so, I’m still curious about any relative advantages/ disadvantages of either option.
If not, I’ll just go with the default for the time being and try to learn more later.
Rule of thumb: the audio sample clock of the recording device should follow the sample clock of the A/D conversion device (slaved to). This has indeed nothing to do with MIDI time code. For example, I work with the Tascam DM3200 mixing board, which is my A/D converter, so it’s the audio sample clock master. At the same time it’s the MIDI slave to Cubase for project timing (MTC), which essentialy is ‘song’ position.
I should have read the Synchronization chapter more carefully and not wasted your time.
It looks like if I am only wanting to send tempo information for delays, I don’t need to activate any of the options which appear related to song positioning or midi machine code … although I can’t see that it would hurt.