Traneptora/FFmpeg
1
Fork 0
forked from FFmpeg/FFmpeg
Code Pull requests Activity

doc/faq: rework r_frame_rate entry.

Browse source
This commit is contained in:
Clément Bœsch 2013-09-24 21:41:21 +02:00
parent 2f8418b584
commit e6273592e4
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/faq.texi
View file

@ -537,11 +537,12 @@ In this specific case please look at RFC 4629 to see how it should be done.
@section AVStream.r_frame_rate is wrong, it is much larger than the frame rate. @section AVStream.r_frame_rate is wrong, it is much larger than the frame rate.
r_frame_rate is NOT the average frame rate, it is the smallest frame rate @code{r_frame_rate} is NOT the average frame rate, it is the smallest frame rate
that can accurately represent all timestamps. So no, it is not that can accurately represent all timestamps. So no, it is not
wrong if it is larger than the average! wrong if it is larger than the average!
For example, if you have mixed 25 and 30 fps content, then r_frame_rate For example, if you have mixed 25 and 30 fps content, then @code{r_frame_rate}
will be 150. will be 150 (it is the least common multiple).
If you are looking for the average frame rate, see @code{AVStream.avg_frame_rate}.
@section Why is @code{make fate} not running all tests? @section Why is @code{make fate} not running all tests?