Hi, >> Someone else recently uploaded an iPhone recording that qtfaststart >> completely fubar'ed > > Could you point me to that file, I must have missed it.
Found it, but I didn't mean to say that, it's some part of iOS or some app that is messing it up, and qtfaststart doesn't recognize the fubar'ed "mov" > Begin forwarded message: > > From: Peter Alderson <[email protected]> > Subject: Re: [FFmpeg-user] Converting Quicktime (.mov ) from iPhone to mp4 > Date: March 25, 2020 at 06:11:15.000GMT-4 > To: FFmpeg user questions <[email protected]> > Reply-To: FFmpeg user questions <[email protected]> > --------------------~~~~~~~~~~~~~~~~---------------- > The Command / Output is... > > $ ffmpeg -i <tezt-file>.mov -vcodec h264 -acodec mp2 test-output-21.mp4 > ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers > built with Apple clang version 11.0.0 (clang-1100.0.33.17) > configuration: --prefix=/usr/local/Cellar/ffmpeg/4.2.2_2 --enable-shared > --enable-pthreads --enable-version3 --enable-avresample --cc=clang > --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl > --enable-libaom --enable-libbluray --enable-libmp3lame --enable-libopus > --enable-librubberband --enable-libsnappy --enable-libtesseract > --enable-libtheora --enable-libvidstab --enable-libvorbis --enable-libvpx > --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid > --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r > --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb > --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-libsoxr > --enable-videotoolbox --disable-libjack --disable-indev=jack > libavutil 56. 31.100 / 56. 31.100 > libavcodec 58. 54.100 / 58. 54.100 > libavformat 58. 29.100 / 58. 29.100 > libavdevice 58. 8.100 / 58. 8.100 > libavfilter 7. 57.100 / 7. 57.100 > libavresample 4. 0. 0 / 4. 0. 0 > libswscale 5. 5.100 / 5. 5.100 > libswresample 3. 5.100 / 3. 5.100 > libpostproc 55. 5.100 / 55. 5.100 > [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fe4de00c000] moov atom not found > <text-file>.mov: Invalid data found when processing input > $ > > The test file can be found at > https://s3-eu-west-1.amazonaws.com/app.netframe.io/another-test.mov > <https://s3-eu-west-1.amazonaws.com/app.netframe.io/another-test.mov> > <https://s3-eu-west-1.amazonaws.com/app.netframe.io/another-test.mov > <https://s3-eu-west-1.amazonaws.com/app.netframe.io/another-test.mov>> At some point in the file everything is shifted 16 bits (long is 32 isn't it?) and it actually looks like the moov atom is cut short based on the length field, not appended by other top-level atoms as I originally thought. Regards, Ted Park _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
