Overview
Multi-Surface mode allows the connection of up to 4 Surfaces to a single DM MixRack or 2 Surfaces to a single CDM MixRack.
Any combination of C Class and S Class Surfaces can be used in a Multi-Surface system. Dual-cable redundancy is available on S Class Surfaces and can be added to C Class Surfaces via a fibreACE module.
Example Applications
FOH/MON - Two Surfaces can be configured to provide a FOH/MON split.
Surface Mirroring - Multi-Surface systems can be used to provide Surface mirroring which could be implemented in a number of scenarios such as additional Surface locations (i.e. for MON use with a B Stage) or for a backup Surface.
Multi-Room Install - Multiple Surfaces can be employed for install applications where a number of Surfaces – each with their own discrete channel range and outputs - are required to control multiple conference or meeting rooms.
Sub-Mixing - A Multi-Surface configuration can also be utilised in applications where it is desirable to have more than one engineer working on the same mix simultaneously; for instance, performances with a very high channel count where traditionally a dedicated sub-mixer would have been used.
Network Configuration
All connected Surfaces require a discrete IP address before connection, for example:
Surface 1: 192.168.1.81
Surface 2: 192.168.1.82
Surface 3: 192.168.1.83
Surface 4: 192.168.1.84
Surface IP addressing can be changed on the Surface /Config / Network page as detailed in Section 10.12
Connection
The Primary Surface connects to the internal gigaACE socket on the MixRack. This can be a dual-cable redundant connection with a DM MixRack and S Class Surface.
Secondary Surfaces connect to gigaACE or fibreACE I/O modules installed in the MixRack. Secondary Surfaces require a fibreACE I/O module if using an optical connection.
Each I/O module supports one Secondary Surface connection - this can be a dual-cable redundant connection if connecting to an S Class Surface, or to a C Class Surface fitted with a fibreACE module.
gigaACE I/O Module Configuration
All gigaACE I/O modules in the MixRack connected to Secondary Surfaces require the front panel Control Network Bridge switch to be in the ON position.
🛈 gigaACE modules installed in a Surface cannot be used for connection to a MixRack.
fibreACE I/O Module Configuration
fibreACE modules in the MixRack require the front panel Control Network Bridge switch to be in the ON position, and the Mode switch to be set to Copper Active or Optical Active mode depending on the cable used.
fibreACE modules installed in Secondary Surfaces and used for the MixRack connection require the front panel switch to be set to Convert.
PAFL
Each Surface can have a dedicated PAFL bus which is assigned via Surface / Audio / PAFL as detailed in Section 10.7. PAFL busses can be added or removed via MixRack / Config / Mixer Config as described in Section 9.1.
🛈 The RTA function is fixed to PAFL bus 1
🛈 Wedge and IEM strips are fixed to PAFL bus 1
🛈 The headphones socket on the MixRack is fixed to PAFL bus 1
🛈 Delay, PFL Trim and Ext Input to PAFL Source are available for PAFL busses 1 and 2
Surface I/O
- I/O Modules – I/O modules installed in the Primary Surface are accessible throughout the system. I/O modules in Secondary Surfaces are not accessible.
- Analogue & AES – Analogue and AES I/O on Primary and Secondary Surfaces are accessible throughout the system.
- DX Expanders – DX Expanders connected to Primary and Secondary Surfaces are accessible throughout the system.
Shows
In a typical Multi-Surface system, each Surface would store and recall its own Show independently of other Surfaces. Although the MixRack data would be the same in each Surface’s Show file, the Surface data would be unique to the Surface that stored the Show.
When loading Multi-Surface shows, the last user to store the Show would recall the Show as normal. Additional operators would recall their Shows in Surface Only Recall mode to prevent making any changes to the MixRack configuration.
🛈 If a Show stored on the FOH Surface is recalled on the MON Surface, it will recall the FOH Show memories and Scene memories including the FOH Surface configuration (i.e. strip layouts)
🛈 Enable Allow Surface Only Recall by pressing Setup when on the Utility / Memory / Show Manager page – see Section 11.1 for more information on Show Manager.
Scenes
In a typical Multi-Surface system, each Surface would store and recall its own Scene(s) independently of other Surfaces.
The Surface Roles menu allows the user to define a Scene Range for each Surface Role and can be accessed by pressing Setup whilst on the Surface / Control / Surface Prefs page.
For example, in a FOH/MON Multi-Surface configuration, the FOH Surface Role could be assigned to Scenes 001-249 and the MON Surface Role could be assigned to Scenes 250-500.
As a Scene also contains MixRack settings it would be typical to configure Role Filters to block unwanted Surface and MixRack parameter changes when recalling a Scene.
🛈 If a Scene stored on the FOH Surface is recalled on the MON Surface, it will recall the FOH Surface memories (i.e. FOH strip assignments etc.) in addition to all MixRack settings.
Surface Roles
Up to 4 Surface Roles can be configured, and each Surface Role contains a scene range and a Role Filter.
In a typical FOH/MON Multi-Surface configuration, the Role Filters would be configured on each Surface to allow relevant changes when a Scene 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 Role Filters for each Role.
Firmware Update
In a Multi-Surface system, Surfaces should be updated individually, either connected as a Primary Surface directly to the MixRack gigaACE socket or with no MixRack connected via the Connection Failed screen on startup.
🛈 Performing a firmware update with Surface(s) connected to the MixRack via I/O module(s) is not supported.
Patching between Surfaces
There are several scenarios where patching inputs between Surfaces is desirable.
For example, signals may need to be patched between Surfaces via Tie-Lines. This can be useful for “shout” communications between engineers when it is not desirable to consume an input processing channel.
As Secondary Surfaces are connected to the MixRack via gigaACE or fibreACE I/O modules, patching between Surfaces is performed on the I/O screen via the MixRack I/O Port tabs.
To patch the signals use the Tie Lines tab in the I/O screen and refer to the gigaACE I/O module channel mapping for the relevant gigaACE I/O channel numbers.
🛈 Primary Surface I/O can only be patched to Input Channels from the Primary Surface itself.
🛈 All Surfaces have the ability to change the patching of I/O modules fitted to the rack. Care should be taken to prevent accidental changes to the patching of gigaACE I/O modules that are being used for connection to Secondary Surfaces.
gigaACE I/O Module Channel Mapping
All channel mapping is from the perspective of the MixRack I/O modules.
Patching is performed on the I/O page via the MixRack I/O Port tabs.
|
gigaACE Channel |
Output |
| 1 | Surface Analogue Output 1 |
| 2 | Surface Analogue Output 2 |
| 3 | Surface Analogue Output 3 |
| 4 | Surface Analogue Output 4 |
| 5 | Surface Analogue Output 5 |
| 6 | Surface Analogue Output 6 |
| 7 | Surface Analogue Output 7 |
| 8 | Surface Analogue Output 8 |
| 9 | Surface Digital Output 9 |
| 10 | Surface Digital Output 10 |
| 11 | Surface Digital Output 11 |
| 12 | Surface Digital Output 12 |
| 13 | Surface Digital Output 13 |
| 14 | Surface Digital Output 14 |
| 15 | PAFL L |
| 16 | PAFL R |
| 17 | DX Outputs 1 |
| 18 | DX Outputs 2 |
| 19 | DX Outputs 3 |
| 20 | DX Outputs 4 |
| 21 | DX Outputs 5 |
| 22 | DX Outputs 6 |
| 23 | DX Outputs 7 |
| 24 | DX Outputs 8 |
| 25 | DX Outputs 9 |
| 26 | DX Outputs 10 |
| 27 | DX Outputs 11 |
| 28 | DX Outputs 12 |
| 29 | DX Outputs 13 |
| 30 | DX Outputs 14 |
| 31 | DX Outputs 15 |
| 32 | DX Outputs 16 |
| 33 | DX Outputs 17 |
| 34 | DX Outputs 18 |
| 35 | DX Outputs 19 |
| 36 | DX Outputs 20 |
| 37 | DX Outputs 21 |
| 38 | DX Outputs 22 |
| 39 | DX Outputs 23 |
| 40 | DX Outputs 24 |
| 41 | DX Outputs 25 |
| 42 | DX Outputs 26 |
| 43 | DX Outputs 27 |
| 44 | DX Outputs 28 |
| 45 | DX Outputs 29 |
| 46 | DX Outputs 30 |
| 47 | DX Outputs 31 |
| 48 | DX Outputs 32 |
|
gigaACE Channel |
Input |
|---|---|
| 1 | Surface Analogue Input 1 |
| 2 | Surface Analogue Input 2 |
| 3 | Surface Analogue Input 3 |
| 4 | Surface Analogue Input 4 |
| 5 | Surface Analogue Input 5 |
| 6 | Surface Analogue Input 6 |
| 7 | Surface Analogue Input 7 |
| 8 | Surface Analogue Input 8 |
| 9 | Surface Digital Input 9 |
| 10 | Surface Digital Input 10 |
| 11 | Surface Digital Input 11 |
| 12 | Surface Digital Input 12 |
| 13 | DX Input 1 |
| 14 | DX Input 2 |
| 15 | DX Input 3 |
| 16 | DX Input 4 |
| 17 | DX Input 5 |
| 18 | DX Input 6 |
| 19 | DX Input 7 |
| 20 | DX Input 8 |
| 21 | DX Input 9 |
| 22 | DX Input 10 |
| 23 | DX Input 11 |
| 24 | DX Input 12 |
| 25 | DX Input 13 |
| 26 | DX Input 14 |
| 27 | DX Input 15 |
| 28 | DX Input 16 |
| 29 | DX Input 17 |
| 30 | DX Input 18 |
| 31 | DX Input 19 |
| 32 | DX Input 20 |
| 33 | DX Input 21 |
| 34 | DX Input 22 |
| 35 | DX Input 23 |
| 36 | DX Input 24 |
| 37 | DX Input 25 |
| 38 | DX Input 26 |
| 39 | DX Input 27 |
| 40 | DX Input 28 |
| 41 | DX Input 29 |
| 42 | DX Input 30 |
| 43 | DX Input 31 |
| 44 | DX Input 32 |
🛈 All Surfaces have the ability to change the patching of I/O modules fitted to the rack. Care should be taken to prevent accidental changes to the patching of gigaACE I/O modules that are being used for connection to Secondary Surfaces.