Destinations

Set up the job

• Many sources, many destinations

  Add as many of each as the job needs. Every source is read once and written to every destination on the list.

• Working and backup copies

  Tag what each destination is for. The distinction carries through to the reports, so the paperwork records which role each copy played.

• Save the setup

  A job you run every day can be kept as a preset and exported, so another station can load the same offload recipe rather than rebuilding it from memory.

Checked before it starts

• Space

  Preflight compares what the job needs against what each destination actually has free, rather than discovering the shortfall at ninety percent.

• Setups that would eat themselves

  A destination sitting inside its own source is flagged before anything runs.

• Files already there

  Skip them, overwrite them, or write alongside. Duplicates are matched on relative path and size first, and shown to you before the choice is applied.

Named as it lands

• Token templates

  Build a naming scheme from the job's own metadata — sequence, project, date, camera type, camera letter, roll index — so files arrive named the way the show names them.

• Numbering you control

  Choose whether cards are ordered by name, by creation date or by start timecode, and whether the counter is scoped to the project or to the project and destination together.