City Theatrical Multiverse SHoW Baby

Blue can indicate any advanced ID absent from the button table.

1. Read the actual SHoW ID through RDM and compare both ends. Matching LED colors alone are insufficient.
2. Check compatible ID family and band; a Multiverse receiver setting is not established by a number used in Neo mode.
3. For Multiverse, also match SHoW Key and the relevant universe. Then check the connected light’s address and personality.

Each SHoW Baby transports a universe; multiple sources need a radio plan.

1. List each transmitter and its SHoW ID. Do not put independent transmitters on the same ID to create different universes.
2. Changing light addresses does not separate radio transmissions. Different SHoW Keys on the same ID are not the manual’s solution either.
3. Design compatible IDs and receivers for each link. When using error correction, check its slot reduction before assuming a full universe remains available.

Separate the radio link from the DMX line and RDM traffic.

1. Compare a known fixture and cable, then check termination and connectors. On a transmitter, connecting OUT removes IN’s automatic termination; the continuing chain needs final termination.
2. RDM Traffic controls downstream device traffic. The manual recommends disabling it for production after configuration because some devices do not handle it correctly.
3. Test signal loss in a safe area: the receiver stops emitting data, but the final look depends on each light’s DMX-loss setting. Do not assume universal blackout.

One transmitter can serve several compatible receivers in a single-universe system. The proposal depends on positions, DMX branches and required universes, not fixture count alone.

1. List source, receivers and fixtures by area; check the radio family and actual IDs before deciding what equipment is missing.
2. We can assess receivers by area with local DMX distribution, or a wired route. Send a sketch, the models you know, and what your production supplies. GLMedia can quote the required equipment, installation, configuration, link testing, and operation within the agreed scope. The proposal details power supplies, antennas, adapters, local distribution, and services, and confirms the model, quantity, and availability.

Compare permitted routes, access and actual link conditions. Radio can avoid some data runs, but does not remove power, mounting or system testing.

1. Test final positions and rehearse loss and return with each fixture’s intended DMX-loss behavior; retain manual environment and antenna limits.
2. We can compare radio, wired, or mixed distribution. Share obstructions, access, and the show’s continuity needs; we propose checking range, stability, and recovery at the planned positions before selecting the solution.

No. P/N 5900 transports DMX/RDM data; it is not a dimmer and does not power the lamp. The assembly needs power and a control device suitable for the load, as well as a compatible data path.

1. Send photos and labels of the lamp or LED tape and its power supply or controller, voltage, power consumption if known, location, whether it moves and the required scene changes. A qualified person must assess the actual assembly; DMX capability or a similar connector alone does not confirm compatibility.
2. We can assess a link completing an already confirmed control system, a fixture with compatible integrated control, or a wired solution where viable. Power, load control, radio, mounting, programming, and the responsible operator are identified as parts of the scope. Rehearse intensity, transitions, and signal loss/return with the set in its planned positions and, if it moves, along its actual route. Agree on the intended operating duration and check each light’s state after data loss.