Log Profile
A log profile stores brightness logarithmically to retain more dynamic range in one file.
What this is about
Shooting log is a promise to grade later. The camera hands over a washed-out, grey image that nobody would show a client, but it carries far more information between the darkest and brightest parts of the frame than a baked-in profile does. That only pays off with enough bit depth and a colourist who reshapes it afterwards. On set, the crew monitors through a conversion LUT so the director sees a sensible picture while the recording stays flat. A project that never books a grade is better off shooting a normal profile.
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:
- Log without a planned grade wastes the advantage and delivers a dull image instead
- Monitor through a conversion LUT on set so nobody judges exposure on the flat signal
- Log needs bit depth: ten bit or more, otherwise the grade tears the gradients apart
With TillyGen
If a grading pass is part of the plan in TillyGen, the decision to shoot log stops being a camera preference and becomes a scheduled step.
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.
Frequently asked
Should we shoot log for a two-day corporate job?
Only if someone grades it. Without a grading day in the schedule, a well-set standard profile delivers a better image with less handling.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.