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? 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> BC> best regards, 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

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

Well I can't seem to fix the problem, and my boss wants results fast, so I'm now looking for a fellow ffmpeg coder with EXPEREIENCE in decoding of all formats, specifically quicktime or mov. our product is a next generation drm solution, i can't get into any more details except to say ffmpeg is the core component of our freeware player. ffmpeg is not used in the commercial aspects. but you will be paid. anyone interested contact me at antonycoder at btinternet.com or on msn Antonycoder at btinternet.com please do not reply to this thread, i'd like to discuss it in private only. ----- Original Message ----- From: "Antony Wells" <AntonyCoder at btinternet.com> To: "FFmpeg user questions and RTFMs" <ffmpeg-user at mplayerhq.hu> Sent: Thursday, March 29, 2007 12:23 PM Subject: [Ffmpeg-user] Does MOV playback work in ffmpeg?

I'm trying to decode a 125mb hi-def quicktime (The serentity trailer from the apple site)

but as soon as it goes to decode the first video stream packet, it hangs.

can anyone confirm hi-def movs can be played back?

I know i already asked a similar question but no one answered, and i need an answer. I've ran out of options.

----- Original Message ----- From: "Andrea Barbieri" <andrea.barbieri at movingimageresearch.com> To: "FFmpeg user questions and RTFMs" <ffmpeg-user at mplayerhq.hu> Sent: Thursday, March 29, 2007 11:46 AM Subject: Re: [Ffmpeg-user] ".mov" conversion error

...

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 _______________________________________________ ffmpeg-user mailing list ffmpeg-user at mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user

_______________________________________________ ffmpeg-user mailing list ffmpeg-user at mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user

On Thu, 29 Mar 2007 12:06:22 +0200, Baptiste Coudurier <baptiste.coudurier at smartjog.com> wrote:

Hi

Andrea Barbieri wrote:

...

Hello,

NJ:=Nicolas Jauffret

NJ> Hello, NJ> NJ> I would like to simply convert from an ".avi" file to a ".mov" file. NJ> The input file is "from_jpg.avi" (it has been generated from a jpeg sequence NJ> and a wav file NJ> with this command : ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec NJ> mp3 from_jpg.avi) NJ> NJ> $ ffmpeg -i from_jpg.avi NJ> FFmpeg version SVN-r8540, Copyright (c) 2000-2007 Fabrice Bellard, et al. NJ> configuration: --enable-gpl --enable-static --enable-swscaler NJ> --enable-pthreads --enable-libmp3lame --enable-libogg --enable-xvid NJ> --disable-ffserver --extra-ldflags=-static --enable-memalign-hack NJ> libavutil version: 49.4.0 NJ> libavcodec version: 51.40.2 NJ> libavformat version: 51.11.0 NJ> built on Mar 29 2007 11:04:31, gcc: 3.3.1 NJ> Input #0, avi, from 'from_jpg.avi': NJ> Duration: 00:00:08.5, start: 0.000000, bitrate: 2881 kb/s NJ> Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r) NJ> Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s NJ> Must supply at least one output file NJ> NJ> $ ffmpeg -i from_jpg.avi -vcodec copy -acodec copy from_avi.mov ; echo $? NJ> FFmpeg version SVN-r8540, Copyright (c) 2000-2007 Fabrice Bellard, et al. NJ> configuration: --enable-gpl --enable-static --enable-swscaler NJ> --enable-pthreads --enable-libmp3lame --enable-libogg --enable-xvid NJ> --disable-ffserver --extra-ldflags=-static --enable-memalign-hack NJ> libavutil version: 49.4.0 NJ> libavcodec version: 51.40.2 NJ> libavformat version: 51.11.0 NJ> built on Mar 29 2007 11:04:31, gcc: 3.3.1 NJ> Input #0, avi, from 'from_jpg.avi': NJ> Duration: 00:00:08.5, start: 0.000000, bitrate: 2881 kb/s NJ> Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r) NJ> Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s NJ> Output #0, mov, to 'from_avi.mov': NJ> Stream #0.0: Video: mpeg4, yuv420p, 640x352, q=2-31, 25.00 fps(c) NJ> Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s NJ> Stream mapping: NJ> Stream #0.0 -> #0.0 NJ> Stream #0.1 -> #0.1 NJ> [mov @ 0x84f4340]track 1: codec frame size is not set NJ> Could not write header for output file #0 (incorrect codec parameters ?) NJ> 0 NJ> NJ> Would you know what is wrong ? As nothing seems special in my ffmpeg NJ> command line...

I believe that this is a long standing issue when using the 'copy' codec and the 'mov' output format (and 'mp4' as well)...

In my experience any valid input file (and media essence) when asked to be simply rewrapped in quicktime file format it leads to this error.

The same command line with one simple change to 'avi' format completes without any problems...

If my memory serves well I've been noticing this issue since I started using ffmpeg around r6000

Yes, mov muxer needs frame_size, since all timestamps in mov/mp4/3gp are based on frame duration.

Problem here is that avi and/or parsers do not set frame_size, therefore muxer is complaining.

