Render

What this is about

Until it is rendered, a timeline is only a set of instructions: use this clip from here to there, put this effect on top, change this colour. Playback previews approximate the result, but the file that leaves the building is calculated frame by frame. Render times scale with resolution, effect count and codec, which makes them a scheduling factor rather than a technicality — an overnight render that fails at ninety per cent costs a full day. Test exports of short sections catch that class of problem while there is still time.

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:

• Treat render time as a scheduled item, especially for long-form or effect-heavy projects
• Export a short test section first; a failed overnight render costs a full working day
• Check the finished file end to end — a render can complete and still contain dropped frames

With TillyGen

Render and export windows entered as steps in TillyGen's plan keep the last day before delivery from being the first attempt at a full-length file.

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.