CorruptData
What decoding does when FFmpeg reports damaged data.
Every backend used to do Skip and say nothing at all: a packet FFmpeg answered AVERROR_INVALIDDATA for was treated exactly like a packet that had been consumed, so a damaged file decoded to fewer frames than it should have with no error, no warning and no count. A caller checking a recording for damage, or transcoding an archive and needing to know whether the result is whole, had nothing to read.
The behaviour itself is still the default, because skipping damage IS what a player should do: one broken frame in a film should not end playback. What changed is that it is now a decision with a name, and that skipping is counted rather than invisible.
Entries
Refuse at the first damaged packet or frame, as FFmpegException carrying FFmpegError.InvalidData.
Properties
Functions
Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
Returns an array containing the constants of this enum type, in the order they're declared.