How much can a
video scaler do?

The states below distinguish the current internal implementation from work in progress and future directions. Internal implementation does not mean public availability.

Exact content geometry

In the internal build

Set content width, height and X/Y independently of the output raster, with black outside the content. External processor behaviour still requires checking.

Cadence matching

Planned direction

Prefer a matching nominal input/output frame rate and identify conversion. Matching is not genlock.

Output raster suggestions

Planned direction

Suggest a compatible raster that contains the requested content, considering cadence, colour and stability. Preserve manual selection and protected timing changes.

Window and display inputs

Planned direction

Use a window or display on the same PC as a source for the scaler, with handling for resizing, permissions and unavailable content.

Colour pipeline control

Planned direction

Expose known colour format, chroma, range and bit depth. Advanced colour and HDR support will develop progressively; unknown physical-chain properties remain identified.

The states below distinguish the current internal implementation from work in progress and future directions. Internal implementation does not mean public availability.

Output on input failure

Current foundation + planned extension

Manual Freeze and Black are implemented.

Develop input-failure policies for holding the last frame, black or a configured slate. No continuity guarantee during a reboot, runtime crash or GPU reset.

Backup input and failover

Planned direction

Develop controlled switching between a primary and backup source, with defined validity and return conditions. This does not imply audio mixing.

Show profiles

Current foundation + planned extension

Configuration persistence is implemented.

Develop reusable profiles for input, transformation, output and protection policies, with import/export and explicit handling of missing devices.

Separate controls and runtime

Current foundation + planned extension

The UI is separate from the runtime; closing it does not itself stop output. Configuration is persisted.

Develop recovery around the applied state and valid settings. Recovering settings does not keep video running through a reboot.

Reconnect capture and output

Planned direction

Restore the same source or destination when it returns, with validated settings. Ambiguous identity must not silently choose another device.

Safe start and arming

Current foundation + planned extension

Capture requires explicit Start in the current candidate.

Develop documented preparation and optional resume policies based on valid devices, formats and operator intent.

Runtime health monitoring

Planned direction

Observe frame delivery, GPU/output progress and process health, with bounded recovery attempts and operator-visible outcomes.

Live format protection

Planned direction

Protect the applied format, route and geometry during live operation rather than silently following a source-format change.

Bounded frame queues

Planned direction

Prefer the newest complete viable frame and discard obsolete frames when necessary. Queue limits are not a claim of zero latency.

The states below distinguish the current internal implementation from work in progress and future directions. Internal implementation does not mean public availability.

LED wall model

In the internal build

Define cabinet rows, columns, module pixels and descriptive pitch; derive resolution and coordinates. Saving the model does not change output geometry.

Locate a cabinet

Being implemented

Highlight a selected cabinet using the configured pixel map. The map is supplied by the operator, not discovered from the physical panels.

Locate a module

Planned direction

Highlight a module inside a cabinet and show its local and wall coordinates, based on the configured layout.

Find a junction

Planned direction

Highlight the selected boundary between cabinets or modules to inspect alignment and uniformity.

Walk the wall

Planned direction

Step through cabinets manually or automatically to check the configured map against the wall.

Test a selected area

Planned direction

Apply a test within a chosen rectangle while preserving the content outside that area.

Calibration assistance

Planned direction

Show patterns in a selected area to assist the technician. Processor calibration coefficients remain under the technician's control.

Port and group overlays

Planned direction

Associate cabinets with operator-declared ports or groups and highlight them. This does not discover or verify physical wiring.

The states below distinguish the current internal implementation from work in progress and future directions. Internal implementation does not mean public availability.

Single-pixel patterns

Planned direction

Reveal unwanted scaling or interpolation using patterns at a stated point before or after the scaler. This is visual diagnosis, not automatic physical detection.

Chroma patterns

Planned direction

Use colour and text patterns to inspect chroma detail. Testing the upstream capture path requires an appropriate pattern from the external source.

Black and white levels

Planned direction

Show near-black and near-white levels in a stated range to help inspect clipping and conversion.

Gradients and bit depth

Planned direction

Inspect banding, quantisation and conversion using patterns with known formats. Appearance alone does not establish the physical bit depth.

Motion and frame patterns

Planned direction

Generate controlled movement and frame counts to inspect the downstream path. A local pattern cannot establish upstream capture losses.

The states below distinguish the current internal implementation from work in progress and future directions. Internal implementation does not mean public availability.

Signal-path status

Planned direction

Explain the known state of input, capture, GPU, scale and output, distinguishing reported, observed and unknown information.

Configuration self-test

Planned direction

Assess a specific setup with its tested scope and limits. A self-test is not universal hardware certification.

Technical event history

Planned direction

Keep a bounded history of operator actions, failures, configuration changes and recovery without recording client video by default.

Performance diagnostics

Planned direction

Expose controlled measurements with their method, scope and duration. Engine timings must not be presented as end-to-end display latency.

Memory-path visibility

Planned direction

Explain known RAM/GPU transfers, uploads and conversions. Observing part of the path does not establish end-to-end zero-copy.

GPU and output topology

Planned direction

Identify the rendering GPU, destination adapter and known transfers to help select a suitable route, with explicit handling of ambiguity.

Output modes and EDID

Planned direction

Inspect advertised modes and known colour capabilities, distinguishing advertised, applied and tested states. EDID does not qualify the whole signal chain.