corruptData

What the batch decode flows do when FFmpeg reports damaged data. CorruptData.Skip by default, which is what every backend always did, silently.

Set it before collecting. Changing it mid-flow applies from the next packet, which is well defined but rarely what anyone means.

What the batch decode flows do when FFmpeg reports damaged data. CorruptData.Skip by default, which is what every backend always did, silently.

Set it before collecting. Changing it mid-flow applies from the next packet, which is well defined but rarely what anyone means.

What the batch decode flows do when FFmpeg reports damaged data. CorruptData.Skip by default, which is what every backend always did, silently.

Set it before collecting. Changing it mid-flow applies from the next packet, which is well defined but rarely what anyone means.

What the batch decode flows do when FFmpeg reports damaged data. CorruptData.Skip by default, which is what every backend always did, silently.

Set it before collecting. Changing it mid-flow applies from the next packet, which is well defined but rarely what anyone means.

What the batch decode flows do when FFmpeg reports damaged data. CorruptData.Skip by default, which is what every backend always did, silently.

Set it before collecting. Changing it mid-flow applies from the next packet, which is well defined but rarely what anyone means.