[FFmpeg-trac] #156(undetermined:open): Full HD Material from Canon 5D treated as 1920x1088

FFmpeg trac at avcodec.org
Sun Dec 11 23:44:00 CET 2011

#156: Full HD Material from Canon 5D treated as 1920x1088
             Reporter:  rmk          |                    Owner:
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0

Comment (by yellow):

 As far as I've tested Quicktime crops bottom 8.

 Although Canon 5D MKII appears to have 8 rows of black this is not the
 case for the other cameras in the range which are also 1088 h264 AVC in a
 mov container, they actually have 8 rows of image data. Easy to see
 comparison of a QT decoded 1088 frame and a ffmpeg decoded frame overlaid
 in Gimp for example will show QT crops 8 off, ffmpeg gives full 1088 lines
 of usable image data, no so called black padding not surprising since
 there is more than enough data coming off the 18MP camera sensor, even
 line skipped without the need to add black padding. ;-) Why the 5D does
 black is odd.

 What does appear suspect with the Canon movs is that ffmpeg treats them as
 yuvj420 not yuv420 so when transcoding to say lossless huffyuv the full
 range luma levels in the original camera file are squeezed into 16 - 235
 unless the movs are first remuxed to something like mkv.

Ticket URL: <http://ffmpeg.org/trac/ffmpeg/ticket/156#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list