#3923(undetermined:new): decode h264 video has some error and bad image
#3923: decode h264 video has some error and bad image --------------------------------------+---------------------------------- Reporter: ytliao | Type: defect Status: new | Priority: normal Component: undetermined | Version: 2.3 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: I play some h264 video with MPC (LAV filter), VLC, Pot Player (ffmpeg), and found there are some bad images. then I try ffplay, same problem. (there are all ffmpeg based as I know) meanwhile I test Microsoft windows media player, it plays fine. QuickTime Player has some visible blocks but it looks much better than ffmpeg. And some other decoders they all play OK. Can someone please to help to check what's wrong with attached h264 video, can ffmpeg play these video without visible bad images ? Following is ffplay log {{{ D:\video\tmp>ffplay.exe 02120003.MOV ffplay version N-66093-g17ad5fb Copyright (c) 2003-2014 the FFmpeg developers built on Sep 3 2014 22:01:47 with gcc 4.8.3 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab le-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable- libcaca -- enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-lib modplug --enable-libmp3lame --enable-libopencore-amrnb --enable- libopencore-amrw b --enable-libopenjpeg --enable-libopus --enable-librtmp --enable- libschroedinge r --enable-libsoxr --enable-libspeex --enable-libtheora --enable- libtwolame --en able-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable- libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable- libx265 --enable-libxavs --enable-libxvid --enable-decklink --enable-zlib libavutil 54. 7.100 / 54. 7.100 libavcodec 56. 1.100 / 56. 1.100 libavformat 56. 4.100 / 56. 4.100 libavdevice 56. 0.100 / 56. 0.100 libavfilter 5. 0.103 / 5. 0.103 libswscale 3. 0.100 / 3. 0.100 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 0.100 / 53. 0.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '02120003.MOV': 0B f=0/0 Metadata: major_brand : qt minor_version : 512 compatible_brands: qt creation_time : 2002-10-29 03:32:30 Duration: 00:03:00.12, start: 0.000000, bitrate: 14151 kb/s Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661), yu v420p, 1920x1080, 14019 kb/s, 30.06 fps, 30.08 tbr, 1k tbn, 60 tbc (default) Metadata: creation_time : 2002-10-29 03:32:30 handler_name : DataHandler Stream #0:1(eng): Audio: pcm_s16le (sowt / 0x74776F73), 8000 Hz, 1 channels, s16, 128 kb/s (default) Metadata: creation_time : 2002-10-29 03:32:30 handler_name : DataHandler [h264 @ 067c0800] concealing 3837 DC, 3837 AC, 3837 MV errors in I frame 115.24 A-V: 0.002 fd= 97 aq= 8KB vq= 806KB sq= 0B f=0/0 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/3923> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#3923: decoding damged h264 video shows strong artefacts -------------------------------------+------------------------------------- Reporter: ytliao | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by cehoyos): * reproduced: 0 => 1 * component: undetermined => avcodec * priority: normal => important * version: 2.3 => git-master * keywords: => h264 regression Comment: The original sample is in http://samples.ffmpeg.org/ffmpeg- bugs/trac/ticket3923/, I attached a remuxed sample that shows identical behaviour with FFmpeg, WMP and QT. WMP indeed shows no visible artefacts for the file, QT shows approximately the same artefacts as FFmpeg before 3af2de76 Current FFmpeg shows significantly stronger artefacts, they are also visible with the attached I-frame but that did not look better with older versions of FFmpeg. -- Ticket URL: <https://trac.ffmpeg.org/ticket/3923#comment:1> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#3923: decoding damaged h264 video shows strong artefacts -------------------------------------+------------------------------------- Reporter: ytliao | Owner: Type: defect | Status: new Priority: important | Component: avcodec Version: git-master | Resolution: Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- -- Ticket URL: <https://trac.ffmpeg.org/ticket/3923#comment:2> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
#3923: decoding damaged h264 video shows strong artefacts -------------------------------------+------------------------------------- Reporter: ytliao | Owner: Type: defect | Status: closed Priority: important | Component: avcodec Version: git-master | Resolution: fixed Keywords: h264 | Blocked By: regression | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by michael): * status: new => closed * resolution: => fixed Comment: Fixed in 033a5334badd8af48f13c6fd1e6827f8e3f2c2f3 -- Ticket URL: <https://trac.ffmpeg.org/ticket/3923#comment:3> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg