6.0

Synchronization
268
with many MTC errors itself, you should nevertheless
check the quality of your SMPTE signal, as well as other
potential sources of error.
MTC Interpretation: Because the MIDI standard only
supports four of the possible six time code formats (the 30
fps and 29.97 fps formats cannot be differentiated),
MAGIX midi studio generation 6 has to decide which for-
mat is “intended”, when it encounters incoming time
code:
In other words, the much more commonly used 29.97 fps
and 30 drop fps formats are used in preference to the un-
common 30 fps and the virtually-unheard-of 29.97 drop
fps formats.
However, you can manually set the format from the
Tempo List editor to whatever you like: for example to con-
vert material to 30 fps for black and white TV transmis-
sion in the NTSC format.
Receiving MIDI Clock/SPP: Sync via MIDI Clock/SPP
is the most accurate method, if MAGIX midi studio gen-
eration 6 is being synchronized to a bar-referenced mas-
ter.
MIDI Clock has a resolution of 24 PPQN (pulses per quar-
ter note), while MAGIX midi studio generation 6 has an
internal resolution of 960 PPQN (some 40 times more ac-
curate!). For this reason, MAGIX midi studio generation 6
has to interpolate the 39 steps between two incoming
clock impulses itself.
If you are bothered by small variations in timing between
master and slave, you can improve the relationship when
in external sync, by entering the expected tempo changes
from the master into MAGIX midi studio generation 6’s
internal tempo list as well.
Even if you don’t take this step, the sync should hold up
fairly well, as long as you avoid large deviations, such as an
internal setting of 200 bpm , with an external tempo of 40
bpm.
Continue Event: When a MIDI Continue Event is received,
MAGIX midi studio generation 6 doesn’t leap to the last
incoming MTC format is interpreted as
24 fps 24 fps
25 fps 25 fps
30 drop fps 29.97 drop fps
30 fps 30 fps