And if I try to recompress the audio stream, mplayer can only play its sound if "-demuxer lavf" is given in parameter. Does ffmpeg write correctly the stream headers in the mov file ? # with the same input file "from_jpg.avi" as described above $ ffmpeg -y -i from_jpg.avi -vcodec copy -acodec mp3 from_avi.mov FFmpeg version SVN-r8540, Copyright (c) 2000-2007 Fabrice Bellard, et al. configuration: --enable-gpl --enable-static --enable-swscaler --enable-pthreads --enable-libmp3lame --enable-libogg --enable-xvid --disable-ffserver --extra-ldflags=-static --enable-memalign-hack libavutil version: 49.4.0 libavcodec version: 51.40.2 libavformat version: 51.11.0 built on Mar 29 2007 11:04:31, gcc: 3.3.1 Input #0, avi, from 'from_jpg.avi': Duration: 00:00:08.5, start: 0.000000, bitrate: 439 kb/s Stream #0.0: Video: mpeg4, yuv420p, 640x352, 25.00 fps(r) Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s Output #0, mov, to 'from_avi.mov': Stream #0.0: Video: mpeg4, yuv420p, 640x352, q=2-31, 25.00 fps(c) Stream #0.1: Audio: mp3, 48000 Hz, stereo, 64 kb/s Stream mapping: Stream #0.0 -> #0.0 Stream #0.1 -> #0.1 Press [q] to stop encoding frame= 200 fps= 0 q=3824.9 Lsize= 441kB time=8.0 bitrate= 451.3kbits/s video:370kB audio:67kB global headers:0kB muxing overhead 0.739459% $ ffmpeg -i from_avi.mov FFmpeg version SVN-r8540, Copyright (c) 2000-2007 Fabrice Bellard, et al. configuration: --enable-gpl --enable-static --enable-swscaler --enable-pthreads --enable-libmp3lame --enable-libogg --enable-xvid --disable-ffserver --extra-ldflags=-static --enable-memalign-hack libavutil version: 49.4.0 libavcodec version: 51.40.2 libavformat version: 51.11.0 built on Mar 29 2007 11:04:31, gcc: 3.3.1 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'from_avi.mov': Duration: 00:00:08.6, start: 0.000000, bitrate: 419 kb/s Stream #0.0(eng): Video: mpeg4, yuv420p, 640x352, 25.00 fps(r) Stream #0.1(eng): Audio: mp3, 48000 Hz, stereo Must supply at least one output file

...

NJ> And, how come it does not return an error code to the shell ?

another bug?

That may be a bug.

How to report it to developpers ?

On Thu, 29 Mar 2007 14:28:29 +0200, Andrea Barbieri <andrea.barbieri at movingimageresearch.com> wrote:

Hello,

NJ:=Nicolas Jauffret

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

as mentioned in http://ffmpeg.mplayerhq.hu/mailinglists.html in theory it should be sufficient to post it to the ffmpeg-user list (as you obviously have done in the first place)...

as suggested by Baptiste it seems that one also needs to subscribe to the ffmpeg-devel list and report it there (it seems a bit weird to me though, because that list is dedicated to those participating in the active development of ffmpeg)

Thank you for your quick answers. That's too bad ffmpeg does not manage well the quicktime mov format conversion. From a jpeg sequence, there is no problem. But when I try to convert an avi file, there is a problem with the sound stream. Would you know any way to circumvent this problem ? ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 out.mov => Readable with mplayer (no sound without "-demuxer lavf" parameter) => readable with MacOS QtPlayer 7.1.5 ffmpeg -i foo.avi -vcodec copy -acodec mp3 out.mov => Readable with mplayer (no sound without "-demuxer lavf" parameter) => Unreadable with MacOS QtPlayer 7.1.5 Best regards, Nicolas

On Thu, 29 Mar 2007 15:06:27 +0200, Andrea Barbieri <andrea.barbieri at movingimageresearch.com> wrote:

Hello,

my suggestion below

NJ:=Nicolas Jauffret

NJ> On Thu, 29 Mar 2007 14:28:29 +0200, Andrea Barbieri NJ> <andrea.barbieri at movingimageresearch.com> wrote: NJ> NJ> >Hello, NJ> > NJ> >NJ:=Nicolas Jauffret NJ> > NJ> > NJ> ...snip... NJ> > NJ> NJ> > NJ> > > NJ> And, how come it does not return an error code to the NJ> > NJ> > > NJ> shell ? NJ> > NJ> > > NJ> > NJ> > >another bug? NJ> > NJ> > NJ> > NJ> >That may be a bug. NJ> > NJ> NJ> > NJ> How to report it to developpers ? NJ> > NJ> >as mentioned in http://ffmpeg.mplayerhq.hu/mailinglists.html NJ> >in theory it should be sufficient to post it to the ffmpeg-user list (as NJ> >you obviously have done in the first place)... NJ> > NJ> >as suggested by Baptiste it seems that one also needs to subscribe to NJ> >the ffmpeg-devel list and report it there (it seems a bit weird to me NJ> >though, because that list is dedicated to those participating in the NJ> >active development of ffmpeg) NJ> NJ> Thank you for your quick answers. NJ> That's too bad ffmpeg does not manage well the quicktime mov format NJ> conversion. NJ> From a jpeg sequence, there is no problem. NJ> But when I try to convert an avi file, there is a problem with the sound NJ> stream. NJ> Would you know any way to circumvent this problem ? NJ> NJ> ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 out.mov NJ> => Readable with mplayer (no sound without "-demuxer lavf" parameter) NJ> => readable with MacOS QtPlayer 7.1.5 NJ> NJ> ffmpeg -i foo.avi -vcodec copy -acodec mp3 out.mov NJ> => Readable with mplayer (no sound without "-demuxer lavf" parameter) NJ> => Unreadable with MacOS QtPlayer 7.1.5 NJ>

