Alcorn Mcbride V+ series, Руководство пользователя

Страница: 65 / 276

WinScript User’s Guide
4-27
W
inS
cr
ipt
G
u
ide
Jam Sync Mode
If a sequence is in this mode, and a timecode jump is detected, the sequence will
‘scrub’ to the location that matches the new time. This is done by rewinding the
sequence to the first event, and then scrolling through the event list until one
with an equal or higher timestamp is found.
PROS – The timecode can scrub back and forth, and the sequence will find the
proper position. This drastically reduces the development effort in timing out
events in long sequences, and makes it easier to skip or redo things during a
show.
CONS
– Since events are not actually executed while the sequence is scrubbing,
conditional jumps (ie. goto, ifon, etc.) should not be used in this mode.
Note - Once a sequence in Jam Sync Mode has been started, it will never stop
on its own. A Reset command must be issued by the script or external
command.
Reset Mode
Unlike Jam Sync Mode, there are a couple of circumstances that can cause a
sequence in Reset Mode to stop executing. They are the following:

When the last event in the sequence is processed.

When a timecode jump is detected.
Once either of these conditions occurs, the sequence can only be started again if
the timecode is below the start time AND a start sequence event is executed.
PROS
- This mode is very useful for sequences that must execute from start to
finish without the possibility of skipping any events. It is also good for critical
sequences that are not expecting the timecode to drop or jump.
CONS
– Although this mode causes the sequence to precisely chase timecode,
this type of sequence cannot be scrubbed.
Note
– Since they do not apply to chasing timecode, both of these modes ignore
the Loop and Restart options. If you enable these options, the compiler will
issue a warning and then disable these settings.