Contact

Production Tool

CuePatch

Build the pixel map, processor outputs, cabling and pack data for an LED wall before a single panel leaves the shop.

Private Validation · Beta Interest

  • macOS & Windows desktop
  • Local project files
  • Brompton · Novastar · Megapixel Helios
  • disguise · grandMA3 · MVR
Contact Us
CuePatch — Builder
The CuePatch Builder window: an outputs and screens rail on the left, three coloured LED surfaces laid out across one 3840 by 2160 output in the centre, and surface colour, screen name and position controls on the right.

Three screens on one 3840×2160 output. The accepted CuePatch capture, running an unsaved local project on ROE Visual Carbon CB5 tiles. Every detail on this page is a region of this same frame.

02

In the build

The wall and the processor argue in one document

A pixel map is only useful if it survives contact with the panel database, the processor budget and the truck. CuePatch keeps all three in the same file, so the map handed to the video engineer matches the cases that ship.

Job — get the wall right

Panel-accurate surfaces, not nominal rectangles

Screens are built from real product specs, so pixel pitch, panel count and physical size stay honest from the first sketch. Multiple surfaces sit on one canvas with per-tile addressing you can read at a glance.

  • 48+ LED tile types covering ROE Visual, Absen, Unilumin, INFiLED, Gloshine and CHAUVET
  • Several screens positioned and aligned on a single output canvas
  • Curved wall builder with configurable radius and panel count
  • Half-tile increments where the product supports them
  • Reference image overlays for design alignment

Boundary CuePatch plans the surface. It does not replace a site survey, a rigging plot or structural engineering.

Detail — output canvas
The CuePatch output canvas showing three LED surfaces side by side, each tile carrying its own grid address from A1 through H10, with per-screen resolution badges reading 1040 by 1664 pixels.

Interface detail from the accepted view — three surfaces on one canvas, every tile addressed, each screen carrying its own resolution badge.

Job — answer the engineer

Outputs and screens stay countable

Outputs are declared with their real processor resolution, and every screen is listed against the output that carries it. The split is visible before anyone patches a fibre, and the numbers under each screen name are the ones the engineer will read back to you.

  • Multi-output mapping with visual screen slicing
  • Cable manager for data runs and signal flow
  • Built around Brompton, Novastar and Megapixel Helios workflows
  • Per-screen names, resolution readouts and master offsets

Boundary CuePatch does not drive processors, send content or control anything live. It produces the document the live systems are configured from.

Detail — outputs and screens
The CuePatch left rail: Output 1 configured at 3840 by 2160 carrying three screens, with HD, 4K and 2K presets, and a screens list naming Stage Right Imag, Stage Left Imag and US Wall with their pixel dimensions.

Interface detail from the accepted view — one declared output at 3840×2160, the three screens assigned to it, and each screen's own pixel dimensions.

03

The safe loop

Define outputs, build the wall, export the show pack

The same document carries the processor truth and the physical truth, so the pixel map, the power figure and the case count never drift apart between departments.

  1. 01

    Define outputs

    Set processor output resolution and add only the outputs the design actually needs. Everything downstream is measured against that budget.

  2. 02

    Build screens

    Place real tiles from the panel database, size the grid in whole or half tiles, and align multiple surfaces on one canvas.

  3. 03

    Map and slice

    Assign screens to processor outputs and split surfaces across outputs with visual slice tools, so the engineer inherits a decision rather than a puzzle.

  4. 04

    Cable and pack

    Work out data runs and signal flow, then turn panel count into road-case and truck figures for the production manager.

  5. 05

    Export

    Emit the images, mesh, media-server and lighting files the rest of the departments need — each as a file of its own, not a screenshot of yours.

Built for

  • Video designers and screens producers scoping a wall during pre-production
  • Video engineers who need the processor map settled before load-in
  • Production managers pricing panel count, power, weight and trucking
  • Shops preparing a repeatable pack for a recurring design

Outside its authority

  • It does not drive processors, send content, or control anything live
  • It does not replace a site survey, rigging plot or structural engineering
  • It does not validate delivered media — that is CueCheck's job
  • It plans LED surfaces; whole-production logistics live in dedicated production-planning tools

04

Interface detail bench

The controls that make the numbers trustworthy

Both benches below are regions of the same accepted Builder capture shown at the top of this page. Use Full frame on either one to see where the region sits in the window.

The CuePatch right-hand inspector showing a surface colour palette with a hex readout, and a screen name panel with weight, size and opacity controls.

A Surface colour and screen labels

Interface detail from the accepted view. Surfaces are colour-coded and named on the canvas, with label weight, size and opacity under your control — so a printed map stays readable in a dim shop.
The CuePatch screen configuration panel: a screen named US Wall using ROE Visual Carbon CB5 tiles, a note that half tiles are available horizontally and vertically, an optimal viewing range of 11.5 to 34.6 metres, and a grid size of 16 by 6 tiles resolving to 1664 by 1248 pixels.

B Tile type drives the arithmetic

Interface detail from the accepted view. Choosing the tile fixes the maths. A 16×6 grid of Carbon CB5 resolves to 1664×1248 px, with the optimal viewing range calculated from the same product data.

These are crops of one real capture, not separate sessions. CuePatch is in private validation, so the site publishes the single screenshot Steve selected rather than manufacturing extra states for marketing.

05

Availability

Commercial truth, stated plainly

Private Validation — Beta Interest

CuePatch is not on public sale.

The application is in private validation with working professionals. There is no public download, no self-service activation, and no published price. Tier structures that previously appeared on this page are retired and are not CueForge's commercial position.

The intended shape is one complete professional edition licensed to one active computer, with a humane self-service transfer when a machine dies. Exact price and terms remain an open commercial decision and will not be quoted until they are settled.

Contact Us
Platform
Desktop application for macOS and Windows.
Data boundary
Projects are local files with autosave and recovery. No cloud account is required to build a map.
Interchange
PNG / JPG / WebP, OBJ, disguise CSV and 3D positions, grandMA3 XML, MVR, slice and pack reports.
Release state
Private validation. Distribution, activation and support terms are not published.