try the conversion without video essence: ffmpeg -i foo.avi -acodec mp3 out.mov

=> Readable with mplayer (no sound without "-demuxer lavf" parameter) => Readable with MacOS QtPlayer 7.1.5 So the problem seems well to come from the "copy" codec.

the simpler the problem the better it is to pinpoint a possible bug

could it be that the avi parser (unlike the wav parser) is not filling up properly all the required parameters for the mov writer?

you can use mpeg4ip or Dumpster (Apple quicktime downloadable tool) to inspect the problematic movie clip

$ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 from_jpg.mov > /dev/null 2>&1 $ mp4info from_jpg.mov mp4info version 1.5.0.1 Track Type Info 1 video MPEG-4 Simple @ L1, 8.000 secs, 0 kbps, 640x352 @ 25.000000 fps 2 audio .mp3, 8.568 secs, 64 kbps, 48000 Hz $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 foo.avi > /dev/null 2>&1 $ ffmpeg -i foo.avi -vcodec copy -acodec mp3 from_avi.mov > /dev/null 2>&1 $ mp4info from_avi.mov mp4info version 1.5.0.1 Track Type Info 1 video FMP4, 8.000 secs, 378 kbps, 0x0 @ 25.000000 fps 2 audio .mp3, 8.616 secs, 64 kbps, 48000 Hz That is strange that the 2 sound streams have not the same duration. That is also strange that the video tags are different. I installed dumpster but could not extract any information from it. Best regards, Nicolas PS: Offtopic, mp4info seems to have problems getting information from "avi" files. $ mp4info foo.avi ; echo $? mp4info version 1.5.0.1 mp4info: can't open foo.avi 0 # Of course, the rights are ok for foo.avi # and "of course", no error code is set by mp4info...

Hello Baptiste BC:=Baptiste Coudurier BC> Nicolas Jauffret wrote: BC> > On Thu, 29 Mar 2007 15:06:27 +0200, Andrea Barbieri BC> > <andrea.barbieri at movingimageresearch.com> wrote: BC> >> BC> >> try the conversion without video essence: BC> >> ffmpeg -i foo.avi -acodec mp3 out.mov BC> > BC> > => Readable with mplayer (no sound without "-demuxer lavf" parameter) BC> > => Readable with MacOS QtPlayer 7.1.5 BC> > BC> > So the problem seems well to come from the "copy" codec. BC> BC> No, problem might come from mplayer demuxer, if Quicktime plays it, BC> file has great chances to be correct. the point is that in this case the output is playable by both applications, when adding the video 'copy' codec this is not true anymore... BC> BC> >> the simpler the problem the better it is to pinpoint a possible bug BC> >> BC> >> could it be that the avi parser (unlike the wav parser) is not BC> >> filling up properly all the required parameters for the mov writer? BC> >> BC> >> you can use mpeg4ip or Dumpster (Apple quicktime downloadable tool) BC> >> to inspect the problematic movie clip BC> > BC> > $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 from_jpg.mov BC> >> /dev/null 2>&1 BC> > $ mp4info from_jpg.mov BC> > mp4info version 1.5.0.1 BC> > Track Type Info BC> > 1 video MPEG-4 Simple @ L1, 8.000 secs, 0 kbps, 640x352 @ BC> > 25.000000 fps BC> > 2 audio .mp3, 8.568 secs, 64 kbps, 48000 Hz BC> > BC> > $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 foo.avi > BC> > /dev/null 2>&1 BC> > $ ffmpeg -i foo.avi -vcodec copy -acodec mp3 from_avi.mov > /dev/null 2>&1 BC> > $ mp4info from_avi.mov BC> > mp4info version 1.5.0.1 BC> > Track Type Info BC> > 1 video FMP4, 8.000 secs, 378 kbps, 0x0 @ 25.000000 fps BC> > 2 audio .mp3, 8.616 secs, 64 kbps, 48000 Hz BC> > BC> > That is strange that the 2 sound streams have not the same duration. BC> BC> Well possible, I need to check. BC> BC> > That is also strange that the video tags are different. BC> BC> No, default ffmpeg mpeg4 codec tag in avi in FMP4, muxer by default BC> uses tag if it is set, patch welcome though. I think that the mov writer module is not behaving properly when creating the video track since the profile and level information is missing as well... the initial movie file (generated by the jpeg -> mov conversion) also appears to be incorrect/incomplete in terms of video track information (sample description atoms) the 0 kbps deducted info is the giveaway. best regards, 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

