-
Notifications
You must be signed in to change notification settings - Fork 12.4k
Comparing changes
Open a pull request
base repository: FFmpeg/FFmpeg
base: c39916bc2f43
head repository: FFmpeg/FFmpeg
compare: 4abc411b97d7
- 7 commits
- 77 files changed
- 2 contributors
Commits on Oct 1, 2012
-
Move xGA font data from lavc to lavu.
This needs to be accessible for libavfilter in the next commit.
Configuration menu - View commit details
-
Copy full SHA for 81bbce9 - Browse repository at this point
Copy the full SHA 81bbce9View commit details -
Configuration menu - View commit details
-
Copy full SHA for d771b1d - Browse repository at this point
Copy the full SHA d771b1dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2308c5b - Browse repository at this point
Copy the full SHA 2308c5bView commit details -
isom: fix redundant redeclaration of ff_mov_read_chan().
Silence a GCC warning. A leftover of the disabled version is still available in lavf/isom.c.
Configuration menu - View commit details
-
Copy full SHA for c4dba58 - Browse repository at this point
Copy the full SHA c4dba58View commit details -
nutenc: use 1/sample rate as timebase for audio instead of framesize/…
…sample rate This way audio frames can be exactly stored even when they are not aligned with timestamp 0 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Configuration menu - View commit details
-
Copy full SHA for 4eb0f5f - Browse repository at this point
Copy the full SHA 4eb0f5fView commit details -
nut: store and read the r_frame_rate
With this, when we use a finer timebase than neccessary to store durations the demuxer still knows what the original timebase was. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Configuration menu - View commit details
-
Copy full SHA for e3fb5bc - Browse repository at this point
Copy the full SHA e3fb5bcView commit details -
nutenc: choose for non audio streams a timebase with finer resolution.
While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Configuration menu - View commit details
-
Copy full SHA for 4abc411 - Browse repository at this point
Copy the full SHA 4abc411View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff c39916bc2f43...4abc411b97d7