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.
How can I identify which source is holding an output up?
During a controlled rehearsal, test each source separately at the same destination, then both together. If each responds correctly alone but the combined result differs, compare selected sources, priorities and engine mode against the intended policy before changing patch. Record each source value and the destination value. HTP/LTP and Backup serve different goals; global merging does not replace a backup design. If an isolated source also fails, check its source → engine → output path first.
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.
Related guides
Help us improve this guide
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.