Add localization tracks
Build a territory matrix in the submit flow's Localization delivery mode, then verify the per-territory evidence after the run. The example delivers one territory with a French dub and a subtitle sidecar.
This article shows the procedure. For the delivery model, the per-territory evidence pass, and the current limitations, see Localization.
Enable Localization delivery#
Start a submission and complete the Source step — see Submit a file. On the Preset step, choose the picture preset for the deliverable and enable Localization (territory delivery). The wizard switches from single-output submission to the territory matrix.
Build the territory matrix#
Add one card per market or locale. On each card, declare the dub audio and subtitle tracks that territory receives — for the example, one dub track with language French and role Dub, and one subtitle track with language French and role Full. The remaining per-track fields — conform, order, flags — are described in Localization — declare tracks.
Declare the conform that is actually true of the track. The engine measures the real speed relationship and refuses a mismatch rather than applying the declared drift.
Attachment methods#
Attach each declared track by one of three methods.
| Method | Use when |
|---|---|
| Upload | The audio or subtitle file is on the current computer. |
| Pick | The asset was uploaded previously and is listed in the Localization Assets panel at Settings → General. |
| Path | The file is already on storage the master can read. Type the path; paths are confined to the configured browse roots. |
Import a CSV manifest#
When the localization order exists as a spreadsheet, import it instead of building the matrix by hand. The matrix accepts a CSV manifest in which each row declares a territory and its tracks; the import fills the territory cards in one action.
Review the populated matrix before continuing. Every imported field remains editable, and tracks still need their assets attached by one of the methods above unless the manifest referenced readable paths.
Preview, submit and verify#
Before submission the flow states how many files the job will produce. Confirm the count matches the delivery order — one file per territory card — then submit. The picture encodes once; each territory's tracks are muxed onto it by stream copy.
After completion, the job's Localization tab shows one card per territory with the per-check evidence — track inventory, language tags, dispositions, duration and offset, and loudness where a QC profile applies. A failing check quarantines that territory only; an operator can accept a quarantined deliverable by entering a reason. See Localization — per-territory evidence.