Broadcast WAV lands in the wrong place? Check the timestamp and the import

A field recording opens in your editor, but it appears at the playhead instead of where you expected it on the timeline. Before moving the only copy or rewriting its metadata, separate three questions: what start-position information the file contains, how the editor interprets it and whether the recordings actually align.

A timestamp can help place an audio file. It is not a listening check, a complete record of the recording setup or proof that two devices kept time together throughout a take.

Keep the original and write down the expectation

Work with a copy. Record the original filename, the intended scene or take, and the position you expected. Include the editor and project revision so that “wrong place” has a specific reference.

Use the blank BWF placement ledger to keep metadata observations beside timeline and listening observations. It does not read a file or repair timestamps. Leave unknown values blank and decisions marked NOT CHECKED until you inspect them.

A useful first question for the sender is: “Should this file start at a particular project position, or should I align it to another recording?” Those are different handoff instructions. A filename such as take-final.wav does not answer either one.

Read the sample rate with the time reference

EBU Tech 3285 version 2, published in May 2011, defines the Broadcast Wave Format. Its TimeReference is a 64-bit count for the first sample since midnight. Interpretation depends on the sample frequency stored in the format chunk. The document also defines separate origination date and time fields.

For this narrow calculation:

seconds since midnight = TimeReference / sample rate

Here is invented arithmetic, not metadata extracted from recordings:

Different raw counts can therefore describe the same time when the sample rates differ. Do not copy a count from one file into another to make their displayed numbers match. If a value is missing or you do not know the file's rate, leave the interpretation unresolved rather than substituting your project rate.

FADGI's BEXT metadata guidance, last updated in 2016, discusses TimeReference for complex recordings. It also points out that the BEXT origination date/time structure does not provide an unambiguous UTC datetime. Do not infer a timezone from a displayed clock value alone.

Inspect the editor's import choice

Open a working copy in the intended project. Record the project time display, expected location and actual location after import. Consult that editor's current documentation for its original-position or timestamp import behavior. This guide does not give a universal menu path.

If the clip appears at the playhead, that observation alone does not establish that the file lacks a timestamp. Equally, an inspector showing a time value does not establish that the editor used it. Record both observations before changing anything.

Try a controlled import into a disposable project or a saved project copy. Preserve the initial result, change one relevant import choice, then compare. Avoid overwriting source metadata while you are still determining whether the problem belongs to the file or the import procedure.

Check alignment beyond the starting point

Compare an identifiable event near the beginning and another later in the take using the reference material supplied by the sender. Describe what you observe rather than labelling every mismatch “drift”. Confirm that the files represent the same take and revision before diagnosing timing behavior.

For a concrete manufacturer example, Sound Devices' 702T/744T digital-input and time-code note, updated in July 2020, explains a configuration where sampling and time-code clocks use different time bases. It is a model-specific example of why the recording setup matters, not setup instructions for every recorder.

If the beginning aligns but a later event does not, retain that evidence and ask about the recording and export history. Do not rewrite a start timestamp and call the whole take synchronized. Any corrective processing needs its own agreement and a separately named result.

Send the placement evidence with the file

A useful handoff includes the untouched original, the intended timeline position, the metadata observations and the passages used to check alignment. If you also need to confirm that the received bytes match, use the checksum and listening guide. File identity and correct placement answer different questions.

Sources reviewed on 3 November 2026. Only the two arithmetic examples were calculated for this guide. No BWF file, recorder, editor import or synchronization result was tested.