Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
e6273592
Commit
e6273592
authored
Sep 24, 2013
by
Clément Bœsch
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/faq: rework r_frame_rate entry.
parent
2f8418b5
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
3 deletions
+4
-3
faq.texi
doc/faq.texi
+4
-3
No files found.
doc/faq.texi
View file @
e6273592
...
...
@@ -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?
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment