Footage Health Check: Finding Black and Silent Spans
Footage problems hide in the middle: a lecture recorder drops a black gap, a meeting recording holds ten seconds of silence, a converted file plays badly in one stretch. Scrubbing minute by minute is hopeless — let the detector list the suspicious spans.
When to run a health check
Three typical cases. Recording: lectures, livestream replays, and screen captures occasionally drop frames or streams, leaving black gaps. Conversion: downloaded or converted files may have a damaged stretch. Pre-edit: when receiving someone else's footage, check it before it enters the timeline so you do not discover a dead middle mid-edit.
Tuning the three thresholds
Detection runs on three parameters: minimum black duration (default 500 ms — fully black frames count only past this), silence loudness (default -35 dB — below this counts as silent), and minimum silence duration (default 500 ms).
Tuning logic: noisy recordings want a lower silence threshold (say -45) so normal pauses are not flagged; to catch only real black-out accidents, raise the black-duration floor above two seconds to filter transitional black frames; hunting for sub-second stream drops? Drop the floor to 200 ms.
Reading the report and what to do next
The output is a list of time spans labeled as black or silent. It is a list of suspects, not verdicts: black may be an accident or an intentional transition; silence may be a fault or a pause. Confirm each against the content.
Then fix by type: dead black spans get cut out with the middle-segment remover; long silences get batch-removed; if the problem came from a conversion, go back to the source and reconvert, and verify the specs (see the codec checker guide).