[FFmpeg-devel] [PATCH 1/4] doc/faq: rework r_frame_rate entry.
Clément Bœsch
u at pkh.me
Tue Sep 24 21:46:27 CEST 2013
---
doc/faq.texi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/faq.texi b/doc/faq.texi
index a0ae537..d06b268 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -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.
-r_frame_rate is NOT the average frame rate, it is the smallest frame rate
+ at 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
wrong if it is larger than the average!
-For example, if you have mixed 25 and 30 fps content, then r_frame_rate
-will be 150.
+For example, if you have mixed 25 and 30 fps content, then @code{r_frame_rate}
+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?
--
1.8.4
More information about the ffmpeg-devel
mailing list