User manual

4REA4 Controller Software User Guide
89
V1.30
16. Appendix E – Multiple Software Controllers
16.1 Sessions
In a typical Multi-Controller system, each Controller computer would store and recall its own Session
independently of other Computers running Controller software. Although the 4REA4 Engine data would be
the same in each Controller’s Session file, the Controller data would be unique to the Controller that stored
the Session.
When loading Multi-Software Controller sessions, the last user to store the Session would recall the Session
as normal. Additional users would recall their Sessions in Control Only Recall mode to prevent making any
changes to the 4REA4 Engine configuration.
 Enable Allow Control Only Recall by pressing Setup when on the Utility / Memory / Session Manager
page – see Section 11.1 for more information on Session Manager.
16.2 Snapshots
In a typical Multi-Controller system, each Controller would store and recall its own Snapshots(s)
independently of other Controllers.
Each Area is allocated its own set of 200 Snapshots
For example, in a 2 Area Multi-Controller configuration, the Area 1 would have Snapshots 1-200 and Area 2
Snapshots 201-400
As a Snapshot also contains Engine settings, it would be typical to configure scopes to block unwanted
Controller and Engine parameter changes when recalling a Snapshot.
16.3 Areas
Up to 4 Areas can be configured, and each Area contains a snapshot range and Area Safe settings.
In a typical Multi-Controller configuration, the Area Safes would be configured on each Controller to allow
relevant changes when a Snapshot recall is performed.
 Changes made to the Mixer Config – for instance adding or removing an AUX, GRP or MTX – would
need to be reflected in the Filters for each Area.