TakeboundOpen local workspace

Circle the take, and the file name is already written.

This browser workspace is for people who run voice-over recording sessions. Log every take against its script cue, circle the one you want, and the delivery filename is already written. Pickups, local WAV and AIFF checks and the handoff record stay on your device. The panel below is the session desk at the size you actually work at.

Recording elsewhereORCHARD / S01 / C017SCRIPT REV 2
Then the orchard lights came on, one row at a time.

Direction Calm, unhurried, land on the last four words.

  • 1
  • 2
  • 3
  • 4
  • 5
  • Take 3 circled
Delivers asorchard_s01_c017_t03.wav
Station 01, the session desk. The circled take is the one the project points at, and the file name is rendered from the naming profile rather than typed.
Open the workspace

Scripts, takes and file names stay in this browser. There is no account, no upload and no microphone request.

The links a folder of files cannot hold

A folder shows take numbers. It does not show which script revision was read, which take was chosen, why a cue came back, or which of two cues will overwrite the other on the way out.

01 Intake

Map the cues

Preview strict UTF-8 CSV, TSV or pasted lines, then commit the accepted rows in one go.

02 Session

Log the takes

Number attempts while your recording software runs, and every take keeps the exact script revision it was read against.

03 Pickups

Keep the reason

A pickup round freezes why the cue came back, which take came before it, and what finally answered it.

04 Delivery

Match the folder

Compare expected names against local WAV and AIFF headers, then freeze what the browser actually observed.

What it refuses to do

The bundled evaluation is fiction, and it is completeOrchard Signal holds 100 original cues, 236 take records, three sessions, two pickup rounds, one prior delivery freeze and four planted problems. It represents no real person, client, production, quotation or recording.

Worked example

The shortest honest answer to what this is: a local ledger that keeps a script cue, the take that was read against it, the file that take will be delivered as, and the reason anything was redone, all in one record that survives a browser reload and travels as a file you own. It sits between your script spreadsheet and your recording software, and it does not try to become either.

The bundled Orchard Signal evaluation shows why that matters. It holds 100 original cues, 236 take records, three night-survey sessions, two pickup rounds and one prior delivery freeze. Since that freeze four things have gone wrong on purpose. Cue C017 was amended to a second revision, so its selected take now reads superseded script text. Cue C042 sits in issued pickup round P02 with no response take linked. Cue C055 is required, has takes, and has no current selection. The selected take for C090 renders an expected filename of CON.wav, a reserved device name on Windows, while cue codes C-071 and C_071 collapse onto one filename token once case and separators are normalized. A folder listing shows none of that. Working the stations in order shows all of it.

Method

The workspace is nine stations in a fixed order: session, cues, intake, takes, filenames, pickups, preflight, delivery, projects. Each station writes one kind of record and refuses to write the others, so a filename decision cannot quietly become a take decision and a pickup round cannot quietly rewrite the session it came from. Every take carries the exact cue revision that was read, which is the single link that makes a stale selection detectable later.

Projects live in IndexedDB in the current browser profile, with a session-only fallback when that storage will not open. Nothing you load or type is uploaded, and the pages carry a content policy that blocks every outbound connection except the billing hosts the Premium page names. Portability comes from versioned JSON checkpoints you download yourself; a restore is transactional and refuses a file whose schema or digest does not check out.

What this does not do

Do this in the app

Fifteen minutes with the bundled evaluation is a faster answer than any feature list.

  1. Open the workspace and load the Orchard Signal evaluation at station 01 Session.
  2. Read station 05 Filenames and station 07 Preflight first; that is where the four planted problems surface.
  3. Download a checkpoint from station 09 Projects to prove the project moves between browsers.

Open the local workspace at station 01 Session

Related reading