Hello BC:=Baptiste Coudurier BC> Andrea Barbieri wrote: BC> > Hello Baptiste BC> > BC> > BC:=Baptiste Coudurier BC> > BC> > BC> Nicolas Jauffret wrote: BC> > BC> > On Thu, 29 Mar 2007 15:06:27 +0200, Andrea Barbieri BC> > BC> > <andrea.barbieri at movingimageresearch.com> wrote: BC> > BC> >> BC> > BC> >> try the conversion without video essence: BC> > BC> >> ffmpeg -i foo.avi -acodec mp3 out.mov BC> > BC> > BC> > BC> > => Readable with mplayer (no sound without "-demuxer lavf" parameter) BC> > BC> > => Readable with MacOS QtPlayer 7.1.5 BC> > BC> > BC> > BC> > So the problem seems well to come from the "copy" codec. BC> > BC> BC> > BC> No, problem might come from mplayer demuxer, if Quicktime plays it, BC> > BC> file has great chances to be correct. BC> > BC> > the point is that in this case the output is playable by both BC> > applications, when adding the video 'copy' codec this is not true BC> > anymore... BC> BC> No, the point is mplayer not correctly playing, Quicktime/ffmpeg/xine BC> play it. I'm afraid I made the mistake to cut *now* relevant parts of previous posts which do explain what I am trying to tell you, please have a look at those. BC> BC> > BC> BC> > BC> >> the simpler the problem the better it is to pinpoint a possible bug BC> > BC> >> BC> > BC> >> could it be that the avi parser (unlike the wav parser) is not BC> > BC> >> filling up properly all the required parameters for the mov writer? BC> > BC> >> BC> > BC> >> you can use mpeg4ip or Dumpster (Apple quicktime downloadable tool) BC> > BC> >> to inspect the problematic movie clip BC> > BC> > BC> > BC> > $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 from_jpg.mov BC> > BC> >> /dev/null 2>&1 BC> > BC> > $ mp4info from_jpg.mov BC> > BC> > mp4info version 1.5.0.1 BC> > BC> > Track Type Info BC> > BC> > 1 video MPEG-4 Simple @ L1, 8.000 secs, 0 kbps, 640x352 @ BC> > BC> > 25.000000 fps BC> > BC> > 2 audio .mp3, 8.568 secs, 64 kbps, 48000 Hz BC> > BC> > BC> > BC> > $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 foo.avi > BC> > BC> > /dev/null 2>&1 BC> > BC> > $ ffmpeg -i foo.avi -vcodec copy -acodec mp3 from_avi.mov > /dev/null 2>&1 BC> > BC> > $ mp4info from_avi.mov BC> > BC> > mp4info version 1.5.0.1 BC> > BC> > Track Type Info BC> > BC> > 1 video FMP4, 8.000 secs, 378 kbps, 0x0 @ 25.000000 fps BC> > BC> > 2 audio .mp3, 8.616 secs, 64 kbps, 48000 Hz BC> > BC> > BC> > BC> > That is strange that the 2 sound streams have not the same duration. BC> > BC> BC> > BC> Well possible, I need to check. BC> > BC> BC> > BC> > That is also strange that the video tags are different. BC> > BC> BC> > BC> No, default ffmpeg mpeg4 codec tag in avi in FMP4, muxer by default BC> > BC> uses tag if it is set, patch welcome though. BC> > BC> > I think that the mov writer module is not behaving properly when BC> > creating the video track since the profile and level information is BC> > missing as well... BC> BC> I believe mp4info just does not recognize FMP4 tag and therefore not BC> even try to gather info. I don't think so... (if you check the source code) BC> BC> > the initial movie file (generated by the jpeg -> mov conversion) BC> > also appears to be incorrect/incomplete in terms of video track BC> > information (sample description atoms) the 0 kbps deducted info is BC> > the giveaway. BC> BC> bitrate is just not set in "esds" atom, if you have specs (14496-1 and BC> 14496-14, maybe 14496-2 for mpeg4) where it says this is mandatory, BC> I'll fix it. you are mentioning MPEG4 standards which define the MP4 format. Unfortunately we are talking about the QuickTime file format (the grandfather of the MP4 and MJPEG200 ones) which behaves differently http://developer.apple.com/reference/QuickTime/ just because these formats are deceptively extremely similar it does not mean that they are identical... may be it was not the best idea to bundle everything together in the mov.c file writer module when dealing with QT, MP4 and 3GP industry and ISO standards. best regards, 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

