End to end worked example
One project, nine stations, four deliberate problems, and the exact cue file to start from.
This page runs the whole product once on a project that is deliberately not tidy. Orchard Signal holds 100 cues, 236 take records across three night-survey sessions, one naming profile, two pickup rounds and one delivery freeze. Since that freeze, four things have gone wrong on purpose, and finding all four is the exercise.
Start with the cue file
The file below is written by the same CSV writer the application uses for its own exports, from the same sample script, and this site does not build unless the file parses back through the application's own cue importer with every row accepted and nothing rejected. It is plain UTF-8 comma-separated text with the headers code, speaker, line, direction, locale.
Download orchard-signal-cues.csv
Step 1: session and authorization
At station 01 Session, confirm that you are authorized to handle the script and the recordings, then create the project and give it a stable code. The sample uses ORCHARD. Download a checkpoint before you do anything else, because browser storage is a working copy and not an archive.
Step 2: intake the cues
At station 03 Intake, load the downloaded file. The station suggests a column mapping from the header names, previews every row, and commits the accepted set atomically. One hundred cues accepted, none rejected. The import itself is recorded, with its source label, delimiter, headers and counts, so the origin of the cue list survives in the project.
Step 3: log the takes
At station 04 Takes, log attempts after your recording software stops. The sample has three takes for the first thirty-six cues and two for the rest. Take 2 is the selected read almost everywhere, take 1 is noted as a first pass and take 3 as an alternate ending. Every take carries the exact cue revision that was read, which is the detail that makes the next steps possible.
Step 4: derive the filenames
The naming profile is called Orchard cue slate. Its pattern is project, session, cue and take joined by underscores, lower-cased, cue padded to three digits and take to two, with a wav extension, so take 2 of C017 in session S01 renders as orchard_s01_c017_t02.wav. Station 05 Filenames shows the rendered name for every selected take together with each normalization applied on the way.
The four deliberate problems
- C017 reads superseded text. After the baseline freeze the cue was amended to a second revision, changing row six to row seven. The selected take still references revision 1, because that is what the performer actually read. The tool marks the selection stale rather than quietly repointing it.
- C042 is waiting on a pickup. Round P02, Path direction, was issued asking for a calmer read, and no response take is linked yet. The round stays visibly unresolved instead of being closed to tidy the view.
- C055 has no current selection. Its selection was cleared. The cue is required, it has takes, and nobody has chosen between them. A folder listing would show plausible files and give no hint that the decision is missing.
- C090 and the C-071 pair break the filenames. The selected take for C090 carries an expected filename of CON.wav, a reserved device name on Windows. Separately, cue codes C-071 and C_071 collapse onto the same filename token once case and separators are normalized, so two different cues would deliver as one file.
Step 5: pickups
At station 06 Pickups, round P01 shows what a resolved round preserves: the reason, the direction, the previously selected take, the response take that answered it, and the times it was created, issued, returned and resolved. Round P02 shows what an open one looks like. Neither round rewrote the session it came from.
Step 6: preflight the folder
At station 07 Preflight, choose the local audio files you actually intend to send. The browser reads a bounded header slice from each and reports differences by category. The sample surfaces two more findings here: one observation declares an AIFF container while its expected filename ends in wav, and a file named room-tone.wav is present in the folder and matches no cue at all. Neither is guessed at; both are named.
Step 7: freeze the delivery
Only once every finding has a decision does station 08 Delivery earn a freeze. The sample's existing freeze D001 is a clean baseline taken before the four problems appeared, carrying one hundred selections and a digest over them. A second freeze taken now would record a different, honest state.
What the freeze is and is not
The digest proves those bytes have not changed since the freeze. It does not prove a single file was sent, received, opened, approved or accepted, and it says nothing about how any take sounds. Verify the audio in your own tools, and confirm transfer and acceptance with the person receiving it.