How do vrecord and QCTools document capturing and checking videotape transfers, and what do they record as fixity and metadata?
vrecord captures via MediaArea's ffmpeg-ma with Blackmagic cards (or AVFoundation for DV on macOS) to FFV1 version 3 with GOP 1 and slice CRCs, writes a framemd5 and logs by default (QCTools XML highly recommended; frame MD5s catch some dropped frames), and checks output against a MediaConch policy (Matroska >= 4, FFV1 >= 3.4, GOP 1). QCTools stores per-frame signal metrics (signalstats, cropdetect, psnr, ssim, ebur128) in a report for review. Neither is a standards conformance tool.
vrecord captures via MediaArea's ffmpeg-ma with Blackmagic cards (or AVFoundation for DV on macOS) to FFV1 version 3 with GOP 1 and slice CRCs, writes a framemd5 and logs by default (QCTools XML highly recommended; frame MD5s catch some dropped frames), and checks output against a MediaConch policy (Matroska >= 4, FFV1 >= 3.4, GOP 1). QCTools stores per-frame signal metrics (signalstats, cropdetect, psnr, ssim, ebur128) in a report for review. Neither is a standards conformance tool.
Curator qualifications: Code and documents read 2026-10-22; nothing captured or played. analog_digitization.md and QCTools filter descriptions not re-read.
Limitations: Code and documents read 2026-10-22; nothing captured or played.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://github.com/amiaopensource/vrecord/tree/e28d27415c34b583bef525752f730b490a80ff39",
"note": "vrecord script at e28d2741 (raw), L2222 and policy L3040, L3080-3081; vrecord README.md at e28d2741 (raw), L43-46, L63; vrecord Resources/Documentation/settings.md at e28d2741 (raw), L13, L58, L60; QCTools docs/data_format.md at 29bc627d (raw); QCTools README.md at 29bc627d (raw), L72-73"
},
{
"url": "https://github.com/bavc/qctools/tree/29bc627d7a3b4048d3e2ac250ca20adb1ba39cd2",
"note": "vrecord script at e28d2741 (raw), L2222 and policy L3040, L3080-3081; vrecord README.md at e28d2741 (raw), L43-46, L63; vrecord Resources/Documentation/settings.md at e28d2741 (raw), L13, L58, L60; QCTools docs/data_format.md at 29bc627d (raw); QCTools README.md at 29bc627d (raw), L72-73"
}
]
}Evidence claims
- [sourced_fact] vrecord captures via MediaArea's ffmpeg-ma with Blackmagic cards (or AVFoundation for DV on macOS) to FFV1 version 3 with GOP 1 and slice CRCs, writes a framemd5 and logs by default (QCTools XML highly recommended; frame MD5s catch some dropped frames), and checks output against a MediaConch policy (Matroska >= 4, FFV1 >= 3.4, GOP 1). QCTools stores per-frame signal metrics (signalstats, cropdetect, psnr, ssim, ebur128) in a report for review. Neither is a standards conformance tool. · locator: vrecord script at e28d2741 (raw), L2222 and policy L3040, L3080-3081; vrecord README.md at e28d2741 (raw), L43-46, L63; vrecord Resources/Documentation/settings.md at e28d2741 (raw), L13, L58, L60; QCTools docs/data_format.md at 29bc627d (raw); QCTools README.md at 29bc627d (raw), L72-73 source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |