Export Settings

What this is about

Most delivery failures happen in this dialogue rather than in the edit. A frame rate silently converted, audio exported at the wrong sample rate, a resolution scaled from the sequence instead of matching it, a colour tag left off — each of these produces a file that plays but is wrong. Saving presets per client and per platform turns the whole thing into a decision made once, and a short checklist on the first and last thirty seconds of the file catches most of the rest before anyone else sees it.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

Where this differs from the general case:

• Save a preset per client and platform; repeating the same dialogue by hand invites mistakes
• Frame rate must match the sequence — silent conversion produces stutter nobody spots in preview
• Check the first and last thirty seconds of every export before it leaves the building

With TillyGen

With the required deliverables listed in TillyGen, the export is set up against an agreed specification instead of against last month's habit.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.