YENRA VIDEO TRANSFER LOG
Use one copy per tape, disc side, or source file set. Save this log beside the
retained transfer. Keep the original media; work on copies when converting.
Guide: https://yenra.com/digital-video/

SOURCE IDENTIFICATION
Source ID:
Label wording and label-photo filename:
Recording date (known / estimated / unknown):
Camera/recorder model and region, if known:
Tape format and recording mode, if known:
Disc type / side / VIDEO, VR or AVCHD mode / finalization status, if applicable:
Condition and previous problems:
Expected events, titles, duration and known gaps:

TRANSFER METHOD
Transfer date and operator:
Playback device / firmware / manual used:
Interface and connections:
Computer OS, capture/copy software and version:
Playback and output settings (including HDV-to-DV conversion, if applicable):
Method (native stream capture / analog capture / file copy / disc image):
Destination folder and full list of retained files:
Error or dropped-frame report filename:
Read errors, interruptions and timestamps:

FILE AND CONTENT CHECKS
Inspection report filename:
Video codec / container / width x height:
Frame rate / scan type and field order / aspect ratio:
Color information and bit depth, where available:
Audio codec / sample rate / channels and track count:
Captions, subtitles, timecode and other required metadata:
Captured duration and completeness against expected events:
Beginning, ending and scene-boundary checks:
Full review completed? If not, record what was reviewed:
Audio sync and channel checks, including near the end:
Motion, shape and playback errors:
Unresolved issues and next action:

COPIES AND DERIVATIVES
Retained original/transfer files (leave unchanged):
Viewing/editing derivative files:
Conversion software, version and settings:
Processing applied (deinterlacing, cropping, scaling, enhancement):
Streams or metadata changed/omitted:
Checksum method and baseline manifest filename:
Backup locations and dates:
Checksum comparisons and playback from backup:
Next planned integrity/readability check:

INTERPRETING RESULTS
A matching file checksum confirms byte identity to its baseline; it does not
prove complete capture or correct playback. A valid viewing file can omit
events or tracks. Verify the expected content as well as file integrity.
Document unresolved faults before marking a transfer complete.