iPhone + iPad · Local network

Live control,
without guesswork.

Compose layers, manage signal inputs and monitor a manufacturer-neutral Generic Link or user-configured declarative TCP endpoint from one safe operator workspace.

Abstract signal routes converging into an LED pixel matrix
State synchronized
One operational surface

Everything essential stays close to the operator.

Controls only appear when the connected endpoint declares support. No dead controls and no claims beyond the live capability contract.

Composition

Keep MAIN, PIP selection and source routing together. Draft position, size and scaling before one deliberate Apply.

Inputs

See signal, resolution and frame rate, then manage color, input crop, hot backup and EDID when available.

Presets

Recall, save, overwrite, rename, copy and clear slots with schematic layer summaries and deliberate confirmation.

Display & output

Operate freeze, blackout, patterns, brightness, format, sync, audio routing/mute, redundancy and transitions.

Monitoring

Track input health, output links, primary/backup roles, traffic and the freshness of every snapshot.

Full demo

Explore the complete interface and deterministic fault scenarios without hardware, an account or a cloud service.

Safe by operation

Read first. Unlock deliberately. Never duplicate a write.

LED Processor Control is built for a live environment where uncertainty must disable control, not hide behind a spinner.

1Synchronize
Read identity, capabilities and complete current state.
2Verify and unlock
Controls remain locked until the operator confirms the state.
3Serialize every command
Polling cannot collide with a write.
4Read back uncertainty
A timeout is never retried automatically.
Compatibility, stated precisely

An open endpoint contract—not a hidden device library.

Included in v1

Generic Link

  • Original JSON Lines protocol
  • Reference Server and deterministic simulator
  • Closed, fingerprinted declarative profile imports
  • No accounts, tracking or remote access
Not included

Third-party implementations

No developer-supplied manufacturer protocol, SDK, binary, firmware, brand asset, model profile or downloadable adapter is embedded in the app. Users may provide closed data-only TCP mappings for protocols they are authorized to use. A distributed branded adapter must pass legal, technical, bench and distribution gates first.