Why Sound Roll Does Not Mean Sound Timecode Is Present

Seeing Sound Roll in a handoff means the file carries a sound-roll field; it does not mean the same handoff also carries sound timecode. ALE and CSV include a Sound Roll column, and the PDF body carries a sound-roll column as well (its header follows the interface language, so an English screen reads Audio Roll), but none of these export snapshots has a sound-timecode field, so the concepts remain separate.

Sound Roll is an identity clue for sound media, not a sound time position; the presence of that column does not make sound timecode appear in the handoff.

Where the Sound Roll column comes from

In ALE and CSV, Sound Roll is derived from the sound-roll number stored on the camera record and then formatted into the displayed roll text. When a usable value is missing the three formats differ: an ALE row with no camera row at all prints a default roll, a CSV row leaves the cell empty, and a PDF row prints a dash. A normal-looking roll string is therefore not proof of verification against an audio file. It should be treated as an identity clue that still needs checking, not as a sound time position.

In a multicamera record, the sound-roll value is camera-level, so different cameras in the same take must be read separately. ALE and CSV write one row per camera, while a PDF row takes only one camera, so the other cameras’ sound rolls never appear on that row. The handoff also carries Tracks, MOS and Wild Track on the sound side, all derived from on-set markers rather than read from an audio file. Whether those values actually correspond to the same set of recorded audio files cannot be established from that column alone. The column also does not decide whether independent sound was recorded on set or whether the audio files are present in the same delivery package.

Why none of the four handoff formats exposes sound timecode

The key point is not that a sound-timecode column was later removed; the export snapshot itself has no sound-timecode field. As a result, ALE, CSV, PDF, and FDX do not contain a sound-timecode column for the receiver to read. The absence is in the export data structure, not a case of hiding an existing value during rendering.

For that reason, Sound Roll should not be treated as a substitute for sound timecode, and picture timecode cannot be used to infer the audio file’s own starting timecode. This should not be described as a timecode-synchronization capability, and the roll field should not be presented as performing timing alignment automatically. The receiver needs to return to the actual audio files and its own sound log to verify each file’s embedded timecode and starting point.

The sound-side clue in the handoff is a roll identifier, not sound timecode; when a time position is needed, the receiver should verify it from the audio files and sound log.

How the roll identifier and picture timecode can be used together

In ALE and CSV the receiver can use the sound-roll identifier and picture timecode in the same check (the PDF body has no timecode column), but their relationship is still established during receiving. The roll identifier identifies the claimed sound roll, while picture timecode identifies the picture record’s time position. Combining those two clues does not create a sound-timecode column that was not exported.

Timing correspondence must therefore be established from the receiver’s sound log, audio-file information, and picture records. What an ALE File Is Actually For describes what an exchange file carries and where its boundaries are, and the missing sound-timecode field belongs on the boundary side of that distinction. The receiver should verify the relationship instead of letting a complete-looking roll identifier stand in for timecode evidence.

Why Reel and Tape are not two independent checks either

ALE has another field relationship that can create a false sense of double confirmation: Tape and Reel use the same derived value. Although they appear as two columns, their source is the same, so agreement between those columns should not be treated as confirmation from two independent sources. Identity still needs to be checked against the media or the on-set record.

The same principle applies to the sound side: Sound Roll is an identity field, not a second timecode chain. If the receiving workflow also needs to understand channel information, the ALE Tracks column is derived from whether the take is marked MOS and does not expose a channel count; that boundary is the subject of What the Tracks Column Does Not Tell You. Each exported field should be read for what it contains rather than combined into data that is absent.

What should be left to the audio file itself during receiving

After receiving the handoff, first check whether the Sound Roll value agrees with the sound log, then inspect the actual audio file for its own timecode and starting point. The picture handoff provides picture-side records, but with no sound-timecode column the sound-to-picture timing relationship is not already verified. Any further correspondence requires evidence from the receiver’s own media.

This also means that whether independent audio files are included, and whether they belong to the same delivery package, should be determined from the media actually received. The app does not use the Sound Roll field to decide those external facts for the receiver. Finally, the receiver should verify the timecode and starting point carried by the audio files themselves.

FAQ

Is Sound Roll the same thing as sound timecode?

No. Sound Roll is a sound-roll identity field, while the current handoff does not expose a sound-timecode column.

Can Sound Roll by itself establish picture-to-sound timing?

That conclusion cannot be made from the roll field. The receiver needs to check the roll identifier, picture record, sound log, and the audio file’s own timecode and starting point together.

Can Tape and Reel in an ALE confirm each other independently?

They should not be treated as two independent signals because Tape and Reel use the same derived value. The receiver still needs to verify media identity against the source media or on-set record.

Where should the sound time position be verified?

It should be checked from the actual audio files and the sound log. The receiver should verify each audio file’s own timecode and starting point rather than inferring a sound-timecode field from Sound Roll.

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