SansferDocs PDF sansfer.com

Part 4 · Records

19

Reports, manifests and ASC MHL

Proof that travels with the footage: a report for people, manifests and ASC MHL for software, all written next to the media on every drive.

Reports

A report states the result plainly, VERIFIED, INCOMPLETE or CANCELLED, and lists every file. There are three kinds:

FormatWhat it holdsFor
PDFThe project and production details, the transfer (start, end, duration, copy order, checksum, files, data, speeds, ASC MHL), the card with its format and volume ID, every destination with its result, warnings, and every file with its size, checksum and result.Clients, producers, insurers, the camera report.
CSVOne line per file and destination: path, original name, size, modification date, checksum, status and any error.Spreadsheets and your own checks.
JSONThe complete record of the transfer.Scripts, databases and asset management.

Saving reports automatically

In Settings › Reports, choose which reports are saved when a transfer ends, and where:

  • Card folder (_Sansfer): next to the footage, in the card's _Sansfer folder on every drive.
  • Project folder (_Sansfer Reports): all reports of a project together, in a _Sansfer Reports folder in the project folder on every drive.

Reports are named after the card, the time and the result, for example Sansfer Report FX9_2 20261118-094012 VERIFIED.pdf, and never overwrite an existing file. Presets can set their own report options.

Checksum manifests

With Write a checksum manifest into each destination folder on (the default, in Settings › Verification), every card folder gets a _Sansfer folder with the checksums of this transfer, in two forms:

  • Sansfer_<time>_<id>.json: the full manifest.
  • Sansfer_<time>_<id>.sha256 or .xxh64: one line per file, checksum and path, in the standard format other tools read.

Checking a copy yourself

Anyone can check a copy against its manifest, without Sansfer, with the standard tools in Terminal. Go to the card folder and run, for a SHA-256 transfer:

cd "/Volumes/SSD_A/Coastal Documentary/FX9_2"
shasum -a 256 -c _Sansfer/*.sha256

Every file should report OK. For an XXH64 transfer, use a tool that reads XXH64 lists, such as xxhsum -c (from the xxHash package), or check the ASC MHL history.

ASC MHL PRO

With ASC MHL on and XXH64 as the checksum, every card folder gets an ascmhl folder: the industry-standard media hash list, version 1.0. It records every file's checksum and who made the copy, when and with what. Each transfer into the same folder adds a generation, such as 0001_FX9_2_2026-11-18_084012Z.mhl. A history that was already on the card is kept and extended, so the chain from camera to archive stays complete.

Post houses and DIT tools that support ASC MHL can check the folder directly, for example with the open-source ascmhl tool:

ascmhl verify "/Volumes/SSD_A/Coastal Documentary/FX9_2"

The operator name in Settings › Reports is written into the history as the person who made the copy.