Hello BC:=Baptiste Coudurier BC> Andrea Barbieri wrote: BC> > Hello BC> > BC> > BC:=Baptiste Coudurier BC> > BC> > BC> Andrea Barbieri wrote: BC> > BC> > Hello Baptiste BC> > BC> > BC> > BC> > BC:=Baptiste Coudurier BC> > BC> > BC> > BC> > BC> Nicolas Jauffret wrote: BC> > BC> > BC> > On Thu, 29 Mar 2007 15:06:27 +0200, Andrea Barbieri BC> > BC> > BC> > <andrea.barbieri at movingimageresearch.com> wrote: BC> > BC> > BC> >> BC> > BC> > BC> >> try the conversion without video essence: BC> > BC> > BC> >> ffmpeg -i foo.avi -acodec mp3 out.mov BC> > BC> > BC> > BC> > BC> > BC> > => Readable with mplayer (no sound without "-demuxer lavf" parameter) BC> > BC> > BC> > => Readable with MacOS QtPlayer 7.1.5 BC> > BC> > BC> > BC> > BC> > BC> > So the problem seems well to come from the "copy" codec. BC> > BC> > BC> BC> > BC> > BC> No, problem might come from mplayer demuxer, if Quicktime plays it, BC> > BC> > BC> file has great chances to be correct. BC> > BC> > BC> > BC> > the point is that in this case the output is playable by both BC> > BC> > applications, when adding the video 'copy' codec this is not true BC> > BC> > anymore... BC> > BC> BC> > BC> No, the point is mplayer not correctly playing, Quicktime/ffmpeg/xine BC> > BC> play it. BC> > BC> > I'm afraid I made the mistake to cut *now* relevant parts of previous BC> > posts which do explain what I am trying to tell you, please have a look at BC> > those. BC> BC> No, read whole explanation, you focus on a weird demuxer behaviour BC> instead of the real issue. Check file, check info written in atoms, BC> compare against specs, finally quote me specs if that is wrong, I'll BC> fix it for sure. I think we are degenerating... BC> BC> > BC> BC> > BC> > BC> BC> > BC> > BC> >> the simpler the problem the better it is to pinpoint a possible bug BC> > BC> > BC> >> BC> > BC> > BC> >> could it be that the avi parser (unlike the wav parser) is not BC> > BC> > BC> >> filling up properly all the required parameters for the mov writer? BC> > BC> > BC> >> BC> > BC> > BC> >> you can use mpeg4ip or Dumpster (Apple quicktime downloadable tool) BC> > BC> > BC> >> to inspect the problematic movie clip BC> > BC> > BC> > BC> > BC> > BC> > $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 from_jpg.mov BC> > BC> > BC> >> /dev/null 2>&1 BC> > BC> > BC> > $ mp4info from_jpg.mov BC> > BC> > BC> > mp4info version 1.5.0.1 BC> > BC> > BC> > Track Type Info BC> > BC> > BC> > 1 video MPEG-4 Simple @ L1, 8.000 secs, 0 kbps, 640x352 @ BC> > BC> > BC> > 25.000000 fps BC> > BC> > BC> > 2 audio .mp3, 8.568 secs, 64 kbps, 48000 Hz BC> > BC> > BC> > BC> > BC> > BC> > $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 foo.avi > BC> > BC> > BC> > /dev/null 2>&1 BC> > BC> > BC> > $ ffmpeg -i foo.avi -vcodec copy -acodec mp3 from_avi.mov > /dev/null 2>&1 BC> > BC> > BC> > $ mp4info from_avi.mov BC> > BC> > BC> > mp4info version 1.5.0.1 BC> > BC> > BC> > Track Type Info BC> > BC> > BC> > 1 video FMP4, 8.000 secs, 378 kbps, 0x0 @ 25.000000 fps BC> > BC> > BC> > 2 audio .mp3, 8.616 secs, 64 kbps, 48000 Hz BC> > BC> > BC> > BC> > BC> > BC> > That is strange that the 2 sound streams have not the same duration. BC> > BC> > BC> BC> > BC> > BC> Well possible, I need to check. BC> > BC> > BC> BC> > BC> > BC> > That is also strange that the video tags are different. BC> > BC> > BC> BC> > BC> > BC> No, default ffmpeg mpeg4 codec tag in avi in FMP4, muxer by default BC> > BC> > BC> uses tag if it is set, patch welcome though. BC> > BC> > BC> > BC> > I think that the mov writer module is not behaving properly when BC> > BC> > creating the video track since the profile and level information is BC> > BC> > missing as well... BC> > BC> BC> > BC> I believe mp4info just does not recognize FMP4 tag and therefore not BC> > BC> even try to gather info. BC> > BC> > I don't think so... (if you check the source code) BC> BC> Well that was just some guess, check mp4info, again check info in atoms BC> compare against specs and I'll fix it. I am not the one with the problem... but I can easily generate a mov file with the same issues and then point at the deficiencies BC> BC> > BC> BC> > BC> > the initial movie file (generated by the jpeg -> mov conversion) BC> > BC> > also appears to be incorrect/incomplete in terms of video track BC> > BC> > information (sample description atoms) the 0 kbps deducted info is BC> > BC> > the giveaway. BC> > BC> BC> > BC> bitrate is just not set in "esds" atom, if you have specs (14496-1 and BC> > BC> 14496-14, maybe 14496-2 for mpeg4) where it says this is mandatory, BC> > BC> I'll fix it. BC> > BC> > you are mentioning MPEG4 standards which define the MP4 format. BC> BC> AFAIK "esds" atom is defined in MPEG4 (14496) standard. BC> BC> > Unfortunately we are talking about the QuickTime file format (the BC> > grandfather of the MP4 and MJPEG200 ones) which behaves differently BC> BC> MP4/MJ2/3GP are derivations of ISO Media file format (14496-12) BC> I am afraid but a bit of hystory lesson is required the QuickTime file format came first, in the late 90's the ISO MPEG-4 group wanted to adopt a file format for MPEG 4... luckily the final choice was to adopt a derivative of Apple QT file format and not Microsoft ASF file format. if you still don't believe me check: http://en.wikipedia.org/wiki/QuickTime BC> > http://developer.apple.com/reference/QuickTime/ BC> BC> Point me where to find "esds" atom description please. http://developer.apple.com/reference/QuickTime/ then follow File Format Specification best regards, 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

