Small tools for big pipelines

Most of the questions that stall a post-production day are arithmetic dressed up as a crisis. These are the ones the tools above were built for, and where to start with each.

Before the shoot: will we have enough disk, and can the edit machine cope?

Start with Storage: pick the camera codec, resolution, frame rate and the number of hours you expect to record, and it returns the terabytes you need, including a copy for backup. If the answer is uncomfortable, Can my Mac edit this? tells you whether the edit suite will cut that footage natively or whether you should plan a proxy workflow from day one — a decision that is cheap before the shoot and expensive after it.

During the edit: frame rates that don't match

Mixed 23.976, 25 and 29.97 material is where drift, pulled audio and off-by-one-frame conforms come from. Framerate & timecode converts durations and timecodes between rates, including drop-frame, and Pulldown & sync shows the speed and pitch change a conversion introduces, so you know in advance whether the sound will need to be pulled.

Handing over to VFX and grading

Consistent names save more time than any plug-in. Shot naming generates names that follow common VFX, episodic and commercial conventions, the EXR sequence checker finds missing or truncated frames in a render folder before a vendor turnover goes out, and the LUT previewer lets you check a client's .cube on a still without opening a grading suite.

Delivery: does it pass?

The Delivery spec validator compares your file's loudness, true peak, codec and colour settings with EBU R128, ATSC A/85 and the published specs of the main platforms. It is a checklist, not a QC report — but it catches the rejections that are caused by a wrong preset rather than a real problem.

Where the numbers come from

Data rates are calibrated against manufacturers' published figures (Apple's ProRes white paper, for example), timecode follows the SMPTE drop-frame rules and loudness targets quote the standards themselves. Where a value is an estimate, the tool says so. The about page explains the method in detail, and if a figure disagrees with a primary source, tell us and we correct it.

Everything runs in your browser. Files you open are read locally and never uploaded, which is why you can safely use these tools on material that is under NDA.