Opened 4 years ago

Closed 4 years ago

#3923 closed defect (fixed)

decoding damaged h264 video shows strong artefacts

Reported by: ytliao Owned by:
Priority: important Component: avcodec
Version: git-master Keywords: h264 regression
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: no

Description

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

Attachments (2)

02120003_91_94_remux.mov (2.4 MB) - added by cehoyos 4 years ago.
frame16.h264 (168.2 KB) - added by cehoyos 4 years ago.

Change History (5)

Changed 4 years ago by cehoyos

Changed 4 years ago by cehoyos

comment:1 Changed 4 years ago by cehoyos

  • Component changed from undetermined to avcodec
  • Keywords h264 regression added
  • Priority changed from normal to important
  • Reproduced by developer set
  • Summary changed from decode h264 video has some error and bad image to decoding damged h264 video shows strong artefacts
  • Version changed from 2.3 to git-master

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.

comment:2 Changed 4 years ago by cehoyos

  • Summary changed from decoding damged h264 video shows strong artefacts to decoding damaged h264 video shows strong artefacts

comment:3 Changed 4 years ago by michael

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.