Timeline Builder
Use Timeline Builder when you need to rebuild a multicam timeline from production audio and prepare an FCPXML handoff.
Choose either the synced WAV or chased-timecode AAF workflow. Both need a Timeline XML for the video or multicam timeline, a Stereo mix WAV, an output folder and a writable filename. The synced WAV workflow also needs a Synced audio folder. The AAF workflow reads audio from the AAF’s embedded or referenced media; choose an External AAF media folder only when external links cannot be resolved.
- On Inputs, choose the audio source workflow and add the Timeline XML.
- For synced WAVs, add the Synced audio folder. For AAF, add the AAF file and, if required, the External AAF media folder.
- Add the Stereo mix WAV, set the video frame rate and choose the output folder and filename.
- For AAF exports with different in points, optionally choose Automatic audio match under AAF alignment.
- Choose Scan and continue. Review the alignment summary when available, then review the analysed events and timecode choices in Mapping.
- Continue to Validate and resolve warnings about missing media, frame rate, timecode or mappings.
- Choose Build timeline, then review the exported FCPXML and build report in Report.
A clean build depends on readable LTC, the correct frame rate, consistent source media and complete mapping. Always review the start time, clip order, gaps, overlaps, grouped WAVs and flagged files before delivery.
Optional AAF audio alignment
AAF alignment is included in v0.3 (build 5). Automatic audio matching is off by default. Current alignment uses the WAV’s BWF start timestamp when available; otherwise it places the first AAF region at the start of the WAV.
Use Automatic audio match when the AAF and Stereo mix WAV are exports of the same edit but may have different in points. The AAF audio may be camera scratch microphones while the WAV is the engineer’s final mix: the recordings need enough shared speech, music or other changing sounds to match.
- In Inputs, choose Automatic audio match from AAF alignment.
- Choose Scan and continue. Matching runs locally during this scan, using the AAF audio’s source ranges.
- Review the offset and confidence summary before proceeding with the camera mapping and build.
The app compares several independent sections and applies one fixed offset only when at least three unambiguous sections agree. Different microphone levels and tone can still match, but heavy noise, echo, added music or replaced dialogue can make matching unreliable. Source files are never changed and audio is never uploaded.
Read the alignment result
The result appears as soon as audio matching finishes during Scan and continue, before camera analysis completes. The summary stays visible beneath the step tabs through Inputs, Mapping, Validate and Report. It also appears in validation and the build report notes. You do not need to build a timeline to see it.
A negative offset means the first AAF region begins before the WAV. For example, −1.354 s means it starts 1.354 seconds before the WAV’s first sample. A positive offset means it begins later in the WAV. Preview and export use the same offset; regions before the WAV start are omitted and crossing audio and picture source ranges advance together.
Confidence comes from independent sections agreeing on one offset. The audio similarity percentage is a comparison score, not a probability that the alignment is correct. Automatic matching uses a 20 ms analysis grid; check sync in the receiving application before delivery.
Set or adjust a manual offset
Choose Manual offset under AAF alignment and enter Offset (seconds), using a decimal point. Positive values place the first AAF region later in the WAV; negative values place it before the WAV. After a successful automatic match, Use this offset manually copies the result so you can adjust it.
Choose Scan and continue again after changing the alignment mode, offset or inputs. The existing result is cleared so the mapping and export cannot reuse an outdated alignment.
If no reliable offset is found
An uncertain match keeps Current alignment and adds a warning for review. Check that the AAF media is accessible and that both exports contain the same edit with enough shared audio. Silence, repeated passages and too little overlapping material may not establish a unique offset.
If sections suggest different offsets, check for different edits or clock drift. Automatic alignment finds one fixed offset; it does not stretch audio or repair edits. Use a verified Manual offset or export matching versions of the edit before continuing.
The matcher checks sections of 4–12 seconds and needs at least three independent matches. It reads audio at 8–192 kHz in files up to eight hours long.