Reconcile script cues and WAV filenames
Turn a delivery folder into an explicit missing, unexpected, duplicate, and metadata-difference review.
Start from selected takes
Each required cue needs one current take and one expected filename. A take tied to an older script revision is blocked before the folder comparison begins.
Choose local candidates
Select WAV or AIFF files from the intended folder. The browser reads a bounded header slice and retains metadata only when you choose to store the scan result.
Interpret findings correctly
An exact filename match says only that names align. Header fields may be incomplete or false, and no sample content is decoded. Listen and verify in qualified audio tools.
Worked example
Run the sample preflight and the findings are not a clean sheet. One observation shows a file whose container is AIFF while the expected name ends in wav, which is a real difference and not a naming typo. One file called room-tone.wav is present in the folder and matches no cue at all. Cue C055 is required and has no current selection, so no filename is even expected for it. Cue C042 is waiting on an unresolved pickup. Cue C017 has a selection that references a superseded script revision.
Five separate problems, four different categories, one folder. The value of the station is that it names each one instead of reporting a count of files.
Method
Reconciliation starts from selected takes, not from the folder. Each required cue must have one current take and one expected filename, and a take tied to an older cue revision is flagged before the comparison begins. You then choose local WAV or AIFF candidates, the browser reads a bounded header slice from each, and the station reports missing, unexpected, duplicate and metadata-difference findings.
Header observations are retained only if you choose to store the scan result. Audio bytes and file paths are never stored.
What this does not do
- An exact filename match says the names align and nothing more.
- No audio samples are decoded, so silence, clipping, noise, loudness, sync and content identity are all invisible.
- Header fields are declarations by whatever wrote the file and can be incomplete or wrong.
Do this in the app
Compare the folder you are actually about to send, not a copy of it.
- Open station 07 Preflight and select the intended WAV or AIFF files.
- Read every missing, unexpected, duplicate and difference finding in turn.
- Fix the cause in the session or the folder, then rescan rather than dismissing the finding.
Open the local workspace at station 07 Preflight