Hello BC:=Baptiste Coudurier BC> ...snip... BC> > BC> > BC> > BC> > I believe that this is a long standing issue when using the BC> > BC> > 'copy' codec and the 'mov' output format (and 'mp4' as BC> > BC> > well)... BC> > BC> > BC> > BC> > In my experience any valid input file (and media essence) when BC> > BC> > asked to be simply rewrapped in quicktime file format it leads BC> > BC> > to this error. BC> > BC> > BC> > BC> > The same command line with one simple change to 'avi' format BC> > BC> > completes without any problems... BC> > BC> > BC> > BC> > If my memory serves well I've been noticing this issue since I BC> > BC> > started using ffmpeg around r6000 BC> > BC> BC> > BC> Yes, mov muxer needs frame_size, since all timestamps in BC> > BC> mov/mp4/3gp are based on frame duration. BC> > BC> BC> > BC> Problem here is that avi and/or parsers do not set frame_size, BC> > BC> therefore muxer is complaining. BC> > BC> > any way to get around the issue in the current release? BC> > BC> > if not, would this capability be added to ffmpeg? BC> BC> It would yes, but it would need to be reported on ffmpeg-devel. BC> BC> > BC> BC> > BC> > NJ> And, how come it does not return an error code to the shell ? BC> > BC> > BC> > BC> > another bug? BC> > BC> > BC> > BC> BC> > BC> That may be a bug. BC> > BC> BC> BC> You can also report that bug on ffmpeg-devel. ffmpeg-devel isn't really just for developers rather than for normal users? wouldn't it be better that a developer monitoring this users forum picks up these two issues (one bug and one feature request) and makes the appropriate steps on the developers forum? many thanks, andrea -- Andrea Barbieri Moving Image Research http://www.movingimageresearch.com/ The Workshop, Hampton Lane, Bristol, BS6 6LE, UK Tel: +44 117 9732200 FAX: +44 117 9732210 PGP ID=0x034DFD5A KeyFingerprint=C168EA9A7189538D214F1281A7529F32034DFD5A