[Libav-user] How to determine the largest best_effort_timestamp?

Andy Shaules bowljoman at gmail.com
Tue Oct 15 17:56:41 CEST 2013


On 10/15/2013 7:34 AM, James Board wrote:
>
> >An AVI container should specify a frame rate, and the time stamp is 
> always 1/framerate * >total_frames_read  there abouts...
>
> That doesn't tell me the exact largest best_effort_timestamp.  Can I 
> determine the
> largest best_effort_timestamp exactly?  Would this be easier with a 
> file container other
> than AVI?
>
>
best_effort implies a guess. There is no guessing for an avi file. its 
uses a static frame rate whether or not there is actual video for that 
frame. The largest timestamp in the file would be total number of vid 
frames times the frame duration.


>
> On Sunday, October 13, 2013 2:20 PM, Andy Shaules 
> <bowljoman at gmail.com> wrote:
> On 10/12/2013 12:52 PM, James Board wrote:
>> In a C program with libav, how can I determine what is the largest 
>> best_effort_timestamp
>> for my input video file, which is AVI container and compressed with 
>> ffvhuff?
>>
>>
>>
>> _______________________________________________
>> Libav-user mailing list
>> Libav-user at ffmpeg.org  <mailto:Libav-user at ffmpeg.org>
>> http://ffmpeg.org/mailman/listinfo/libav-user
> An AVI container should specify a frame rate, and the time stamp is 
> always 1/framerate * total_frames_read  there abouts...
>
> If the length of the video payload is zero, then count that as a 
> dropped encoder frame, and increment the total_frames_read for it, 
> continue.
>
> Andy
>
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org <mailto:Libav-user at ffmpeg.org>
> http://ffmpeg.org/mailman/listinfo/libav-user
>
>
>
>
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/libav-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20131015/6d39f103/attachment.html>


More information about the Libav-user mailing list