Display and GPU Configuration

Last updated 31 July 2026

Display and GPU Configuration

Everything that decides which physical outputs a Brainsalt server drives, what signal each one sends, and how that survives a reboot. These settings live in the System Management web interface of the server itself, under Configure > GPU.

Display configuration requires the Administrator role. The whole GPU group is hidden from User and Operator accounts. Read-only signal monitoring is available to every role on the separate GPU Status page under Maintain.

[USER-ACTION-REQUIRED: Attach a screenshot of the System Management sidebar with the GPU group expanded here]

The GPU tabs

Tab

What you do there

Typical reason

EDID

Force a saved EDID onto an output, or build one from a live display, a .bin file, or from scratch.

A projector reports a mode you do not want, or the server must hold a resolution with nothing plugged in.

Outputs

Set signal format, output bit depth, dynamic range, and desktop color depth per output or per Mosaic grid.

Match the projector's expected input, or trade chroma for bandwidth headroom.

Genlock

Synchronize the refresh timing of multiple GPU outputs using an internal VSync or an external house sync reference.

Eliminate visible tearing at the seams of an edge-blended projection or a multi-display video wall.

Mosaic

Combine several physical outputs into one large logical display.

Drive an LED wall or a projector array as a single canvas.

Virtual Monitors

Create headless virtual displays whose GPU-accelerated desktops Backstage can capture as live assets.

Integrate a third-party rendering application into a Backstage-driven installation without physical screens.

Desktop

Remove outputs from the Windows desktop so Backstage uses them exclusively, or return them to Windows control.

Recommended for all Backstage rendering outputs — improves performance and eliminates OS interference.

Options

Decide what is restored at startup and after a display change, and reach the display recovery actions.

Make a configuration survive reboots, or reset a display setup that has become stuck.

Signal health for these same outputs is reported separately, read-only, on Maintain > GPU Status.

Recommended order

When commissioning a server, work through the tabs in this order. Each step changes what the next one sees.

  1. EDID — fix the mode each output reports first. An output that is part of a Mosaic grid or removed from the desktop cannot have its EDID changed.

  2. Mosaic — build the grids, now that every member reports the intended mode.

  3. Outputs — set format, bit depth, and range on the resulting outputs and grids.

  4. Genlock — if the server has synchronization hardware, enable frame-lock on the outputs that must refresh together.

  5. Virtual Monitors — add any virtual monitors needed for third-party application capture.

  6. Desktop — remove the outputs Backstage renders to from the Windows desktop. This hands them to Backstage exclusively and improves performance.

  7. Options — turn on the restore settings so the result comes back after a reboot, then reboot once to prove it.

While the server is applying a display change, other GPU pages show Monitor configuration in progress - retrying... and refresh themselves once it finishes. This is normal. Do not reload the browser or send a second change while it is showing.

Articles in this section

How to Check GPU Output Signal Status — read-only signal and bandwidth health per output, available to every role.

Server Configuration — the rest of the server configuration section: users, roles, and configuration backup.

How to Recover an Output When a Monitor Is Unplugged or Moved (Ghost Outputs) — what to do in Backstage when a monitor is unplugged or moved and an output goes missing.