What a CSV Handoff Carries That an ALE Does Not

The CSV detail sheet and the ALE are not the same data with different file extensions. CSV is a tabular detail sheet for human and spreadsheet review, while ALE is an exchange list for a receiving workflow; they differ in field coverage, missing-value behavior, encoding, and field meaning. The CSV carries more camera and shooting detail, but it is still not a media manifest and it does not provide channel mapping or sound timecode.

The important difference between formats is not merely column count; it is what each field means, where it came from, and how the receiver is expected to check it.

The CSV carries more camera and shooting detail

Compared with the ALE, the CSV includes a wider set of shot- and camera-level values. Lens, filter, ISO, aperture, shutter, aspect ratio, resolution, shot size, shot angle, and movement are represented in the tabular handoff.

It also contains several state fields for camera-level VFX, plate, clean, and reference conditions, plus a shooting date. Keep one boundary in view: a column in an export does not prove that the current app has an on-set entry path for that field. Some sound-state columns exist in the file structure but must not be turned into claims about available recording controls.

Take notes and camera notes also occupy separate columns. During CSV generation, line breaks, carriage returns, and tabs in text are flattened to spaces. The receiver therefore gets table-safe text rather than a promise of character-for-character note preservation.

The two rating columns do not mean the same thing

The CSV has a text rating and a Boolean Circle column. The text rating can be Circle, Keep, Hold, or N/G, with an unmarked take left empty. The Boolean Circle field is narrower: only the Circle rating produces TRUE; the other cases produce FALSE.

A take marked Keep therefore carries Keep in the text rating while its Boolean Circle field is FALSE. The Boolean column cannot be read as the complete meaning of whether a take was treated as selected on set. It is a derived test for one specific rating.

Rating is a text status. Circle is a narrower Boolean condition. They are not interchangeable fields.

A receiving template that reads only the Boolean can miss distinctions carried by the text rating. A template that reads only the text rating should not assume it is identical to every internal state field either.

More columns still do not provide media location or sound routing

Additional detail does not turn the CSV into a complete media relationship file. The current output does not contain media paths, channel mapping, or sound timecode. If the receiving workflow needs file location or microphone-to-channel relationships, that information has to come from the media and other handoff records.

Likewise, Filename, reel, and clip fields do not by themselves make the CSV a verified media manifest. Compare those identifiers with actual filenames, reels, and the on-set record.

Encoding and text handling differ from the ALE

The CSV is written with a byte-order mark, while the ALE is not. Both use LF line endings, but actual compatibility with a receiving environment still needs to be tested. When text opens with the wrong characters or columns shift, encoding, separators, and text handling should be checked before assuming the business fields are wrong.

CSV data values also pass through their own escaping path. Newlines and tabs are flattened, while commas and quotation marks trigger the generator’s quoting rules. That describes the current output behavior; it should not be expanded into a claim that the file conforms to an external CSV specification.

Dates do not use one literal format across every handoff

The CSV Date field is written in a fixed Gregorian machine format, yyyy-MM-dd. A report header in another delivery format follows the device environment’s date formatting instead. Those outputs serve different reading contexts, so their date strings should not be promised to match character for character.

For cross-file comparison, treat formatting differences as expected and then verify whether the fields refer to the same shooting date. A different string does not automatically mean a different date, and a matching string does not replace source verification.

FAQ

What does the CSV mainly add beyond the ALE?

It adds more camera, optical, composition, state, and date detail, including lens, filter, ISO, aperture, shutter, resolution, shot size, shot angle, and movement.

Why can Rating and Circle appear to disagree?

They encode different things. Rating stores the text status, while the Boolean Circle field is TRUE only for the Circle rating. A Keep take can therefore carry Rating=Keep and Circle=FALSE.

Does the CSV preserve notes exactly as entered?

No. Line breaks, carriage returns, and tabs are flattened to spaces during generation, so the receiving side gets text normalized for a table row.

Do the extra CSV fields provide media paths and audio channel mapping?

No. The current CSV still omits media paths, channel mapping, and sound timecode. Those relationships must be verified from the media and other handoff information.

Axiom One LLC — SlateX. Figures current as of 24 September 2026.