Jands HOG 1000, Руководство по эксплуатации

Страница: 51 / 126

Advanced Programming
••••
45
Advanced Programming
This chapter covers the more complex aspects of programming. It begins by explaining the concept of
tracking in greater detail than previous chapters. Understanding the reasoning and logic of tracking is the
first step to mastering the console.
Tracking
The HOG 1000 and 500 are tracking consoles – meaning it only saves programmed changes and not entire
states. This concept directly impacts on how you program your show; not understanding how tracking
works can lead to confusion and mistakes.
Under normal circumstances, recording a new cue on the console only stores information for the parameters
you adjusted since the last record command. For example, if only the colour wheels were adjusted before
recording, the cue won’t contain information for intensity, position, or beam.
There are two advantages to using this system. One is that the storage of cues is extremely efficient, since
programmed values are not repeated throughout a cuelist. The other is flexibility during playback. Some
shows are programmed with only one parameter type in each cue or sequence, allowing them to be
combined with each other in different ways to achieve a wide selection of looks. In other situations, a single
parameter override needs to be manually triggered from a different Master at varying points during a show.
This would not be possible if the console always stored values for each parameter.
However, this system can occasionally be confusing, and sometimes recorded cues don’t appear the same
during playback as they did while in the programmer. This problem usually one of two causes:
1) Active cues on the playback masters while recording. The look on stage is a combination of the
programmer and the playback masters, but only what’s in the programmer is recorded in the cue. Later,
when the cue is played back, it will look different if the cues that were active while recording are now
turned off.
2) Active cues during playback outputting values for parameters not included in the recorded cue. If a
Cyberlight is programmed with only intensity, colour, and focus information, an iris setting will not be
included in the cue. If this cue is activated after another cue has put the same fixtures in a tight iris, the iris
will remain tight even though it was open when recorded. This is because no information was programmed
for iris since it was not touched.
An Example of Tracking
Looking at an example will help make sense of tracking.
Cue Action Cue Contents Output
1 2 3 4 5 1 2 3 4 5
1 1 @ Full FF FF
2 2 @ 50 50 FF 50
3 3 + 5 @ 80 80 80 FF 50 80 80
Tracking Off:
4 4 @ Full FF FF 50 80 FF 80
5 1 Thru 3 @ 70 70 70 70 0 70 70 70 0 80
The first column is the cue number. The second column shows what programming activity takes place in
that cue (assuming
ENTER
and
Record
). The third column (Cue Contents) shows what actually is
recorded in the cue. The fourth column (Output) shows the resulting state of the cuelist as the cues are
executed (this assumes that
Maintain State
has been kept as the default setting in the cuelist options
window).