Midas HERITAGE 4000, Руководство оператора

Страница: 57 / 78

Note 1
All scene memory information remains local to the console so when saving or loading memories to or from
the console by either computer file or midi sysex dump, each console must be done individually. When
setting up a multiple console system it is recommended that programming is done from the start with all
consoles linked. This is to avoid recalling a scene that does not exist on a slave console. If this is done you
will see a warning message on the Master indicating that the scene does not exist and prompting for
confirmation at which point the master will recall the required scene but the slave will remain on the last
existing scene recalled.
MIDI may only be stored locally on a console, if you wish to program midi outs on slave console you must
first make this the master or stand alone ( this will be described later) and then program your midi out
messages as normal.
Note 2
As the Solo add and Clear function of the Heritage 1000 are controlled differently to that of the 4000, 3000
and 2000. The solo CLR and ADD functions are not linked and must be triggered locally on any 1000 linked
into a system.
Press the SYSTEM menu and using the UP and DOWN keys scroll to CONS then press CONFIRM.
Using the UP and DOWN keys select either Master or Slave then Press CONFIRM.
You will then be prompted to choose the ID number of the console using the UP and DOWN keys you have a
choice of ID 1 to 8. No two consoles in the same system may have the same ID.
Pressing CONFIRM will then synchronize the console with the system.
Note When a console is in slave mode CONS is the only item of the SYSTEM menu that can be accessed. If a
slave console is reconfigured to be a master it will automatically make the original master console a slave
when the CONFIRM button is pressed.
Switching a Console to Master or Slave:
Automation and Linking Automation and Linking
Operators Manual
- Page 52