Changes between Initial Version and Version 1 of Ticket #10772
- Timestamp:
- Jan 2, 2024, 12:30:50 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10772 – Description
initial v1 1 1 Summary of the bug: 2 2 3 The codec_whitelist feature, as introduced in 5c8eb16769e581f828ce420373c558c190185cc1, appears to block codecs from decoding, but it does not prevent automatic codec selection from picking a blocked codec .3 The codec_whitelist feature, as introduced in 5c8eb16769e581f828ce420373c558c190185cc1, appears to block codecs from decoding, but it does not prevent automatic codec selection from picking a blocked codec (and thus it does not make ffmpeg behave as if only the listed codecs were compiled in, which I presume was the intent - it is at least what the Chromium developers believe the intent was in https://source.chromium.org/chromium/chromium/src/+/02508a7461cde79277a7e5e55f1704d3fb6a5f7a). 4 4 5 5 Thus, when the feature is used and one wants to play/decode a file whose preferred codec is not on the whitelist, but a different codec is on the whitelist that can decode the file, decoding will fail unless explicitly selecting the decoder.


