This section is about synchronization via MIDI Clock, and does not apply to users of ReWire. If you are using Reason Essentials together with a ReWire compatible application, ReWire automatically handles all synchronization issues for you. See
“About synchronization” for details.
Synchronization, in this context, is when you make Reason Essentials play at the same tempo as another device; where both start, stop and can locate to certain positions, together. This is done by transmitting MIDI Clock signals between Reason Essentials 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 Essentials and hardware devices (tape recorders, drum machines, stand alone sequencers, workstations etc.) and other computer programs running on the same or another computer.
In a synchronized system there is always one master and one or more slaves. In our case, the master is the one that controls the tempo. In other words, it is only the tempo setting on the master device that is of any relevance, since the slaves slavishly follow the master's tempo.
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 Essentials.
Because of the latency problem described in “ReWire and Latency”, you might need to adjust Reason Essentials’ playback in relation to the sync master, so that they are in perfect time. The tempo will not differ between the two, but Reason Essentials 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.
There might be situations where you can’t compensate enough in Reason Essentials 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.
Due to the latency phenomenon, described in “About latency”, Reason Essentials needs some time to correct it’s 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:
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.
Again, due to the latency phenomenon, Reason Essentials 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 Essentials 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 Essentials can adjust to it.
The Input Focus (MIDI + Audio) and Play Focus (MIDI Sync) buttons (located on the Reason Essentials 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.