[Ffmpeg-devel] Fwd: Re: [Ffmpeg-user] ".mov" conversion error

[Nicolas Jauffret]

Hello,
As I was asked by Baptiste Coudurier, I foward here two issues from the  
user mailing list.
Thank you for your time.
Regards,

Nicolas

------- Forwarded message -------
From: "Baptiste Coudurier" <baptiste.coudurier at smartjog.com>
To: "FFmpeg user questions and RTFMs" <ffmpeg-user at mplayerhq.hu>
Cc:
Subject: Re: [Ffmpeg-user] ".mov" conversion error
Date: Thu, 29 Mar 2007 12:25:56 +0200

Andrea Barbieri wrote:
> Hello,
>
> BC:=Baptiste Coudurier
>
> BC> Hi
> BC>
> BC> Andrea Barbieri wrote:
> BC> > Hello,
> BC> >
> BC> > NJ:=Nicolas Jauffret
> BC> >
> BC> > NJ> Hello,
> BC> > NJ>
> BC> > NJ> I would like to simply convert from an ".avi" file to a ".mov"  
> file.
> BC> > NJ> The input file is "from_jpg.avi" (it has been generated from a  
> jpeg sequence
> BC> > NJ> and a wav file
> BC> > NJ> with this command : ffmpeg -i foo.%d.jpg -i bar.wav -vcodec  
> mpeg4 -acodec
> BC> > NJ> mp3 from_jpg.avi)
> BC> > NJ>
> BC> > NJ> $ ffmpeg -i from_jpg.avi
> BC> > NJ> FFmpeg version SVN-r8540, Copyright (c) 2000-2007 Fabrice  
> Bellard, et al.
> BC> > NJ>  configuration: --enable-gpl --enable-static --enable-swscaler
> BC> > NJ>  --enable-pthreads --enable-libmp3lame --enable-libogg  
> --enable-xvid
> BC> > NJ>  --disable-ffserver --extra-ldflags=-static  
> --enable-memalign-hack
> BC> > NJ>  libavutil version: 49.4.0
> BC> > NJ>  libavcodec version: 51.40.2
> BC> > NJ>  libavformat version: 51.11.0
> BC> > NJ>  built on Mar 29 2007 11:04:31, gcc: 3.3.1
> BC> > NJ> Input #0, avi, from 'from_jpg.avi':
> BC> > NJ>  Duration: 00:00:08.5, start: 0.000000, bitrate: 2881 kb/s
> BC> > NJ>  Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r)
> BC> > NJ>  Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s
> BC> > NJ> Must supply at least one output file
> BC> > NJ>
> BC> > NJ> $ ffmpeg -i from_jpg.avi -vcodec copy -acodec copy  
> from_avi.mov ; echo $?
> BC> > NJ> FFmpeg version SVN-r8540, Copyright (c) 2000-2007 Fabrice  
> Bellard, et al.
> BC> > NJ>  configuration: --enable-gpl --enable-static --enable-swscaler
> BC> > NJ>  --enable-pthreads --enable-libmp3lame --enable-libogg  
> --enable-xvid
> BC> > NJ>  --disable-ffserver --extra-ldflags=-static  
> --enable-memalign-hack
> BC> > NJ>  libavutil version: 49.4.0
> BC> > NJ>  libavcodec version: 51.40.2
> BC> > NJ>  libavformat version: 51.11.0
> BC> > NJ>  built on Mar 29 2007 11:04:31, gcc: 3.3.1
> BC> > NJ> Input #0, avi, from 'from_jpg.avi':
> BC> > NJ>  Duration: 00:00:08.5, start: 0.000000, bitrate: 2881 kb/s
> BC> > NJ>  Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r)
> BC> > NJ>  Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s
> BC> > NJ> Output #0, mov, to 'from_avi.mov':
> BC> > NJ>  Stream #0.0: Video: mpeg4, yuv420p, 640x352, q=2-31, 25.00  
> fps(c)
> BC> > NJ>  Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s
> BC> > NJ> Stream mapping:
> BC> > NJ>  Stream #0.0 -> #0.0
> BC> > NJ>  Stream #0.1 -> #0.1
> BC> > NJ> [mov @ 0x84f4340]track 1: codec frame size is not set
> BC> > NJ> Could not write header for output file #0 (incorrect codec  
> parameters ?)
> BC> > NJ> 0
> BC> > NJ>
> BC> > NJ> Would you know what is wrong ? As nothing seems special in my  
> ffmpeg
> BC> > NJ> command line...
> BC> >
> BC> > I believe that this is a long standing issue when using the 'copy'  
> codec
> BC> > and the 'mov' output format (and 'mp4' as well)...
> BC> >
> BC> > In my experience any valid input file (and media essence) when  
> asked to be
> BC> > simply rewrapped in quicktime file format it leads to this error.
> BC> >
> BC> > The same command line with one simple change to 'avi' format  
> completes
> BC> > without any problems...
> BC> >
> BC> > If my memory serves well I've been noticing this issue since I  
> started
> BC> > using ffmpeg around r6000
> BC>
> BC> Yes, mov muxer needs frame_size, since all timestamps in mov/mp4/3gp
> BC> are based on frame duration.
> BC>
> BC> Problem here is that avi and/or parsers do not set frame_size,
> BC> therefore muxer is complaining.
>
> any way to get around the issue in the current release?
>
> if not, would this capability be added to ffmpeg?

It would yes, but it would need to be reported on ffmpeg-devel.

> BC>
> BC> > NJ> And, how come it does not return an error code to the shell ?
> BC> >
> BC> > another bug?
> BC> >
> BC>
> BC> That may be a bug.
> BC>

You can also report that bug on ffmpeg-devel.