As per issue2629, most 23.976fps matroska H.264 files are incorrectly
detected as 24fps, as the matroska timestamps usually have only
millisecond precision.
Fix that by doubling the amount of timestamps inspected for frame rate
for streams that have coarse time base. This also fixes 29.970 detection
in matroska.
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
(cherry picked from commit 78431098f9e306ebe27e7698d0ae539e3df2afe9)
Tested with mplayer based on this report
http://thread.gmane.org/gmane.comp.video.mplayer.user/66043/focus=66063
Signed-off-by: Reinhard Tartler <siretart@tauware.de>
(cherry picked from commit 7c152a458d3fb0a2fb1aef1f05bfee90fe70697e)
When symbol versioning is enabled, moving symbols from one library to
another breaks binary compatibility. This adds wrappers with the old
version tag for the av_*packet functions recently moved to lavc.
backport r23611 by mru
Originally committed as revision 23613 to svn://svn.ffmpeg.org/ffmpeg/branches/0.6
this patch restores binary compatibility for the av_*_packet symbols that have
been moved from libavformat to libavcodec. This patch works for gnu toolchains
only; support for ARM RCVT will be handed in for a later point release as soon
as the patch is ready and approved by the ARM maintainer(s).
Originally committed as revision 23610 to svn://svn.ffmpeg.org/ffmpeg/branches/0.6
It is not harmful and it scares too many users.
backport r23139 by bcoudurier
Originally committed as revision 23221 to svn://svn.ffmpeg.org/ffmpeg/branches/0.6
in its place.
av_metadata_set() is going to be dropped at the next major bump.
Originally committed as revision 22961 to svn://svn.ffmpeg.org/ffmpeg/trunk
Passing an explicit filename to this command is only necessary if the
documentation in the @file block refers to a file different from the
one the block resides in.
Originally committed as revision 22921 to svn://svn.ffmpeg.org/ffmpeg/trunk
when no parser is available.
This partly fixes the frame rate misdetection in issue1756.
Originally committed as revision 22824 to svn://svn.ffmpeg.org/ffmpeg/trunk
loop of ff_probe_input_buffer(), making sure that probe_size is always
set to probe_max_size in the last iteration.
Also make the function return an error if we get to the max probe
length and still cannot figure out what the format is.
Patch by Micah Galizia micahgalizia A gmail D com.
Originally committed as revision 22688 to svn://svn.ffmpeg.org/ffmpeg/trunk
AVERROR_NOFMT if the format is unknown / cannot be recognized.
It is returned AVERROR_INVALIDDATA, in the sense that the data is
invalid within what the specific libav* binary supports.
That was the last remaining use of AVERROR_NOFMT, which is going to be
dropped at the next libavutil major bump.
Originally committed as revision 22625 to svn://svn.ffmpeg.org/ffmpeg/trunk
If the format probe hits end of file, do not add the error code
to the buffer position. This is obviously wrong, and with a
small input file would cause a negative buffer overflow.
Fixes issue 1818.
Originally committed as revision 22571 to svn://svn.ffmpeg.org/ffmpeg/trunk
av_probe_input_buffer() so that it can be reused. Here are a few
differences to the original way things were probed:
- maximum probe buffer size can be specified as a parameter.
- offset within the stream to probe from can be specified as a parameter.
- instead of seeking back to the start each time a probe fails, stream
data is appended to the reallocated buffer. This lowers the amount
of data read from the stream (there is no repetition) and results in
fewer closed and reopened streams (when seeking fails).
New attempt after r22296, which was revert in r22315 due to a FATE
failure.
See the thread:
Subject: [FFmpeg-devel] [PATCH] Move av_open_input_file probe loop to its own method
Date: 2010-03-05 03:23:57 GMT
Patch by Micah F. Galizia printf("%s%s@%s.%s", "micah", "galizia", "gmail", "com").
Originally committed as revision 22532 to svn://svn.ffmpeg.org/ffmpeg/trunk
This reverts r22296. This change made some files to fail to open.
The patch submitter has promised to investigate next week.
Originally committed as revision 22315 to svn://svn.ffmpeg.org/ffmpeg/trunk
The sample rate, frame size, and channel count from the container are
not reliable when backwards compatible signaling is used.
Originally committed as revision 22301 to svn://svn.ffmpeg.org/ffmpeg/trunk
av_probe_input_buffer() so that it can be reused. Here are a few
differences to the original way things were probed:
- maximum probe buffer size can be specified as a parameter.
- offset within the stream to probe from can be specified as a parameter.
- instead of seeking back to the start each time a probe fails, stream
data is appended to the reallocated buffer. This lowers the amount
of data read from the stream (there is no repetition) and results in
fewer closed and reopened streams (when seeking fails).
Patch by Micah F. Galizia printf("%s%s@%s.%s", "micah", "galizia", "gmail", "com").
Originally committed as revision 22296 to svn://svn.ffmpeg.org/ffmpeg/trunk
This way streams with no or very few frames can be avoided during
auto selection
Originally committed as revision 21998 to svn://svn.ffmpeg.org/ffmpeg/trunk
than inside the muxers. Remove special handling of "encoder" tags from
AVI and MP3 muxers.
Patch by Anton Khirnov <wyskas gmail com>.
Originally committed as revision 21850 to svn://svn.ffmpeg.org/ffmpeg/trunk
