1. Why facade pitch is frequently mis-specified

Three different questions are often collapsed into one: Can a viewer distinguish individual light points? Can the grid reproduce the intended content? Can the control and electrical system support the resulting pixel count? A smaller pitch may improve spatial resolution, but it also increases fixtures, addresses, data ports, power branches, connectors and service points. A larger pitch reduces infrastructure, yet may make lettering, logos or diagonal motion visibly coarse.

Root cause: teams select from a product catalogue before writing a content-and-viewing brief. The correct order is viewing zones → content class → required grid → fixture/pitch candidate → control/power architecture → mock-up.

2. Technical model: convert physical pitch into angular pitch

For a pitch p and viewing distance D, the angular spacing is:

NCBI's Webvision explains that a critical detail for 6/6 (20/20) acuity subtends one minute of arc [S4]. That clinical high-contrast reference does not establish the acceptable pitch of a colored, moving outdoor facade. Brightness, contrast, haze, viewing angle, motion, surrounding light and the size of the content feature all change perception. Use the angular calculation to compare options, not to bypass a mock-up.

Worked angular example

3. Calculate the actual facade resolution

For a rectangular grid, use installation dimensions and center-to-center spacing:

• columns = floor(facade width ÷ horizontal pitch) + 1
• rows = floor(facade height ÷ vertical pitch) + 1
• total controlled pixels = columns × rows

24 m × 12 m facade example

At 250 mm horizontal and 500 mm vertical spacing: 97 columns × 25 rows = 2,425 RGB pixels. The content canvas is therefore only 97 × 25—not a conventional video screen. It can support gradients, waves, large symbols and low-resolution motion, but detailed text should not be promised without a content test.

4. Translate pixels into control capacity

ESTA's DMX512-A guide identifies 1–512 channels per universe [S3]. In a simple direct RGB channel model, one pixel consumes three channels; RGBW consumes four. Real SPI controllers and gateways may map pixels differently, so controller port limits, protocol, frame rate and fixture IC remain approval items.

These figures describe address capacity, not guaranteed performance. Network throughput, gateway capacity, SPI port pixel limits, cable length and refresh-rate targets must be verified with the selected controller documentation.

5. Product references: what the published pitch actually tells you

6. Why display-screen pitch rules are only a benchmark

Christie's direct-view LED white paper publishes pitch-to-distance estimates and labels them as guidelines [S5]. Those products are dense, regular video walls. Architectural pixel tubes may have non-square spacing, gaps, transparent backgrounds, different emitting areas and facade geometry. Use display guidance as a comparison reference—not as evidence that a sparse facade will reproduce the same image quality.

7. What not to choose

• Do not choose the smallest pitch when the content is only slow color movement and the added ports, power branches and maintenance points have no visual benefit.
• Do not choose a coarse pitch when the approved content contains small text, thin logos, faces or high-frequency video detail.
• Do not choose a square grid by habit when facade mullions force different horizontal and vertical spacing; render content at the true non-square grid.
• Do not approve from a desktop simulation alone. Camera exposure and monitor scaling can hide glare, dark gaps and motion artifacts.
• Do not freeze the fixture before the controller. The IC, port capacity, signal segmentation and failure behavior are part of the product-system decision.

8. Failure impact and maintenance design

Ask whether one failed pixel, tube, data branch, power supply or gateway affects a single element, a downstream chain or a complete zone. Document isolation points, spare addresses, accessible connectors and replacement mapping. For long facades, segment the system so one fault does not remove an entire elevation. Exact break-point recovery behavior is product- and IC-specific and remains 待确认 until the approved wiring diagram and controller test are available.

9. Evidence ledger

10. FAQ

Is there one universal viewing-distance formula?

No. Angular pitch is calculable, but acceptable image quality also depends on content, contrast, brightness, atmosphere, angle and motion.

Can 20/20 visual acuity determine the final pitch?

No. The one-arc-minute reference describes a controlled acuity condition [S4], not a performance guarantee for outdoor colored pixels.

How many RGB pixels fit in one DMX universe?

In a simple three-channel model, 170 complete RGB pixels use 510 of 512 channels. Confirm the actual fixture personality and gateway mapping.

Should horizontal and vertical pitch be equal?

Not necessarily. The building structure may require a non-square grid, but content must be rendered and reviewed at that true aspect.

What must a sample test include?

Final pixel spacing, emitting surface, night ambient light, representative content, nearest and principal viewing zones, off-axis views, camera behavior and service access.

Who authored and reviewed this guide?

Author: 待确认 · Technical reviewer: 待确认. Replace these fields with verifiable names, positions and profile links before publication.