EZSequence Layout Mapping, Singing Faces and Tune-To Signs
EZSequence adapts a sequence to the layout supplied to EZRGB. The useful starting question is: “Does the service have the same display I am about to play?” A fresh render cannot correct an outdated model list, an unintended singing role or a physical port assignment that changed after the layout was uploaded.
EZRGB provides design and sequence services; EZPlayer runs the resulting show. You can also build and sequence a local show in xLights. Choose that workflow in local xLights setup, or use the Light Show Designer guide when starting from EZRGB’s design tools.
Official reference: EZRGB services; Getting sequences into EZPlayer.
Three kinds of mapping need to agree
Scroll sideways to see all columns.
| Layer | Question it answers | Example check |
|---|---|---|
| Creative role | What should this prop do in the sequence? | Which face sings lead? Should a sign remain informational? |
| Channel and network plan | Where does the rendered data belong? | Do the render and current controller configuration use the same layout? |
| Physical connections | Which output and pixels receive that data? | Does the named model actually occupy the planned controller port? |
Mattos recommends diagnosing a mismatch at the layer that explains it. A singer on the wrong face suggests a role choice. The correct effect on the wrong physical prop suggests channel or connection mapping. A completely absent prop needs both its layout inclusion and its output path checked.
Official reference: Controller Port Map; EZRGB mapping help.
Supply a current, consistent layout
For an existing xLights display, the relevant pair is xlights_rgbeffects.xml and xlights_networks.xml from its working show folder. Before supplying them, save the intended layout and verify that both files come from the same show. Keep a dated copy of that submitted pair so a later result can be compared with what the service received.
Use a short review sheet: model name, pixel count, physical location and intended role. Add unusual orientations or props that should stay outside sequence mapping. This is a Mattos planning aid, not another required EZRGB import file.
Official reference: xLights configuration files.
Connected EZPlayer shows also have a layout owner. In xLights-managed mode, use the documented local-layout push workflow. In cloud-managed mode, make the authoritative changes in the cloud; fetching that layout can replace local edits. Confirm the mode before making changes in two places.
Official reference: Cloud layout ownership and controls; Full cloud control.
Assign faces, static props and signs deliberately
In EZRGB, use My Account → My Layout → Edit Layout to review mapping choices. The help page describes singing-role adjustments and model-type overrides for incorrectly recognized props.
Static choices include On White, On Primary Color and State (Static On). None (Skip Mapping) excludes a prop from EZSequence mapping. For a fixed tune-to message, the documented role is Tune To (Matrix).
Review one example song after changing a role. For several singing faces, choose a passage that clearly distinguishes the lead and supporting parts. For a static prop, watch a quiet section and a bright section to confirm that its intended role remains legible.
Official reference: Roles, model overrides and tune-to mapping.
Check the message as well as the model
EZRGB Show Settings includes the show’s frequency and an optional signage message. Enter the intended listener instructions and review the rendered result from the viewing position. A correct model type is only part of the job: the sign also needs the right information and readable presentation.
If another player or a separate process drives the sign, establish which system owns those pixels. Keep a note beside the model so the next layout edit does not accidentally give both systems responsibility for it. The background-lighting guide explains a separate player-side approach and the current blending limitation.
Official reference: Show identity, frequency and signage settings.
Understand what you receive
The normal EZSequence playback result is a rendered .fseq, rather than editable effect blocks. EZRGB also documents an advanced .iseq import workflow from its downloaded package for layering additional work in xLights; this does not expose the original effects.
Official reference: Player files and advanced import.
For cloud-connected EZPlayer, distinguish a purchase or pending render from an installed song. Wait for the sequence to finish processing and downloading, then check the actual playable entry. For a manual download, select the intended FSEQ and its matching audio in Songs. Do not assume an unrelated recording with the same song title has the same timing.
Official reference: Cloud sequence delivery.
Make a change, render, then verify
After adding a prop or changing its pixel count, update the authoritative layout before using new renders. Test a representative song on the real display, including faces, signs and any changed outputs. Keep the last working files until that test passes.
If you need help, capture the model name, intended role, song title, render or download date, and a short description of the mismatch. That evidence makes the next decision concrete: adjust a creative role, correct the layout, or investigate the controller connection.