Hello BC:=Baptiste Coudurier BC> Andrea Barbieri wrote: BC> > BC> > BC> > BC> BC> > BC> > BC> > BC> > That is also strange that the video tags are different. BC> > BC> > BC> > BC> BC> > BC> > BC> > BC> No, default ffmpeg mpeg4 codec tag in avi in FMP4, muxer by default BC> > BC> > BC> > BC> uses tag if it is set, patch welcome though. BC> > BC> > BC> > BC> > BC> > BC> > I think that the mov writer module is not behaving properly when BC> > BC> > BC> > creating the video track since the profile and level information is BC> > BC> > BC> > missing as well... BC> > BC> > BC> BC> > BC> > BC> I believe mp4info just does not recognize FMP4 tag and therefore not BC> > BC> > BC> even try to gather info. BC> > BC> > BC> > BC> > I don't think so... (if you check the source code) BC> > BC> BC> > BC> Well that was just some guess, check mp4info, again check info in atoms BC> > BC> compare against specs and I'll fix it. BC> > BC> > I am not the one with the problem... but I can easily generate a mov file BC> > with the same issues and then point at the deficiencies BC> BC> Please do, and quote specs clearly specifying where the deficiencies are. i.e. mp4info does not extract the bitrate of the video track? (or quicktime player movie info or movie porperties panels) BC> BC> > BC> BC> > BC> > BC> BC> > BC> > BC> > the initial movie file (generated by the jpeg -> mov conversion) BC> > BC> > BC> > also appears to be incorrect/incomplete in terms of video track BC> > BC> > BC> > information (sample description atoms) the 0 kbps deducted info is BC> > BC> > BC> > the giveaway. BC> > BC> > BC> BC> > BC> > BC> bitrate is just not set in "esds" atom, if you have specs (14496-1 and BC> > BC> > BC> 14496-14, maybe 14496-2 for mpeg4) where it says this is mandatory, BC> > BC> > BC> I'll fix it. BC> > BC> > BC> > BC> > you are mentioning MPEG4 standards which define the MP4 format. BC> > BC> BC> > BC> AFAIK "esds" atom is defined in MPEG4 (14496) standard. BC> > BC> BC> > BC> > Unfortunately we are talking about the QuickTime file format (the BC> > BC> > grandfather of the MP4 and MJPEG200 ones) which behaves differently BC> > BC> BC> > BC> MP4/MJ2/3GP are derivations of ISO Media file format (14496-12) BC> > BC> BC> > BC> > I am afraid but a bit of hystory lesson is required BC> > BC> > the QuickTime file format came first, in the late 90's the ISO MPEG-4 BC> > group wanted to adopt a file format for MPEG 4... luckily the final choice BC> > was to adopt a derivative of Apple QT file format and not Microsoft ASF BC> > file format. BC> > BC> > if you still don't believe me check: BC> > http://en.wikipedia.org/wiki/QuickTime BC> BC> yes, that made ISO Media (14496-12), then after generic container BC> specifications came MP4 (14496-14) and 3GP I think I'm failing to make sure you understand that QuickTime file format is *not* the MP4 nor 3GP nor MJPEG2000 although deceptively close. BC> BC> Now point me where "esds" and wrapping of "mp4v" and "mp4a" are BC> defined in the quicktime file format specifications. AFAIK they BC> aren't, while they are in ISO 14496-* somewhere. I don't have those BC> documents so please highlight defiencies by quoting specs compared to BC> what's written by the muxer. that's another matter... here you are talking about Apple's own documentation of specific codec related information. sometimes there are no specs (Apple own ones)... just establishing if movie files play correctly in Apple QuickTime enabled applications is the only way to check for 'compliancy'. and in these cases looking at how 'valid' movie clips are structured could be the only way forward (call it detective work). and because ffmpeg does not rely on any Apple QT SDK discrepancies can and do arise. see my previous point... if an Apple QuickTime enable application fails to correctly play (or show the correct properties)... it is an issue with the .mov file writing application (unfortunately and the available documentation might be very thin). in the case of the issue raised by this very thread I think we are experiencing a problem when using the mov file writer. BC> BC> > BC> > http://developer.apple.com/reference/QuickTime/ BC> > BC> BC> > BC> Point me where to find "esds" atom description please. BC> > BC> > http://developer.apple.com/reference/QuickTime/ BC> > BC> > then follow File Format Specification BC> BC> Nothing about "mp4a" nor "mp4v" here, and document is quite old BC> (2001). if you look under the complete QuickTime Reference List you'll find the 2006/05/23 QuickTime Atoms and Resources Reference it's not complete but it is a start. also because Quicktime File Format is not an ISO standard you'll see that 'sometimes' Apple is very reluctant to provide explanations for some atoms. see for example the 'special' extension atom required (in the video track sample description) to get a .mov (or .mp4) file play on a 5th generation video iPod for 640x480 image size (but not needed to play in QuickTime Player or iTunes). best regards 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

