[Ffmpeg-devel] Re: [PATCH] wrong duration is set with some MOV files

Baptiste Coudurier baptiste.coudurier
Fri Oct 20 14:34:25 CEST 2006


Alexey Sidelnikov wrote:
> Baptiste Coudurier <baptiste.coudurier <at> smartjog.com> writes:
> 
>>> I have a mov file with some strange DATA stream: Stream #0.2(eng):
>>> Data: tmcd / 0x64636D74
>>>
>>> ffmpeg converts it well, but for some reason duration was not
>>> detected correct. The real duration is 79 seconds, but ffmpeg
>>> reported as 19-something minutes. It was set incorrect in 
>>> libavformat/utils.c/av_update_stream_timings() function That was
>>> because of that DATA stream. I added printfs, so the output is here:
>>>
>> Nope, your mov is 19 minutes long. Why the tmcd track is shorter than
>> the video track is the good question to ask. Wrongly cut mov file ? I
>> guess...
>>
> 
> Well... movie player says it is 79 seconds. And after I decode/encode using
> ffmpeg, new file becomes 79 seconds as well. So yes, broken mov file, I agree.
> But from the other side, ffmpeg is about video/audio processing, not data,
> right? Anyway, I'm not really good in mov container theory, so does that mean
> you reject the patch?
> 

Basically yes, patch rejected. File duration is the longest duration of
all tracks.

-- 
Baptiste COUDURIER                              GnuPG Key Id: 0x5C1ABAAA
SMARTJOG S.A.                                    http://www.smartjog.com
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
Phone: +33 1 49966312




More information about the ffmpeg-devel mailing list