ETC Gio @5

Confirm the station role and local port assignment separately from the fixture patch. A connected Client does not necessarily supply local DMX.

1. Check whether the console is Primary, Backup, Client or Offline, and identify the intended active source. Do not change a live session’s roles merely to see whether a fixture responds.
2. Open Setup > Device > Local Output and identify the connected hardware/port. Compare its starting Address with the patched output address; check port settings and any restart warning.
3. If this is an intentional Client output, review Output In Client Mode, which defaults to disabled. Coordinate the change with the system operator and rehearse the intended route. With a verified cable, test the same fixture before changing its profile or start address.

An online network interface indicates a connection; also check the full lighting-control path and receiver settings.

1. In Setup > Device > Network, inspect the actual connected interface, IP/subnet and protocol enable. Trace the cable and compare the receiver’s input settings with the agreed network plan.
2. Also inspect Patch > Protocols. Confirm Enabled Protocol, intended default protocol, Start Universe and relevant per-universe overrides. An offset can send a correct patch to a different receiving universe.
3. For sACN, compare priorities and multicast/unicast destination choices with the receiving system. Observe data at the receiver, not just a console indicator. If data is present but the device ignores it, investigate its own input/mapping settings; do not copy another model’s IP workaround.

Output count concerns patched addresses. A multiparameter fixture can occupy several addresses while remaining a single control channel.

1. With an empty command line, open About and compare System Count, Patched Addresses and Allowed Output Addresses. A high universe number alone is not proof that the total address allowance is exceeded.
2. In a conventional Primary/Backup arrangement without expansion processing, the lower output count sets the system allowance; the two console counts do not add. Check both proposed host devices before relying on failover.
3. About while networked may show the session allowance rather than that individual desk’s programmed capacity. Verify each device separately during a planned isolated inspection, never by unplugging an active console. If capacity or allowed address ranges are insufficient, preserve the show and resolve the system design before rehearsal.

We can assess a cue list and playback controls suited to the operator. Gio @5’s surface provides access but does not replace agreed cue calls, transitions and responsibility.

1. Send a provisional script or rundown, changes, positions and rehearsal time. Mark called cues and live adjustments; test pauses, repeats and the agreed exit look too.
2. We can quote advance programming, show adaptation, rehearsal and show operation as separate scopes. State which console, file, accessories and personnel your production supplies and what needs solving. GLMedia can assess a partial supply or a prepared package; model, availability, enabled capacity, peripherals and deliverables are confirmed in the proposal. Rental does not imply a ready show file or an operator.

We can assess integration without replacing the whole system. Identify who manages it and which control route and capacity are available.

1. Share an inventory or photos, models/modes, plan or known addresses and venue protocols. Preserve existing files and settings; a screen or network link does not establish useful control at every receiver.
2. We can compare completing existing control with Gio @5 or another suitable configuration. Nodes, cables, accessories and coordination with the local manager must be defined; similar connectors do not guarantee compatibility.

A show-file copy can recover data, but it does not replace a system prepared to take control. An Eos synchronized Backup is a session role; another device holding a saved file is not ready on that basis alone.

1. Tell us what interruption the event can tolerate, who decides recovery, and the available consoles, licenses, versions, fixture library and output paths. Eos sessions have matching requirements between devices; the full system must be reviewed before confirming backup. Include power, network, nodes, physical connections and operator access in the plan.
2. We can assess an independent copy with a reload procedure, a prepared replacement device, or a compatible Primary/Backup session. These are different scopes: preparation, interfaces, rehearsal and personnel are quoted for the continuity required. Rehearse takeover and return with the actual receivers and an agreed test area; a second console does not promise uninterrupted transfer or output from the same ports.