#9535: PNG decoder fails processing more than a certain number of frames
-------------------------------------+-------------------------------------
Reporter: panthalassa | Owner: (none)
Type: defect | Status: new
Priority: normal | Component:
| undetermined
Version: unspecified | Resolution:
Keywords: png | Blocked By:
decoding pattern_type glob |
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by Eric Reed):
In the initial process of finding the corrupted PNG from a large batch, I
was successful with a manual binary search. It seems like OP has failed at
this step. Blender is mentioned, maybe the render had crashed partway
through and was resumed, without OP realizing that the very last file to
be rendered had not been fully written out.
The confounding variable here was probably that the timing of the error
occurring cannot be reliably used to determine which PNG is corrupt (i.e.
by watching the output frame tally). I don't fully understand why, but it
may be due to buffering done by the video encoder or similar.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9535#comment:14>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
