Loading...
Loading...
The Notes List
Drive one production of The Notes List from your Companion surface.
https://thenoteslist.com unless you are on beta/alpha.$(<connection label>:pairing_code) (drop it on a button to read it off the deck).A station belongs to one production. To move to another show, revoke it in Settings and pair again.
Enter the desk's IP in Eos desk IP (ticking Use TCP SLIP is the safe choice on Eos 3.1+: it uses port 3037, which is SLIP whatever the desk's OSC TCP format is set to; unticked, it uses port 3032, which only works with that format set to OSC 1.0. If the two disagree, the log says "is the desk expecting SLIP?"). Enable OSC RX/TX on the desk under Setup → System → Show Control → OSC. This module then follows the live cue of cue list 1 (change Cue list if needed), fetches the cues around it first, and walks the whole list in the background, gently, one request every 150 ms (a 500-cue show takes about 80 s, a 1700-cue show about 4 minutes; the desk never sees a burst). It subscribes as soon as it connects, so cue edits on the desk (record, insert, delete, relabel, add a part) update the cache by themselves: each edit re-reads only the cues it names, a few requests, never the whole list again. On connect it sets an OSC output filter (Eos 2.6.1+) so the desk sends only cue messages, not the wheel and channel traffic that comes with a subscription; the log says when the desk accepts it; if the desk does not answer through the filter within 5 s, the module clears it and says so in the log. It pings the desk every 5 s and reconnects when the desk stops answering for 12 s (pulled cable, desk reboot); while the desk is gone the cue variables are blank, so a note never lands on a frozen cue. It never sends a command to the desk. Eos: reload the cue list is there if you ever want to force a fresh read.
Selected cue. Notes land on the selected cue, which normally follows the live cue. If a press comes late, Selected cue ◀ / ▶ move the selection back or forward through the cached list without touching the console; Selected cue = live follows the running cue again. When the desk fires the next cue the selection returns to live (tick Keep cursor offset to hold the offset instead). The selection is held as a cue number, so an insert or delete on the desk never moves it to a different cue; steps and the offset count base cues only (parts are skipped). Key faces: $(<connection label>:selected_cue) (with selected_cue_label, or selected_cue_label_short for the first 7 characters), $(<connection label>:cue_live); the Selected cue is not the live cue feedback turns a key amber while stepped, and Selected cue is the live cue turns the = live key green. With no desk connected the = live preset reads NO DESK. Presets under "Selected cue" include a display-only key showing the selected cue and the start of its label.
With Send cue labels to The Notes List ticked (the default), the labels of the cue list this module reads (the Cue list setting) go to the show this station is paired to, where they fill the Cue Label column. A cue with no label of its own but a labelled part (a label typed on Part 1, for example) sends the label of its lowest-numbered labelled part. Where a cue also has a label from The Cuelist, the desk's label wins. Nothing extra is asked of the desk: the labels come from the list the module already reads. Once the whole list has been read, every label is sent in one go; after that only changes are sent (a relabel, a new cue, a cleared label), about 2 s after the last edit. The log shows "Cue labels: sent N" for the full send and "Cue labels: updated …" naming the cues for each change, or "Cue labels: removed …" ending "(label cleared)" or "(cue deleted)". Untick it to stop sending.
$(<connection label>:cue_labels_status) says how it is going:
waiting for walk — the cue list is still being read from the desk (or the desk is not connected).sending — a send is in progress, or being retried after a network or server error.ok <n> — The Notes List holds the labels of n cues.paused (server off) — The Notes List has cue labels switched off for now; the module tries again later by itself. (paused (too soon) is the same after sending too often.)stopped: <code> — The Notes List refused them (for example 401: the station is no longer paired; 404: the server does not know about cue labels yet). Nothing more is sent until you save the settings, the desk reconnects, or you press Resend cue labels.off — the box is unticked.The Resend cue labels action clears a stopped or paused state and sends every label again once the list is fully read.
The Cue number box on a New note key is variable-aware, so with another console's Companion module you can type its variable there (for example a QLab or grandMA3 cue variable) instead of the Eos cursor.
Everything acts on your own open browser tab of The Notes List, on the page for the chosen module. Other members' tabs never react. With several tabs open on that page, only the one you last clicked into acts; if a key seems to do nothing, click into the tab you want.
Under Presets, in the order you reach for them in tech:
Every key keeps its text on the bottom edge, clear of the N, so a row of keys lines up. Drag them onto the deck. Keys dragged from an earlier version keep their old look: drag them again to pick up a new one.
Colour key by note type / by priority — background matches the chip colour in the app (renamed or recoloured types follow within a minute).
Outstanding count above threshold — colour a button when a module has more than N open notes.
Connected — station is paired and the production accepts it.
$(<connection label>:cue_outstanding), work_outstanding, production_outstanding, electrician_outstanding, station_name, production_name, pairing_code, connected.
Eos: cue_live, cue_live_label, selected_cue, selected_cue_label, selected_cue_label_short (7 characters, for a key face), selected_cue_offset (base cues from live, parts not counted; 0 = live, ? while loading), eos_connected, cue_labels_status.