diff options
| author | Clément Bœsch <u@pkh.me> | 2013-09-24 21:41:21 +0200 |
|---|---|---|
| committer | Clément Bœsch <u@pkh.me> | 2013-09-29 23:31:12 +0200 |
| commit | e6273592e442e21714d34720307e0b12a316d722 (patch) | |
| tree | 0af60f92918254f2d710e2a21f76e534afebb842 /doc/faq.texi | |
| parent | 2f8418b584d2e3d742b6c1c3b320e37c55a3df95 (diff) | |
doc/faq: rework r_frame_rate entry.
Diffstat (limited to 'doc/faq.texi')
| -rw-r--r-- | doc/faq.texi | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/faq.texi b/doc/faq.texi index a0ae537444..d06b268d01 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 +@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? |