Synchronization and Advanced MIDI : Synchronization to MIDI Clock

Synchronization to MIDI Clock
ReWire users – read this!
This section is about synchronization via MIDI Clock, and does not apply to users of ReWire. If you are using Reason together with a ReWire compatible application, ReWire automatically handles all synchronization issues for you. See “About synchronization” for details.
What is synchronization and MIDI Clock?
Synchronization, in this context, is when you make Reason play at the same tempo as another MIDI device; where both start, stop and can locate to certain positions, together. This is done by transmitting MIDI Clock signals between Reason and the other device. MIDI Clock is a very fast “metronome” that can be transmitted in a MIDI cable. As part of the MIDI Clock concept there are also instructions for Start, Stop and locating to sixteenth note positions.
You can set up synchronization between Reason and hardware devices (tape recorders, drum machines, stand alone sequencers, workstations etc.) and other computer programs running on the same or on another computer.
Host/Device
In a synchronized system there is always one Host and one or more Devices. In our case, the host is the one that controls the tempo. In other words, it is only the tempo setting on the host that is of any relevance, since the devices follow the host's tempo.
Using Reason as MIDI Clock Host
Reason can transmit standard MIDI Clock signal. It also sends Start, Stop, Continue and Song Position Pointer (SPP) MIDI messages so that you can also control the transport functions of the synced equipment from the Transport Panel in Reason. To set up Reason as a MIDI Clock host, proceed as follows:
1.
Selecting MIDI clock output port.
2.
3.
*
Now, you have set up Reason as a MIDI Clock sync master. When you start the Reason sequencer, MIDI Clock is sent out on the selected MIDI Out Port.
*
*
A negative Output Offset means that the MIDI Clock signal is sent out from Reason earlier to compensate for the lag.
*
There are also some additional options regarding the MIDI Clock signal that can be selected at the bottom of the MIDI clock sync section:
When this box is checked, Reason continues to send out MIDI clock signal also when the sequencer is stopped.
When this box is checked, Reason sends out MIDI Song Position Pointer information to the device. If the synced device doesn't support Song Position Pointer, turning this setting off can improve synchronization. This is also useful if the synced device is playing a looped pattern and should disregard all positioning.
When this box is checked Reason sends out Stop/Song Position Pointer/Continue messages to the synced device, if the song position locator in the sequencer is moved (either manually or when in Loop mode) when the sequencer is running.
If unchecked, only Song Position Pointer messages are sent out if the song position locator is moved (or in Loop mode) while the sequencer is running.
Syncing Reason to an external MIDI application or instrument
This example assumes that you have an external device, such as a drum machine, hardware sequencer, another computer, tape recorder etc., that transmits MIDI Clock signals to which you want to synchronize Reason.
1.
2.
3.
4.
5.
6.
7.
Reason will start playing in sync with it.
*
Syncing Reason to another program on the same computer
*
The preferred method for synchronizing two applications is by using ReWire, see “ReWire”. However, if the application you need to sync Reason to doesn’t support ReWire, you can try the procedures described below.
This section describes how to use MIDI Clock to synchronize Reason to another application running on the same computer.
*
Proceed as follows:
1.
Under Windows this is done by selecting one of the MIDI routing utility ports.
2.
3.
4.
5.
6.
Reason will start playing in sync with it.
*
External synchronization considerations
Adjusting for Latency
Because of the MIDI latency problem described in “ReWire and Latency”, you might need to adjust Reason’s playback in relation to the sync host, so that they are in perfect time. The tempo will not differ between the two, but Reason might play ahead or behind the other application. You might need to adjust this. However, this is something you only need to do once. The setting is stored with your other preferences, so you don’t need to adjust it again.
Proceed as follows:
1.
This click can either come from an internal metronome or from a MIDI source. If you use a MIDI source, make sure you pick one that has solid MIDI timing.
2.
You might for example use the sequencer Click or a Redrum drum computer for this.
3.
4.
5.
6.
7.
If Latency Compensation isn’t enough
There might be situations where you can’t compensate enough in Reason to make two software applications run in sync. This might especially be true if the other application is an audio sequencer, that is if it can record and playback both audio and MIDI.
This problem is an indication of the fact that the other application has not been set up properly and that its audio playback is not in sync with its own MIDI playback.
*
About the beginning of the Song
Due to the latency phenomenon, described in “About latency”, Reason needs some time to correct its playback speed when it first receives the Start command. This can be noted as a small glitch in the audio playback, when the program starts. If this is a problem, you need to insert a couple of empty measures at the beginning of the Song. Proceed as follows:
1.
2.
3.
4.
About MIDI Song Position Pointers
MIDI Clock actually consists of five type of messages: The actual clock (the metronome that establishes the tempo), Start, Stop and Continue commands and Song Position Pointers. This last type of message contains information about positions, so that a program for example “knows” where in a Song to start playback from.
Normally, this ensures that you can locate to any position and activate playback from there. In older devices, Song Position Pointers might not be implemented. This means that you will be able to synchronize properly only if you start both devices from the absolute beginning of the song.
About Tempo and Tempo Changes
Again, due to the latency phenomenon, Reason needs a bit of time to adjust to changes in tempo. If there are abrupt changes in the MIDI Clock, due to drastic tempo changes in the master, you will note that Reason will require up to one measure to adjust itself to the change. How long this actually takes also depends on the precision of the incoming MIDI Clock. The more precise it is, the faster Reason can adjust to it.
If this adjustment is a problem, try to use gradual tempo changes rather than immediate ones.
*
*
Input Focus and Play Focus
If you activate (external) MIDI Clock sync on the Options|Sync menu, the Transport Panel controls will be disabled, and Reason will not run unless MIDI Sync data is provided from an external device.
The Input Focus (MIDI + Audio) and Play Focus (MIDI Sync) buttons (located on the Reason Hardware Interface) relate to how incoming MIDI and MIDI sync should be handled if there are several open Song documents. If you have two or more Songs opened, and no MIDI sync is used, the currently selected Song (the document “on top”) always has Input focus.
If (external) MIDI Clock sync is enabled (which is global for all currently open Song documents), this functionality changes in the following way:

Synchronization and Advanced MIDI : Synchronization to MIDI Clock