Brainsalt Knowledge Base
Documentation for running a Brainsalt media server installation: Brainsalt Hub for the server itself, Backstage for the show that runs on it — plus recordings of most of it.
Where to start
The two products are used in order. Set the server up first, then build the show.
|
Section |
Use it for |
|---|---|
|
New to Brainsalt — which product does what, and the order to work through them |
|
|
First. Discover the server, set its address, sign in, create users, configure displays and GPU outputs, watch hardware health, control power, reach it remotely |
|
|
Second. Everything about the application: building a show, running it, and driving it from outside |
|
|
The same material recorded on a real server, filed the same way as these pages |
Not sure which half your problem belongs to? Missing outputs, a display behaving oddly, network or user trouble are server questions — Brainsalt Hub. Anything about what appears on screen is Backstage.
Backstage in five pages
If the server is already running and you just need the application:
-
What is Backstage? — what the product is and what it is for
-
How Backstage Thinks — the mental model: how scenes, content and outputs relate
-
User Interface — how the interface works, and why no screenshot shows where anything is
-
Your First Project — one guided path from an empty project to media on a physical output
-
Workflow — the same journey with every choice spelled out
The build, stage by stage
Each stage produces something the next one needs, and each says what "done" looks like.
|
Stage |
Covers |
|---|---|
|
Displays, projection surfaces, projectors and mappings — the model of the room |
|
|
Video routing, audio devices and mixers, Art-Net pixel output |
|
|
Mesh warping, camera calibration, blending, black level — for projection |
|
|
Importing media, conversion, and live sources — NDI, capture cards, Unity |
|
|
Sequences, steppers, the Broadcast Scheduler, transitions and timecode |
Then, as the job needs them
|
Section |
Reach for it when |
|---|---|
|
A control system, browser, stream-deck surface or script has to drive the show |
|
|
The show needs logic the built-in windows do not cover |
|
|
Checking it runs cleanly before an audience arrives, or finding out why it does not |
|
|
Lighting, motors or effects are programmed in Conductor |
|
|
Complete builds — an LED facade, a dome, an L-shaped wall, a stereoscopic rig |
Looking for something specific?
|
Section |
What you will find |
|---|---|
|
Every window and panel explained |
|
|
Every Node Editor node, with its pins documented |
|
|
A symptom — black output, assets not loading, connections not firing, servers out of sync |
|
|
Short answers to the questions that come up most |