Why does -v error find nothing in a damaged file?
FFmpeg reports some damage as a warning, not an error. We wrote 4 KiB of zeros into the middle of a different keyframe of in.mp4 20 times. A decode at -v error flagged 16 of the 20 files. A decode at -v warning flagged all 20, and each one had between 5 and 48 damaged frames.
ffmpeg -v error -i damaged.mp4 -f null -No output and exit code 0, yet 2 s of this file are smeared green (the second picture above). At -v warning it prints corrupt decoded frame.
On the clean in.mp4, -v warning printed nothing, so the lower log level added no noise.



