#11494(avcodec:new): Encoding to ffv1 produces broken bitstream for specific sample with specific settings
#11494: Encoding to ffv1 produces broken bitstream for specific sample with specific settings -------------------------------------+------------------------------------- Reporter: Damian | Type: defect Höster | Status: new | Priority: normal Component: avcodec | Version: | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- **How to reproduce:** Download br2049-00006.mkv from here: https://mega.nz/file/UCw1AQ7D #-oQ_Hcob_VByBC-KSqvJ2xuV7GZkvkCJ-XOrU00zQeg Reencode like this: ffmpeg -i br2049-00006.mkv -vcodec ffv1 -pass 1 -coder 1 -context 1 -slices 24 -f null /dev/null && ffmpeg -i br2049-00006.mkv -vcodec ffv1 -pass 2 -coder 1 -context 1 -slices 24 broken-ffv1.mkv Then try to decode. I get errors like these: {{{ [ffv1 @ 0x57b2744be500] CRC mismatch F9B52803! }}} {{{ [vist#0:0/ffv1 @ 0x57b2744dec00] [dec:ffv1 @ 0x57b2744e0f40] Error while opening decoder: Invalid data found when processing input }}} ffmpeg version N-118655-g696ea1c223 on Arch Linux -- Ticket URL: <https://trac.ffmpeg.org/ticket/11494> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#11494: Encoding to ffv1 produces broken bitstream for specific sample with specific settings -------------------------------------+------------------------------------- Reporter: Damian | Owner: (none) Höster | Type: defect | Status: closed Priority: normal | Component: avformat Version: unspecified | Resolution: fixed Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by mkver): * component: avcodec => avformat * resolution: => fixed * status: new => closed Comment: Fixed in 92e310eb82e04713e55d248b65c22f0eb95afada. The encoded file is actually fine; a FFmpeg with the above commit can handle it. (When I wrote 92e310eb82e04713e55d248b65c22f0eb95afada, I thought that it could only break files encoded using slicecrc mode 2 which is currently experimental. Yet I was wrong: This bug made the decoder read the slicecrc mode as two for your file, although the encoder only used one.) -- Ticket URL: <https://trac.ffmpeg.org/ticket/11494#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg