Problem: EOS lacks co-processing and the ability to expand past 25k output. LED pixelmap rigs and cell controlled moving lights can surpass this quickly.
Current Solution: Run two primaries on offsets with midi or sACN triggers.
Proposed solution: Streamline the multisystem output with sync'd cues and subs directly through the console. Operators would still design the network so that each additional console controls the additional units similar to running a multi primary setup. It would share all overall timing information and triggering of subs and cues.
Hypothetical setup: Console 1 controls 30 universes of moving lights and conventionals, Console 2 controls 48 universes of pixels.
Scenario #1: Console one creates and saves cue 1/1, console 2 designs pixel look and updates 1/1 with their data, timing from console 1 is automatically shown/created for console 2. Either console can play through cues.
Scenario #2: Console 2 creates subs with various pixelmaps and singular effects. Console 1 can bump those subs while running the show in a busking setup. Console 1 doesn't hold any sub data but the trigger is sent network wide.
Of course having both consoles see each others data is useful, I'm just unaware if that changes the processing power of the consoles, or if it's just what is patched. Similar to processing offline vs online. I feel that users that are hitting the output cap can handle dealing with the basic logistic constraints, and this would be leaps faster and more useful than the current setup. The setup of additional consoles to unlock more use is also in line with current EOS licensing. Backups would have to be assigned or not an option in this setup.
