[FFmpeg-trac] #1296(undetermined:new): Multi-thread decoding artifact for MTS H.264

FFmpeg trac at avcodec.org
Thu May 10 21:10:15 CEST 2012


#1296: Multi-thread decoding artifact for MTS H.264
--------------------------------------+----------------------------------
             Reporter:  andreasg      |                     Type:  defect
               Status:  new           |                 Priority:  normal
            Component:  undetermined  |                  Version:  0.10.3
             Keywords:                |               Blocked By:
             Blocking:                |  Reproduced by developer:  0
Analyzed by developer:  0             |
--------------------------------------+----------------------------------
 When extracting images from an interlaced H.264 MTS file, there are
 artifacts in some of the frames.  The images are extracted inside my own
 application.  I could not figure out how to make ffmpeg run multi-threaded
 when the output is a sequence of images.

 The test video is the one linked from ticket #993:
 [http://file.meyersproduction.com/hg10/00009.MTS.zip]

 {{{
 ffprobe version 0.10.3 Copyright (c) 2007-2012 the FFmpeg developers
   built on May 10 2012 10:41:04 with gcc 4.6.3 20120306 (Red Hat 4.6.3-2)
   configuration:
   libavutil      51. 35.100 / 51. 35.100
   libavcodec     53. 61.100 / 53. 61.100
   libavformat    53. 32.100 / 53. 32.100
   libavdevice    53.  4.100 / 53.  4.100
   libavfilter     2. 61.100 /  2. 61.100
   libswscale      2.  1.100 /  2.  1.100
   libswresample   0.  6.100 /  0.  6.100
 [mpegts @ 0x32174e0] Format mpegts probed with size=2048 and score=100
 [mpegts @ 0x32174e0] stream=0 stream_type=1b pid=1011 prog_reg_desc=HDMV
 [mpegts @ 0x32174e0] stream=1 stream_type=81 pid=1100 prog_reg_desc=HDMV
 [h264 @ 0x321b3a0] err{or,}_recognition separate: 1; 1
 [h264 @ 0x321b3a0] err{or,}_recognition combined: 1; 10001
 [ac3 @ 0x321bd60] err{or,}_recognition separate: 1; 1
 [ac3 @ 0x321bd60] err{or,}_recognition combined: 1; 10001
 [ac3 @ 0x321bd60] Unsupported bit depth: 0
 [h264 @ 0x321b3a0] Increasing reorder buffer to 1
 [h264 @ 0x321b3a0] no picture ooo
     Last message repeated 1 times
 [h264 @ 0x321b3a0] no picture
 [mpegts @ 0x32174e0] max_analyze_duration 5000000 reached at 5003333
 rfps: 59.916667 0.001150
     Last message repeated 1 times
 rfps: 59.940060 0.000000
     Last message repeated 1 times
 Input #0, mpegts, from '00009.MTS':
   Duration: 00:00:36.54, start: 0.766967, bitrate: 6884 kb/s
   Program 1
     Stream #0:0[0x1011], 302, 1/90000: Video: h264 (High) (HDMV /
 0x564D4448), yuv420p, 1440x1080 [SAR 4:3 DAR 16:9], 1001/60000, 59.96 fps,
 59.94 tbr, 90k tbn, 59.94 tbc
     Stream #0:1[0x1100], 158, 1/90000: Audio: ac3 (AC-3 / 0x332D4341),
 48000 Hz, stereo, s16, 256 kb/s
 [h264 @ 0x321b3a0] err{or,}_recognition separate: 1; 10001
 [h264 @ 0x321b3a0] err{or,}_recognition combined: 1; 10001
 [h264 @ 0x321b3a0] detected 8 logical cores
 [ac3 @ 0x321bd60] err{or,}_recognition separate: 1; 10001
 [ac3 @ 0x321bd60] err{or,}_recognition combined: 1; 10001
 [ac3 @ 0x321bd60] Unsupported bit depth: 0
 }}}

 This works without problems with FFmpeg 0.9 but both versions 0.10 and
 0.10.3 have the problem when using eight threads instead of one.

 The attached files show the same extracted frame with FFmpeg 0.9 (multiple
 threads), 0.10.3 (multiple threads), and 0.10.3 (single thread).  In all
 cases, the image is scaled to 1440x810 to correct the aspect ratio.

 Please let me know if you need additional information.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1296>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list