Verification on Seatbelt

ASC MHL

Mon, 01 Jan 0001 00:00:00 +0000

Seatbelt is built around the industry standard ascmhl hash lists.

ascmhl creates a chain of custody by tracking every copy made from the original source media. It is commonly used in production workflows to safeguard media from capture through to archival.

This is especially useful when working with large datasets across multiple users and storage locations, where it helps prevent corrupted or altered files from being unknowingly propagated.

Seatbelt is validated against the current ASC MHL schema (v2.0).

Hashing algorithms

Mon, 01 Jan 0001 00:00:00 +0000

Seatbelt uses xxHash by default; an extremely fast, non-cryptographic hash that verifies file integrity without slowing down the transfer. For a typical camera offload, the verification overhead is barely noticeable.

xxHash is widely trusted in the media and data-management industry and catches even single-bit errors with near-perfect reliability.

For conformance to ASC MHL we also support md5, sha1 and c4.

Verification modes

Mon, 01 Jan 0001 00:00:00 +0000

Seatbelt offers three basic verification modes:

Source & Destination

Every file is hashed at the source, copied, then hashed again at the destination. If the two checksums match, the file is confirmed good. If they don’t, Seatbelt flags it immediately. This is the only mode that supports ASC MHL manifests.

Source Only

For managing multiple backups from a single source, we check the source against itself during and after transfer. If a drive is about to go bad, or read errors appear - you can catch it in time.