6.2
Slave Mode
Some demanding lighting designs can require more than two universes of DMX.
When multiple CueCore2 units are combined to create a large multi-universe
system there is the need for synchronisation of those CueCore2 devices. The
Slave mode facilitates this. See figure 6.3.
When in Slave mode the CueCore2 is taken over by a master-CueCore2 and
is no longer responsible for its playbacks and scheduling; the master takes care
of this. All the slave requires is to contain the lighting content in its tracks.
The master-CueCore2 will control all its slaves to activate the same tracks and
keep the playback of those tracks synchronised.
It is necessary to put all action-programming in the master-CueCore2. In fact,
the playback information inside the slaves will be overwritten by the master.
The master does this because it stores a copy of its playback-data in each slave to
enable the slave to continue autonomously in case the communication between
master and slave is interrupted.
The logical place for the action lists and action for a master/slave system
is also inside the master, however, it is allowed to place actions in a slave and
they will get executed.
The Slave mode is enabled in the Settings page (See chapter 12, page 66).
Once enabled, the Slave mode is entered as soon as the master connects to the
slave. The Slave mode reverts back to the Stand-alone mode when the master
disconnects or when the slave disables Master/Slave in the Settings page.
6.3
CueluxPro Mode
CueluxPro (see figure 6.4) is a software-based lighting console that is bundled
with the CueCore2. The purpose of the CueCore2 in this mode is to be an
Figure 6.3: Master/Slave setup
35
Need help?
Do you have a question about the CUECORE2 and is the answer not in the manual?