Live dashboard

The live dashboard is where the show is run: the timer, the current run, the runners, the scene on screen, the feeds, audio and OBS. Every overlay follows what you do here at once. Open it from the marathon dashboard; it takes the whole screen.

Operators and above get the full dashboard. Hosts, runners, commentators and moderators get a smaller one, see Crew roles.

Arranging the dashboard

Panels are modules shown as tiles on a six-column grid, in tabs. The default is made for a 1080p screen, so each tab fits without scrolling: the timer and the scenes sit in a fixed area at the top, on every tab, and below them are four tabs: Run (run, runners, up next, schedule), Production (previews, feeds, audio), Extras (countdown, ticker, music, OBS) and Donations (donation queue and total). Every tile collapses with the arrow in its header.

Press Edit to build your own screens:

• Tabs. Use + for a new tab, then rename, move or delete the open one with the buttons beside it. Any tab can go, the first three included, but the last one stays. Deleting a tab only takes its modules off the screen; add them back from Modules.
• Modules. The Modules menu adds a module to the open tab, or removes it. A module lives on one tab at a time, so adding one from another tab moves it.
• Position and size. Drag a tile by its grip to move it and drag the corner to resize it. A tile is at most 6 columns wide, and the grid packs tiles upward so there are no holes. A tile's height follows its content (auto height) until you drag the corner up or down; the height button in the tile's bar switches between auto height and a fixed one (a fixed tile scrolls inside: only its body, the header stays put). Drop a tile on another tab to send it there, or use the arrow menu. From the keyboard, focus the grip and use the arrow keys to move, Shift and the arrows to resize.
• Fixed area. While editing, a dashed area above the tabs holds modules that stay on screen whichever tab is open (the timer, say). Add modules to it from the second group of the Modules menu, or drop a tile on it. It lays out like a tab, and is hidden when empty.
• The reset button brings back the default screens.

On a narrow window the grid becomes a single column, and only the tab and module controls apply. The arrangement is yours and stays in your browser, so each operator can set it up their way.

Drafts. Forms such as the run or the runners hold what you type until you press Apply, so another operator's change doesn't erase your typing. Timer, scene and countdown buttons apply at once. The avatars in the header are the other operators on the dashboard right now.

Timer

Start, pause, resume and reset (reset asks first). In a race each runner has a Finish button, with undo, and the timer stops when the last one finishes.

Click the clock to type a new time, or fix one runner's finish time. The tile shows the time against the estimate. The timer runs on the server's clock, so a reload or a second operator never makes it drift.

With Runners control their own timer on, a runner linked to a slot can start, pause and finish their own run from their dashboard.

Run

Game, category, platform, estimate, host and commentators of the current run. When the run comes from the schedule, these are already filled in.

Up next

The upcoming runs. Next run makes the first one current and resets the timer, after asking if the timer is still running.

When the marathon has a schedule, Next run also fills the runners, the race mode and the commentators, and picks the scene. Schedule items here are read-only: Make this the current run jumps to any of them (to go back after a mistake, or skip ahead), and Sync rebuilds the list from the schedule if it changed during the event. Without a schedule you type the queue by hand.

A break, intermission or interview from the schedule keeps the runners, shows its title as the game and starts a countdown for its length.

Schedule

The current slot's planned start and end and how far it is over, plus the next slots. When a run overruns or ends early, fix it here and the rest of the schedule moves with it:

• ± buttons add or take minutes.
• End now sets the slot's length to the time since it started.
• Or type the length.

Slots pinned to a fixed time don't move; they warn when the slot before them now overlaps. The public schedule follows every change.

Runners

Up to four runners with name, pronouns, stream platform and channel, and the mode: solo, race or coop/teams. Adding a second runner switches solo to race. Each slot can be linked to a member's account, which gives them their runner view.

Scenes

A button per scene of the layout, for each output that follows the dashboard. Auto picks the scene from the runners and mode: normal-<ratio> for one runner, race-<n>-<ratio> for a race. A ratio switch appears when the layout has more than one.

