Preparation and troubleshooting
LumiNode 4: distribution and source control policy
Define inputs, processing and outputs before combining controllers.
Proposed test, scope and alternatives
LumiNode 4 has four configurable DMX ports and six process engines. An engine is not a connector. We propose a source → engine → destination map to separate routing, merging and backup.
Forward, HTP/LTP and Backup serve different goals. Merging is not a rehearsed console takeover; decide whether sources should act together or one should replace the other.
- Preserve profile/version. Record source, protocol, universe, applicable priority, engine, function and destination; check each port direction.
- Test a known signal with one source, then the second independently, without repatching fixtures.
- Enable both during rehearsal and compare against intended policy. Check source selection/priorities and mode before restarting the network.
- For backup, test primary loss and return, recovery behavior and operator responsibility. Record measured timing; two connected consoles do not prove continuity.
Start with your date, venue and approximate needs. We can assess equipment, configuration and operation within an agreed scope.
Do more engines mean more connectors?
No. Size processing and physical connections separately.
Can both sources keep sending?
Only with a defined tested policy. Splitting attributes may require specific patching; do not choose global HTP by habit.
Would a simpler node work?
For single-source conversion without merging/adaptation, we can compare options by ports, protocol and support.
What starts a proposal?
Date, venue, controllers and intended failure behavior. We can assess node, network, setup and operation without a final plan; scope and availability require confirmation.