Hello!
On 08/31/2016 04:04 PM, Carl Eugen Hoyos wrote:
Iirc, this has the (intended or unintended) side-effect of making
mov output of ffmpeg (the app) suddenly defaulting to an
additional track.
Is this correct? Is it intended?
Hmm, it seems mov files still have one track according to these commands:
% ffmpeg -i foo.png foo.mov
% MP4Box -diso foo.mov
% grep ' TrackID=' foo_info.xml
<TrackHeaderBox CreationTime="0" ModificationTime="0" TrackID="1"
Duration="40" Width="2.00" Height="2.00">
Certtainly that kind of variation would not be intended. The fate tests
(lavf-moov) have bitwise comparisons for mov results, but of course they
don't use the defaults.
So I imagine you are referring to the enable_tracks function. The change
is probably not strictly required for this functionality to work in
general and it was added for uniformity in dealing with this the same as
with other track types.
Thanks for input!
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
