Table of Contents
Advertisement
Master/Slave Modes
This section of the addendum elaborates on the section in the manual titled "Master/Slave
Configuration" beginning on page 3-3.
Master/Slave Modes and Preset Programming
Recall from the section titled "Preset Mode Programming" on page 4-45 of the manual that a preset
consists of the master dim level along with the master delay/audio value and any modulation effects
(color, gobo, dim or size). Because master and slave controllers are each programmed separately, it
is possible for the master controller to have a different master dim level than any of the slave
controllers.
When the preset is fired, the slave's dim level will be recalled and used by the slave. The master
controller does not store the dim level of any of its slaved controllers. However, when the master
dim level is changed on the master controller, that dim level is sent to all slaved controllers as the
new dim level. For example, if the slave's preset master dim level is lower than the master dim
level of the master controller, the light level of the slave will rise to that of the master controller.
If the same master dim levels are stored in the presets, dimming will be consistent between a master
and any slaves.
Master/Slave/Neither Modes and MIDI Commands
This section explains how selecting master, slave or neither for the controller affects the way the
controller passes MIDI commands.
Configuring the controller as a master is useful for controlling other Universal controllers, and for
outputting data to some sort of MIDI data capture system for later playback and control of the
Universal controller.
When configured as a master, the controller will Out all MIDI data.
When the controller is configured as a slave or as neither a master or a slave, it will Thru all MIDI
data. The Universal controller does not Merge data.
(Remember to take the controller out of the "master" mode when you want to control it from a
playback system.)
Addendum UN-1
Page 7
Advertisement
Table of Contents
