Situation 1:
Desk "Matster" on Stage, Desk "Remote" at FoH position, ability to have 1 desk operate like a glorified remote mixing console. Ability to change ALL mixing and routing parameters from the Second Remote Desk, which would eliminate AES50 dropouts over LONG cable runs. Keeping all Audio Processing and I/O on Stage.
DAW Remote - Often, an Unused button on the X32 for Live Environments might be a good candidate for this.
Situation 2:
Desk 1 full size surface as mixer
Desk 2 Rack Mount as fx processor
Link 2 desks with AES50 (48 Ch) use Desk 2 as a dedicated set of FX insert points. Unknown how hard it would be to set each channel to have an "external" insert point or if this IO routing would be limited. One feature the A&H SQ series has over the X32/WING is the ability to use any of the Desk IO as channel inserts on every channel, not limited to the 16 ST FX Slots.
Situation 3:
Desk 1 Leader
Desk 2 Channel Count Expander
Desk 1 is the control surface and has visibility of ALL channels across 1 or more desks, Desk 1 would be able to add Desk 2's channels to it's surface and interact as if that channel was native. Use AES50 to take all BUS feeds and MAIN / MATRIX and sum them together across the two desks (this would take a lot of IO), on the WING I have achieved this using the AUX INPUTS to route audio from one desk to another. Both desks would have to have the same BUS,MAIN,MATRIX layout and setup.
16,4,8 = 56 audio lines for a WING, I would suggest not using MATRIX in this design to keep the paths from 2 to 1 less than an AES50's worth of IO
Some obvious limitations would be things like Audio Key Source for Gates and Compressors you wouldn't be able to access channels from across the surfaces for this function. QL and CL had similar limitations that you could only access in banks of 8. Mixed a number or orchestras and 40 ST channels still a little bit of a limitation.
Setup Menu:
Remote Desk IP / URL
Passwords
High Bandwidth Mode (Copper/Fibre), all data all the time.
Low Bandwidth Mode (WiFi...) no RTA, slower metering updates etc.
Being able to Route the SOLO bus over AES50 back to the Remote Console or over AoIP
Being able to route Remote Audio Channels - VOG, VTs, BGM from Remote Desk to Master desk.
It would be AMAZING if the type of desk didn't matter, i.e. WING at FoH and X32 Rack / WING Rack on stage.
This would allow for AES50 lines to be cut and for Audio to still flow.
A big UPS and a WiFi Router and you have a portable FoH mixing console.
Situation 1:
Desk "Matster" on Stage, Desk "Remote" at FoH position, ability to have 1 desk operate like a glorified remote mixing console. Ability to change ALL mixing and routing parameters from the Second Remote Desk, which would eliminate AES50 dropouts over LONG cable runs. Keeping all Audio Processing and I/O on Stage.
DAW Remote - Often, an Unused button on the X32 for Live Environments might be a good candidate for this.
Situation 2:
Desk 1 full size surface as mixer
Desk 2 Rack Mount as fx processor
Link 2 desks with AES50 (48 Ch) use Desk 2 as a dedicated set of FX insert points. Unknown how hard it would be to set each channel to have an "external" insert point or if this IO routing would be limited. One feature the A&H SQ series has over the X32/WING is the ability to use any of the Desk IO as channel inserts on every channel, not limited to the 16 ST FX Slots.
Situation 3:
Desk 1 Leader
Desk 2 Channel Count Expander
Desk 1 is the control surface and has visibility of ALL channels across 1 or more desks, Desk 1 would be able to add Desk 2's channels to it's surface and interact as if that channel was native. Use AES50 to take all BUS feeds and MAIN / MATRIX and sum them together across the two desks (this would take a lot of IO), on the WING I have achieved this using the AUX INPUTS to route audio from one desk to another. Both desks would have to have the same BUS,MAIN,MATRIX layout and setup.
16,4,8 = 56 audio lines for a WING, I would suggest not using MATRIX in this design to keep the paths from 2 to 1 less than an AES50's worth of IO
Some obvious limitations would be things like Audio Key Source for Gates and Compressors you wouldn't be able to access channels from across the surfaces for this function. QL and CL had similar limitations that you could only access in banks of 8. Mixed a number or orchestras and 40 ST channels still a little bit of a limitation.
Setup Menu:
Remote Desk IP / URL
Passwords
High Bandwidth Mode (Copper/Fibre), all data all the time.
Low Bandwidth Mode (WiFi...) no RTA, slower metering updates etc.
Being able to Route the SOLO bus over AES50 back to the Remote Console or over AoIP
Being able to route Remote Audio Channels - VOG, VTs, BGM from Remote Desk to Master desk.
It would be AMAZING if the type of desk didn't matter, i.e. WING at FoH and X32 Rack / WING Rack on stage.
This would allow for AES50 lines to be cut and for Audio to still flow.
A big UPS and a WiFi Router and you have a portable FoH mixing console.