BC:=Baptiste Coudurier [snip] BC> > BC> > BC> > BC> > I am afraid but a bit of hystory lesson is required BC> > BC> > BC> > BC> > the QuickTime file format came first, in the late 90's the ISO MPEG-4 BC> > BC> > group wanted to adopt a file format for MPEG 4... luckily the final choice BC> > BC> > was to adopt a derivative of Apple QT file format and not Microsoft ASF BC> > BC> > file format. BC> > BC> > BC> > BC> > if you still don't believe me check: BC> > BC> > http://en.wikipedia.org/wiki/QuickTime BC> > BC> BC> > BC> yes, that made ISO Media (14496-12), then after generic container BC> > BC> specifications came MP4 (14496-14) and 3GP BC> > BC> > I think I'm failing to make sure you understand that QuickTime file BC> > format is *not* the MP4 nor 3GP nor MJPEG2000 although deceptively BC> > close. BC> BC> I think you fail to understand that Quicktime file format use many BC> specifications from MP4/3GP (see amr/mp4a/mp4v/h264 atoms) and what about if it was the other way around for the *overwhelming majority* of the atoms? best regards 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

Nicolas Jauffret wrote:

On Thu, 29 Mar 2007 18:34:50 +0200, Baptiste Coudurier <baptiste.coudurier at smartjog.com> wrote:

...

Nicolas Jauffret wrote:

...

On Thu, 29 Mar 2007 15:06:27 +0200, Andrea Barbieri <andrea.barbieri at movingimageresearch.com> wrote:

...

try the conversion without video essence: ffmpeg -i foo.avi -acodec mp3 out.mov

=> Readable with mplayer (no sound without "-demuxer lavf" parameter) => Readable with MacOS QtPlayer 7.1.5

So the problem seems well to come from the "copy" codec.

No, problem might come from mplayer demuxer, if Quicktime plays it, file has great chances to be correct.

The fact is, Quicktime does not play its sound, if "-vcodec copy" is used to generate the mov file.

With MacOs Quicktime 7.1.5 : - from a jpg sequence => all is Ok. - from an avi file => the "-vcodec copy" causes a sound reading problem.

I thought -vcodec copy failed because of "frame size not set". Are you sure ? If not, I'd like to check that avi file. -- Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA SMARTJOG S.A. http://www.smartjog.com Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA Phone: +33 1 49966312

Hello Nicolas, NJ:=Nicolas Jauffret NJ> On Thu, 29 Mar 2007 19:21:59 +0200, Baptiste Coudurier NJ> <baptiste.coudurier at smartjog.com> wrote: NJ> NJ> >Nicolas Jauffret wrote: NJ> > >On Thu, 29 Mar 2007 18:34:50 +0200, Baptiste Coudurier NJ> > ><baptiste.coudurier at smartjog.com> wrote: NJ> > > NJ> > > >Nicolas Jauffret wrote: NJ> > > > >On Thu, 29 Mar 2007 15:06:27 +0200, Andrea Barbieri NJ> > > > ><andrea.barbieri at movingimageresearch.com> wrote: NJ> > > > > > NJ> > > > > >try the conversion without video essence: NJ> > > > > >ffmpeg -i foo.avi -acodec mp3 out.mov NJ> > > > > NJ> > > > > => Readable with mplayer (no sound without "-demuxer lavf" NJ> > > > > => parameter) NJ> > > > > => Readable with MacOS QtPlayer 7.1.5 NJ> > > > > NJ> > > > >So the problem seems well to come from the "copy" codec. NJ> > > > NJ> > > >No, problem might come from mplayer demuxer, if Quicktime plays it, NJ> > > >file has great chances to be correct. NJ> > > NJ> > >The fact is, Quicktime does not play its sound, if "-vcodec copy" is used NJ> > >to generate the mov file. NJ> > > NJ> > >With MacOs Quicktime 7.1.5 : NJ> > >- from a jpg sequence => all is Ok. NJ> > >- from an avi file => the "-vcodec copy" causes a sound reading problem. NJ> > NJ> >I thought -vcodec copy failed because of "frame size not set". Are you NJ> >sure ? NJ> >If not, I'd like to check that avi file. NJ> NJ> I have brought different issues in this mailing list : NJ> NJ> The first one : NJ> ffmpeg -i from_jpg.avi -vcodec copy -acodec copy from_avi.mov NJ> => [mov @ 0x84f4340]track 1: codec frame size is not set NJ> Could not write header for output file #0 (incorrect codec parameters ?) NJ> => Error code=0 NJ> NJ> The second one: NJ> compression works when setting -acodec mp3, instead of copy codec, NJ> but then, can not be played with MacOS Quicktime Player 7.1.5 NJ> NJ> To make it clearer (from .avi to .mov) : NJ> -vcodec copy -acodec copy => "Could not write header" error + no error code NJ> set NJ> -vcodec copy -acodec mp3 => compression works, but will not open in QtPlayer NJ> 7.1.5 NJ> -sameq -acodec copy => "Could not write header" error + no error code set NJ> -sameq -acodec mp3 => works fine NJ> as mentioned in many postings... raise just one issue per email/subject otherwise bad things can happen :) cheers, 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