Feeds

Where each runner's game and webcam come from. The layout's feed sources show whatever is picked here.

Each runner has a card with a summary line for the game and for the webcam: where it comes from, how it is delivered, whether it is cropped, and its play, pause and restart buttons. Click a line, or Edit, to open the editor on the whole screen: the Game and Webcam tabs each have the large preview with the crop frame on the left, and the source, delivery and crop options on the right. With several runners, pick the runner at the top. Changes follow the card's Apply bar (or Studio's staging), and the editor has the same buttons.

For vdo.ninja, Generate an ID and Copy the send link, then send the link to the runner; they open it and share their screen or camera.

Delivery picks how a stream reaches the overlay: the platform's player, a plain video, or an OBS media source. The default suits each kind; RTMP and SRT always go through OBS, since browsers can't play them. Speedthon never relays the video itself: the overlay reads it straight from the platform.

Preview and crop is in the editor. Drag the frame to move the visible area, drag its handles to resize it, or type how much to cut from each edge. The crop applies to the overlay and to OBS.

Feeds with a player have play, pause and restart buttons, for a stream that froze or fell behind.

Studio mode

The Studio button in the header works like OBS's Studio Mode. The Previews panel then shows a Preview (green) above the Program (red), which is what the audience sees. Pick a scene in Scenes and adjust the feeds (source, crop, linked OBS source), the run (game, category…) and the runners: it all shows in the Preview only. When it looks right, press Transition (or T) to put the scene and feeds on the air together. Discard drops what you prepared.

With OBS control, Studio and OBS's own Studio Mode work together. Turning Studio on or off turns OBS's Studio Mode on or off, and switching it in OBS switches Studio here. In the OBS panel a scene click then picks OBS's Preview scene. Next to Transition, one icon button per OBS transition (cut, fade, stinger…) replaces the single button: pressing one makes it OBS's current transition and runs it, which puts Speedthon's scene and feeds on the air and swaps OBS's Preview into the Program. The OBS tab of Previews shows OBS's Preview above its Program, and the list of OBS sources a feed can be linked to is read from OBS's Preview scene while Studio Mode is on.

What you prepare stays in your browser; it is not shared with other operators and is lost if you reload.

Previews

Overlay shows one output's overlay, live and scaled down. A feed linked to an OBS source shows a still of that source (taken when the source changes; the camera button in the caption takes new ones). OBS shows a still of what OBS is sending to the stream; press refresh for a new one. The OBS tab needs OBS control.

Audio

Every volume in one place: each runner's game and webcam feed, and OBS's own audio inputs. A fader applies when you let go, and follows changes made in OBS. Feeds start muted. OBS inputs show while OBS control is connected.

OBS

The connection state, start and stop of the stream and recording, OBS's scenes, and a box for any obs-websocket request with JSON parameters. See OBS.

Extras

• Countdown: presets or a typed time, for "starting soon" and breaks.
• Ticker: one message per line, shown by ticker sources.
• Music: artist and title for Now playing.
• Donations: the total shown on stream. It follows approved donations, and you can type a manual total instead. Recalculate from donations drops the manual value and sums the approved donations again.

Donation queue

New donations waiting for a moderator: approve, reject, or point the donation at an incentive. Only approved donations count toward totals and show on stream. The full list is on the donation review page, see Moderation.

Keyboard shortcuts

Shortcuts are ignored while you type or have a dialog open.

Crew roles

Crew see only their part of the dashboard, and the server enforces the same limits.

• Runner: the timer and run, read-only, and their own feeds. With runner timer control on, they start, pause and finish their own slot. They can't reset or edit times.
• Host: the run, the upcoming list (including Next run), the ticker and music.
• Commentator: the timer and run, read-only, and every runner's original feeds.
• Moderator: the donation queue, with the timer and run read-only.

Crew never see output keys, scenes or OBS controls.