What Is LED Pixel Mapping? Layout, Patch and Positions

What is LED pixel mapping?

LED pixel mapping assigns values from a software image, animation or effect to the physical positions of independently controlled lighting pixels. The map connects the logical canvas to the installation through a fixture patch and output-address allocation. It lets an effect follow the intended spatial layout, whether the LEDs form a line, a ceiling grid or a three-dimensional structure.

The pixels in the software canvas and the LED packages in a fixture are not automatically a one-to-one match. A physical control pixel can contain several packages. The map should describe the independent units that the selected fixtures and control mode actually expose.

The patch connects position to control data

MADRIX's Patch Editor documentation describes a virtual LED matrix that records fixture choice, quantity and placement. Its patch settings connect that spatial arrangement to the fixtures' control allocation. Other software uses its own terminology and configuration, but the underlying task is to match content positions with the real installation.

There are two related questions. First, where is a pixel in the composition: its X/Y position, or X/Y/Z position for a spatial layout? Second, where do its control values go: the controller, output, universe, start channel and fixture mode? A plan that answers only one question is incomplete. Correct addresses with incorrect spatial positions can still produce a mirrored or scrambled image.

The diagram pairs six logical positions with six physical groups. Its numbers identify an example patch. They do not prescribe a universal cable order or imply that every controller uses the same addressing convention.

A six-pixel example

Imagine two horizontal rows, each with three independent RGB pixels. The intended canvas order is top-left to top-right, then bottom-left to bottom-right. A test image containing a single bright position should light the corresponding physical group.

Now suppose the lower row is physically chained from right to left. The patch must account for that order, or the lower part of an effect will run in the wrong direction. Software may support a reversed row or an explicit position assignment; the exact method depends on the chosen system. Rearranging a virtual fixture does not physically move a light or increase its control resolution.

These six RGB pixels would use 18 color slots in a simple three-slot-per-pixel mode. That is a data-footprint example, not a recommendation for a power connection or a controller model. A fixture mode with extra functions needs a different allocation.

Resolution, spacing and the intended view

More independent pixels can represent more spatial detail, but the useful resolution depends on the effect and the way people see it. A broad ceiling wave and a recognizable text image demand different layouts. Gaps between strips, fixture orientation, diffuser behavior and viewing distance all influence the result.

The software canvas should reflect the actual geometry closely enough for the intended content. It cannot create a separately controlled position inside a group that the hardware always drives together. Before comparing software features, confirm the pixels per fixture, channel mode and physical spacing.

For a project example that joins the layout with network control and hardware selection, see the MADRIX LED ceiling system. That solution handles the system-planning stage; this page establishes the mapping terms used in the brief.

What to include in a mapping brief

Provide a drawing with dimensions, row and column counts, fixture orientation, independent pixels per unit, intended control order and controller zones. Add the content goal, the chosen software or media server, required color channels and the proposed data protocol. For a 3D installation, describe depth positions and the viewing directions as well as the front view.

Keep physical connection order and logical image order visible in the same patch plan. Include a simple position-and-color check in commissioning so that an addressing error is distinguishable from an effect-design decision. There is no need to assume a universal frame rate or cable distance to establish that relationship.

Use the pixel-project RFQ and BOM template to carry the known layout and control assumptions into a supplier discussion. Unconfirmed fixture modes, channel footprints and output assignments should remain explicit questions until the selected hardware documentation resolves them.