Hello, NJ:=Nicolas Jauffret NJ> ...snip... NJ> > NJ> >try the conversion without video essence: NJ> >ffmpeg -i foo.avi -acodec mp3 out.mov NJ> NJ> => Readable with mplayer (no sound without "-demuxer lavf" parameter) NJ> => Readable with MacOS QtPlayer 7.1.5 NJ> NJ> So the problem seems well to come from the "copy" codec. very good finding... it should help the developers... NJ> NJ> NJ> >the simpler the problem the better it is to pinpoint a possible bug NJ> > NJ> >could it be that the avi parser (unlike the wav parser) is not NJ> >filling up properly all the required parameters for the mov writer? NJ> > NJ> >you can use mpeg4ip or Dumpster (Apple quicktime downloadable tool) to NJ> >inspect the problematic movie clip NJ> NJ> $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 from_jpg.mov > NJ> /dev/null 2>&1 NJ> $ mp4info from_jpg.mov NJ> mp4info version 1.5.0.1 NJ> Track Type Info NJ> 1 video MPEG-4 Simple @ L1, 8.000 secs, 0 kbps, 640x352 @ 25.000000 NJ> fps NJ> 2 audio .mp3, 8.568 secs, 64 kbps, 48000 Hz NJ> NJ> $ ffmpeg -i foo.%d.jpg -i bar.wav -vcodec mpeg4 -acodec mp3 foo.avi > NJ> /dev/null 2>&1 NJ> $ ffmpeg -i foo.avi -vcodec copy -acodec mp3 from_avi.mov > /dev/null 2>&1 NJ> $ mp4info from_avi.mov NJ> mp4info version 1.5.0.1 NJ> Track Type Info NJ> 1 video FMP4, 8.000 secs, 378 kbps, 0x0 @ 25.000000 fps NJ> 2 audio .mp3, 8.616 secs, 64 kbps, 48000 Hz NJ> NJ> That is strange that the 2 sound streams have not the same duration. NJ> That is also strange that the video tags are different. by the look of it the 'copy' codec facility (both audio and video) needs serious looking/enhancing when the target output format is mov/mp4/3gp NJ> NJ> I installed dumpster but could not extract any information from it just drag and drop the movie clip on the Dumpster icon, you should then be able to navigate the QT atoms structure NJ> NJ> Best regards, NJ> NJ> NJ> Nicolas NJ> PS: Offtopic, mp4info seems to have problems getting information from "avi" NJ> files. NJ> $ mp4info foo.avi ; echo $? NJ> mp4info version 1.5.0.1 NJ> mp4info: can't open foo.avi NJ> 0 NJ> # Of course, the rights are ok for foo.avi NJ> # and "of course", no error code is set by mp4info... hemmm... mp4info ... a tool for gathering info on mp4/mov files ... AVI is a totally different file format, no surprise that it oes not understand it best regards, 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

Hello, NJ:=Nicolas Jauffret NJ> On Thu, 29 Mar 2007 18:40:01 +0200, Andrea Barbieri NJ> <andrea.barbieri at movingimageresearch.com> wrote: NJ> NJ> >Hello, NJ> > NJ> >NJ:=Nicolas Jauffret NJ> > NJ> NJ> [snip] NJ> NJ> > NJ> $ mp4info foo.avi ; echo $? NJ> > NJ> mp4info version 1.5.0.1 NJ> > NJ> mp4info: can't open foo.avi NJ> > NJ> 0 NJ> > NJ> # Of course, the rights are ok for foo.avi NJ> > NJ> # and "of course", no error code is set by mp4info... NJ> > NJ> >hemmm... mp4info ... a tool for gathering info on mp4/mov files NJ> >...AVI is a totally different file format, no surprise that it oes NJ> >not understand it NJ> NJ> Oops, ffmpeg makes us used to tools that gets anything in NJ> input/output. I should have been more careful before posting this :) NJ> But it does not change the fact that it should not return 0 on error. NJ> As ffmpeg does when it tells "Could not write header for output file". yes, I understand, but the most appropriate place to report this particular bug is at http://sourceforge.net/projects/mpeg4ip best regards, 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