Opened 12 years ago

Last modified 6 years ago

#1484 open enhancement

Width and Height wrong on mov file

Reported by: DonMoir Owned by:
Priority: wish Component: undetermined
Version: git-master Keywords: mov cropping h263
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: no

Description (last modified by Carl Eugen Hoyos)

This file is from ticket #126.

http://sms.pangolin.com/temp/r-2002-30.mov

The reported width and height from ffmpeg is: 352x288

The real width and height is: 320x240

Plays correctly in VLC and QuickTime. MediaInfo also reports the correct width and height. Playback is incorrect for ffmpeg related code because of width/height problem.

C:\ffmpeg-dev\bin>ffplay c:\r-2002-30.mov
ffplay version N-41843-gc17808c Copyright (c) 2003-2012 the FFmpeg developers
  built on Jun 22 2012 17:41:57 with gcc 4.7.1
  configuration: --disable-static --enable-shared --enable-gpl --enable-version3
 --disable-w32threads --enable-runtime-cpudetect --enable-avisynth 
 --enable-bzlib --enable-frei0r --enable-libass --enable-libcelt
 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype
 --enable-libgsm --enable-libmp3lame --enable-libnut --enable-libopenjpeg
 --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora
 --enable-libutvideo --enable-libvo-aacenc --enable-libvo-amrwbenc
 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs
 --enable-libxvid --enable-zlib
  libavutil      51. 61.100 / 51. 61.100
  libavcodec     54. 29.100 / 54. 29.100
  libavformat    54. 11.100 / 54. 11.100
  libavdevice    54.  0.100 / 54.  0.100
  libavfilter     2. 82.100 /  2. 82.100
  libswscale      2.  1.100 /  2.  1.100
  libswresample   0. 15.100 /  0. 15.100
  libpostproc    52.  0.100 / 52.  0.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'c:\r-2002-30.mov':
  Metadata:
    creation_time   : 2001-08-08 17:13:07
  Duration: 00:03:27.66, start: 0.000000, bitrate: 811 kb/s
    Stream #0:0(eng): Video: h263 (h263 / 0x33363268), yuv420p, 352x288 [SAR 12:
11 DAR 4:3], 435 kb/s, 15 fps, 15 tbr, 1500 tbn, 29.97 tbc
    Metadata:
      creation_time   : 2001-08-08 17:13:07
      handler_name    : Apple Alias Data Handler
    Stream #0:1(eng): Audio: adpcm_ima_qt (ima4 / 0x34616D69), 44100 Hz, 2 channels, s16, 352 kb/s
    Metadata:
      creation_time   : 2001-08-08 17:13:07
      handler_name    : Apple Alias Data Handler
[ffplay_buffer @ 0130bfc0] w:352 h:288 pixfmt:yuv420p tb:1/1500 fr:0/1 sar:12/11
 sws_param:
  39.00 A-V:  0.053 fd=  52 aq=    6KB vq=  121KB sq=    0B f=0/0   f=0/0

Attachments (1)

h264_odd_dimensions.mov (386.4 KB ) - added by Carl Eugen Hoyos 11 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 by Carl Eugen Hoyos, 12 years ago

Description: modified (diff)
Keywords: cropping added
Priority: normalwish
Reproduced by developer: set
Status: newopen
Type: defectenhancement
Version: unspecifiedgit-master

comment:2 by Carl Eugen Hoyos, 11 years ago

Keywords: mov added; cropping removed

comment:3 by Carl Eugen Hoyos, 11 years ago

Keywords: cropping added

by Carl Eugen Hoyos, 11 years ago

Attachment: h264_odd_dimensions.mov added

comment:4 by Carl Eugen Hoyos, 9 years ago

Additional samples in videolan ticket 12767

comment:6 by Zach Ember, 7 years ago

Are there any updates or pointers regarding this bug? We are experiencing this bug as well with a number of videos - QuickTime sees a different (smaller) set of dimensions than ffmpeg sees and so when it's run through ffmpeg we get black and grey bars to make up the difference. I can't provide sample videos at the moment because they're proprietary but I can verify that the samples attached to this ticket show the same behavior we are seeing with our videos.

If there's any way I can help with debugging, diagnosing, or reproducing this I would love to do so as several of our users are affected by this.

I'm in the process of learning about whether the affected users share a certain authoring tool/technique/settings.

in reply to:  6 comment:7 by Zach Ember, 7 years ago

The affected videos all seem to be h.263.

Replying to zarfmouse:

comment:8 by Zach Ember, 7 years ago

Keywords: h263 added

comment:9 by Carl Eugen Hoyos, 6 years ago

The attached sample from bugzilla was fixed in 2e9dcb82 (2.8).

Last edited 6 years ago by Carl Eugen Hoyos (previous) (diff)
Note: See TracTickets for help on using tickets.