Andrea Barbieri wrote:
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)
mp4info doing bad or good things is not a argument. Only specs matters. If Quicktime can't play it that's a problem yes, but here Quicktime plays it. You need to change video tag (-vtag mp4v) if you want to stream copy video stream from avi.
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.
I think you fail to understand that Quicktime file format use many specifications from MP4/3GP (see amr/mp4a/mp4v/h264 atoms)
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'.
See previous answer.
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.
See first answer.
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.
There is no "esds" atom description in that document. Quicktime just uses MPEG4 specifications for esds, see second answer. -- Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA SMARTJOG S.A. http://www.smartjog.com Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA Phone: +33 1 49966312