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 provides no channel map; sound start timecode has its own column, and a value failing the shape check ships empty.

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 carries several state flags: VFX, plate, clean and reference sit on the camera of that take, MOS and wild track sit on the take itself, all of them set on the record form, and a shooting date comes along too. Read the two sound flags together: when MOS and wild track are both on, the file ships the take as silent; when both cells read FALSE, that means either the row carries a sync-sound fact or it carries none, and the cell alone does not separate the two.

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.

Read the three rating-related columns by their own rules

Rating is fixed English text: Circle, Keep, Hold, or N/G; an unmarked take is empty. The Circle column uses a narrow rule: it writes TRUE only when the rating itself is Circle, and writes FALSE for every other case.

Circled On Set is also derived from the same rating value, but uses a broader rule: both Circle and Keep write TRUE, while the other ratings write FALSE. A Keep take therefore carries Rating=Keep, Circle=FALSE, and Circled On Set=TRUE in the same row.

Rating outputs the text label, Circle tests only for the Circle rating, and Circled On Set treats both Circle and Keep as circled on set. These are three derivations of one rating value, not three independent states.

A receiving template should map the columns separately. Reading only Circle misses the distinctions among Keep, Hold, and N/G; reading only Rating does not replace the broader circled-on-set interpretation in Circled On Set. The columns are not interchangeable and should not be treated as independent sources that validate one another.

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 carries Source File Name and Source File Path, plus a Sound TC column for the sound’s start position. The two source-file cells have two routes: you type them on set, or the software fills those same cells when media are brought in from a file, and a value you already typed is never overwritten. The sound start timecode has only the transcription route. Anything neither route supplied stays empty. It still does not say where the media sits on the receiver’s machine, and it has no channel map: file location and microphone-to-channel relationships have 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. For why no handoff can hand back a path to the media, see “Why a Handoff Cannot Hand Back a Path to the Media”.

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 output’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?

All three derive from the same rating value under different rules: Rating stores the text label, Circle is TRUE only for the Circle rating, and Circled On Set is TRUE for both Circle and Keep. A Keep take therefore carries Rating=Keep, Circle=FALSE, and Circled On Set=TRUE.

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 flattened for a table row.

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

Partly. The two source-file cells get their value from one of two routes: you type it on set, or the software fills the same cells when media is brought in from a file — a value you already typed is never overwritten. The sound start timecode has only the first route. Whatever never arrived stays empty. The file still omits channel mapping and does not point at media on your machine. Verify location and sound relationships from the media and other handoff information.

Axiom One LLC — SlateX