Synchronization project settings consist of the following four tabs: General, Audio, MIDI, and Unitor.
Choose File > Project Settings > Synchronization (or use the Open Synchronization Project Settings key command, default assignment: Option-Y).
Click the Settings button in the Arrange toolbar, then choose Synchronization from the pop-up menu.
Control-click the Sync button in the Transport bar, then choose Synchronization Settings from the shortcut menu.
The General pane of the Synchronization project settings offers the following synchronization parameters, which are used when running Logic Pro as a slave.
Logic Pro automatically locks to the first synchronization signal it receives.
Important: Ensure that different synchronization signals don’t arrive simultaneously—remember that there can only be one time code master.
Note: In drop frame formats, certain frames are left out. (This follows a regular pattern.) To distinguish between formats, those without dropped frames are sometimes referred to as “nd” or “non drop.”
Note that it is not possible to automatically distinguish between the 29.97 and 30 fps MTC frame rates:
The MTC standard does not allow a distinction.
A measured rate of 30 fps could also be 29.97 fps time code running too fast, and vice versa.
Logic Pro automatically interprets frame rates of “approximately 30 fps” as either 29.97 (drop frame) or 30 fps (non drop), depending on whether or not the drop frame format is used. This interpretation will usually be correct, because these two formats are used as a standard.
The “Auto detect format of MTC” option only switches to 29.97 (drop frame) or 30 fps (non drop) if one of the other conventional formats was previously set. If you want to synchronize Logic Pro to one of these unconventional frame rates, you need to define the format manually. This setting will not be altered by the “Auto detect format of MTC” function.
There are some devices that generate time code pulses that may require a specific number of frames to be set, in order to maintain synchronization. The “never, Jam Sync” setting basically sets Logic Pro to free-wheel if the synchronization signal is lost. In other words, Logic Pro will run on its own internal clock (at the most recently received tempo) if the synchronization pulse is lost. This approach ensures that recording will continue, even if the incoming timing pulse fails.
The default is Bar Position: 1 1 1 1 plays as SMPTE 01:00:00:00.
The SMPTE offset of 01:00:00:00 (one hour) is normally used, because it allows you to pre-roll an amount of time code.
The Tempo List always shows the real SMPTE time, never the SMPTE View Offset. The SMPTE View Offset is used in all other windows (including the Transport bar).
Tip: It is common practice in many video (and audio) post-production houses to set a one-hour SMPTE offset (01:00:00:00). This avoids a problem commonly referred to as midnight, where a pre-roll passes through SMPTE time 00:00:00:00, which causes issues with some tape machines (such as the ADAT).
Use the parameters in the Audio pane of the Synchronization project settings to keep your audio and MIDI tracks synchronized.
Note: The real-time sample rate conversion feature of Logic Pro allows it to follow an external MTC signal (MTC Continuous), while maintaining the correct audio playback pitch and speed. This feature even works when recording in MTC-slave mode.
The MIDI pane configures Logic Pro to send time code via MIDI, when it is in playback or record mode. This pane lets you synchronize external slave devices to Logic Pro, which acts as the master.
Every time you start, a Song Position Pointer (SPP) message is also sent. Because not all devices can process SPP, the MIDI system real-time Continue message is also sent. The exception is when you start at position 1 1 1 1. In this situation, the real-time Start message is sent.
MIDI Clock can easily be sent with other normal MIDI events (notes and controllers, for example). When using multi-port MIDI interfaces (such as the Unitor8), better timing is achieved by sending MIDI Clock to All ports, rather than to several individual ports.
If MIDI Clock is transmitted to all ports, the events are only sent once from the computer to the interface. If you address individual ports, one event needs to be sent for each port, placing a higher strain on the bandwidth of all ports.
MMC is normally used when Logic Pro is running as a slave to an external master (such as an ADAT), and you want to control the external master’s transport functions from Logic Pro. Logic Pro therefore acts as MMC master and MTC slave simultaneously. If you want to use the external master’s transport controls, you don’t need to use MMC. In this situation, Logic Pro follows the MTC master as a slave. You can also use MMC to place tracks on the MMC slave device into Record-Enabled mode.
Logic Pro recognizes these commands when listening to MMC Input:
Play
Deferred Play
Stop
Deferred Play is a special command for mechanically slow synchronization slaves such as reel-based tape recorders. Rather than having the machine play immediately, it is asked to reach the desired SMPTE position before playback is started. There is no noticeable difference in the response of Logic Pro to the Play and Deferred Play commands, as Logic Pro can locate to any position almost instantly.
Logic Pro ignores these messages when incoming external MTC (MIDI time code) commands are detected.
Logic Pro also obeys Full Frame Messages, and sets the playhead to a new location, without starting playback. Once again, incoming MTC data has higher priority, if conflicting information is received.
Some synchronizers send Full Frame Messages (instead of MTC) to locate the slave device (Logic Pro in this case) to a new position, without implicitly starting playback. This is useful when in Slow Shuttle or Single Frame Advance mode with video machines, because the slave device is perfectly located, without being in playback mode.
The Unitor pane of the Synchronization project settings is used to set the major synchronization parameters for the Unitor8 MIDI interface.
Note: You should only use Refresh mode if you are copying time code.
Long freewheel times can maintain synchronization, even if there are dropouts in the time code, but they also increase the reaction time of Logic Pro after the time code master stops. In practice, you should set a value that is as large as necessary (for sustained operation), and as small as possible (to reduce waiting times).
If the Scan option is enabled, the VITC lines are automatically recognized. You should only enter the lines manually if there are problems with Scan mode.