ffmpeg goes berserk when trying to convert this video to mjpeg

Bug #940721 reported by Teo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libav (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have a 3gp video of 20 seconds, 10 fps, 480x640 resolution, h264 codec, for a file size of about 4 MB; I tried the following command:
ffmpeg -i VIDEO0024.3gp -vcodec mjpeg -s 300x400 -qmin 0.8 -qmax 0.8 VIDEO0024.mov
After several minutes, ffmpeg had processed more than 145357 frames, reported a time of 1.62 seconds, had written more than one GIGABYTE of output and was still working. I obviously killed it.
The exactly same command has worked just fine with other video files encoded with other codecs.

I think the problem is that for some reason it by default uses an output framerate of about 90000 fps. Adding -r 10 for the output fixes the issue. But it is still an issue: according to documentation the default framerate is 30fps, anyway 90000 is certainly not a reasonable default.

I erroneously reported this in the FFmpeg bugtracker and they say it's probably fixed in FFmpeg.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ffmpeg 4:0.7.3-0ubuntu0.11.10.1
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Feb 25 01:49:11 2012
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libav
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (79 days ago)

Revision history for this message
Teo (teo1978) wrote :
description: updated
Revision history for this message
Sebastian Ramacher (s-ramacher) wrote :

Is this issue still present in libav-tools 11-2.1? If yes, please report it at https://libav.org/bugreports.html.

Changed in libav (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libav (Ubuntu) because there has been no activity for 60 days.]

Changed in libav (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.