christian/Nextcue
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: showing the next cue's name in Companion and ProdDash

Browse Source 
The cue name is now shown wherever the countdown is, and the setup lives
in Companion's and ProdDash's own settings, so record how it's done:

- Companion: a button with $(resi-studio-cues:next_cue_name) in the top
  46% (shrink to fit) over $(resi-studio-cues:next_cue_time_in_hms);
  connection settings (3000 ms poll, decoder once connected). Section 3
  pointed at the 0.1.2 package; it's 0.1.5.
- ProdDash: use Resi Cues' card (solo:resi-cues:next-cue), which is
  titled with the cue name, not ProPresenter's NextCue timer; each screen
  reloads its named layout to pick up a change.
- What's set where at North Attleboro (5 Booth 1/4; BOH TV, Studio A
  Ingest and Studio B layouts).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
christian
2026-10-07 19:26:47 -04:00
co-authored by Claude Opus 5.5
parent 0327d6a9f8
commit a0cdd1b598
1 changed files with 29 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+29 -2
View File
@@ -55,10 +55,32 @@ Run only **one copy per ProPresenter**: two copies fight over the same timer.
## 3. Optional: Companion module
In Companion: **Modules → Import module package** → `resi-studio-cues-0.1.2.tgz`, then add a
**Rey Kroona: Resi Studio Cues** connection. It provides variables such as
In Companion: **Modules → Import module package** → `resi-studio-cues-0.1.5.tgz`, then add a
**Rey Kroona: Resi Studio Cues** connection: the Resi login, **Player position poll** 3000 ms,
and (once it has connected) the **Default decoder/player**. It provides variables such as
`next_cue_name`, `next_cue_time_in_hms` and `playback_state` for buttons.
**A button with the next cue's name and its countdown:** give the button two text
elements, split by a line if you like:
| Element | Text | Position |
|---|---|---|
| Cue name | `$(resi-studio-cues:next_cue_name)` | top-aligned, height 46%, **Shrink to fit** on |
| Countdown | `$(resi-studio-cues:next_cue_time_in_hms)` | bottom-aligned, full height |
Keeping the name to the top half lets a long cue name ("Message OUT (end of prayer; MC
comes out)") shrink to fit instead of running over the countdown.
## 4. Optional: the cue name in ProdDash
ProdDash's **Resi Cues** module (in the ProdDash repo) feeds the **Timers** tile a countdown
titled with the next cue's name. Show that card, not ProPresenter's `NextCue` timer, which
only ever says "NextCue". In a single-timer Timers tile, choose **Resi › Next cue** when
adding it (stored as `solo:resi-cues:next-cue`). In an "all timers" tile it's already listed.
Each screen keeps its own copy of its layout. After a named layout changes, reload it on
each screen: **Layouts** (the grid icon, left of the gear) → the layout's name.
## Day to day
| To… | Run (on that Mac) |
@@ -115,3 +137,8 @@ package's `package.json` on every change.
**Running at North Attleboro:** the bridge, Companion and ProdDash all run on the NA Ingest
Mac, and all three use the `media@waters.church` Resi login. Keep them polling no faster than
every 3 seconds: Resi rate-limits the account when tools share it.
- ProPresenter (NA-ProP): `NextCue` timer on the stage screen's layout; stage messages off.
- Companion: page **5 Booth**, row 1, column 4 shows the next cue's name over its countdown.
- ProdDash: the NextCue tiles in the **BOH TV**, **Studio A Ingest** and **Studio B** layouts
show Resi's countdown titled with the cue's name; FOH Booth and Mobile list all timers.