The Render Log Remembers What The Folder Forgot

This file is 17,479 bytes. It holds 656 words across 154 lines, and its sha256 hash begins 8709906ba70e443d. Underneath those numbers sit 22 records, carrying ids 01 through 22 with no gap anywhere in the sequence. The schema is 6 keys: an id, a duration, a still URL, a clip URL, a done flag and an error field. 20 of the 22 rows carry 5 of those keys, 1 row carries 4 and 1 row carries 3. Now put it beside the list it belongs to. That list is 91,211 bytes, 12,934 words and 39 rows. The log is 19.16 per cent of the list by bytes and 5.07 per cent of it by words, which works out at 794.5 bytes of log for every record it holds and 6.773 seconds of film for every line. A log is not a copy of the plan. It is the smaller file that can contradict it.

Read the 2 files against each other and the first thing that shows is not an error. It is silence. The log covers 22 of the 39 priced ids, and on all 22 of them the duration agrees with the shot list exactly. Not 21 of 22. 22 of 22. The list declares 149 seconds across those 22 ids and the log writes 149 seconds back, because 17 rows sit at 7 seconds and 5 sit at 6. That total was not renegotiated in the log and it was not rounded into a range. A render log that repeats the declared duration on every row it touches is doing exactly what a delivery record is supposed to do: it proves the film was attempted at the length that was priced, and it leaves the disagreement for the rows it never reached. The 2 numbers to hold on to from this section are 149 and 149.

The done flag is the whole point of the file. 20 of the 22 records carry one and it reads true. 20 finished rows carry 135 of the 149 logged seconds, which is 90.60 per cent of the work the log actually reached. Measured against the full 252 seconds the list priced, 135 seconds is 53.57 per cent. The remaining 2 records carry no flag at all, and 2 blanks is not a rounding error in a file this size, it is the entire difference between a folder and a record. The other columns tell the same story in the same direction: id is present on 22 rows, duration on 22, a still URL on 21 and a clip URL on 20. Every one of those counts is checkable against the row it sits on, and none of them needs a person to remember which shot was rendered last Tuesday. A done flag on every row is not bookkeeping. It is the only honest answer to the question of what has actually finished.

The 2 records without a finished flag carry an error instead, and they are specific. Row 08 stopped with the words video task produced no output, followed by a task id and a uuid long enough to look like a decision. Row 22 stopped with BALANCE EXHAUSTED, code 97, on a 7 second shot. Row 08 holds 1 of the 21 still URLs and no clip. Row 22 is thinner still: 3 keys, an id, a duration and the refusal, with no image attached anywhere on the line. That is 14 seconds of the 149 logged seconds stopped dead, and both stops are written down on a numbered row next to the length of the shot they killed. This is what a folder can never do. A folder shows a missing file and lets you guess. A log writes BALANCE EXHAUSTED on row 22 and makes the guess unnecessary. The 2 empty flags are worth more than the 20 ticks, because the ticks confirm what you already hoped and the blanks tell you where the money and the render actually stopped.

17,479 bytes. 22 records. Ids 01 to 22, no gaps.

The list prices 39 shots. The log covers 22. The difference is 17 ids, running 23 through 39, and every one of them is priced, prompted, referenced and never logged at all. Those 17 ids account for 103 of the 252 declared seconds, which is 40.87 per cent of the film. Add the 14 seconds stopped dead on rows 08 and 22 and the position reads 117 of 252 seconds with no moving frame, or 46.43 per cent. 1 of those 17 ids is the difference between a production that is nearly finished and one that is half shot, and only the log can tell you which. The 22 logged rows also carry 21 distinct still URLs and 20 distinct clip URLs, so the file holds the links back to the frames themselves rather than a note that they once existed. When the folder is cleaned, moved or renamed, the count survives. When the log is read against the list, the 17 missing ids are 17 named line items instead of a feeling on the last day of the edit.

Two numbers decide whether a production is on schedule or merely busy: the seconds priced in the plan and the seconds carrying a finished flag in the log. Here they read 252 and 135, and the 117 second gap between them is a line item because the rows named it first. That arithmetic travels outside film. 210 energy systems were deployed across Africa and Asia on the same rule, that each unit carries a flag when it is live, because a deployment counted from a folder counts intent and a deployment counted from a record counts units. A shot list is the price. The render log is the receipt. The probability that a folder of 39 prompts gets read as 39 finished shots is not small, and the check that settles it is 2 cells wide: 252 declared, 135 done. The render log remembers what the folder forgot. Keep more of yourself, for longer.