| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 703626
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732203 / CID 732204
|
|
|
|
|
|
|
| |
The code would have segfaulted before if oggstream were NULL.
CC: libav-stable@libav.org
Bug-Id: CID 732218
|
|
|
|
|
|
| |
Makes coverity less confused and code more readable.
Bug-Id: CID 732262
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 733777
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732246
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
should be the raw amount of pixels (for example 3840x1080 for full HD side by
side) and the DisplayWidth/Height in pixels should be the amount of pixels for
one plane (1920x1080 for that full HD stream)."
So, move the aspect ratio check in the mkv_write_stereo_mode() function
and always write the embl when stereo format and/or aspect ration is set.
Also add a few comments to that function.
CC: libav-stable@libav.org
Found-by: Asan Usipov <asan.usipov@gmail.com>
|
|
|
|
|
|
|
| |
While a standalone implementation is nice, we already depend on
gmtime and gmtime_r in a number of places.
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
|
|
|
|
|
|
| |
gmtime isn't thread safe in general. In msvcrt (which lacks gmtime_r),
the buffer used by gmtime is thread specific though.
One call to localtime is left in avconv_opt.c, where thread safety
shouldn't matter (instead of making avconv depend on the libavutil
internal header).
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
|
|
|
| |
If the buffer provided to strftime is too small, the buffer contents
are indeterminate - it does not guarantee actually null terminating
the buffer.
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
| |
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 1197050
|
|
|
|
|
|
|
|
|
| |
None of these are likely unless the user is writing a file with two billion
streams or a duration of around two months.
CC: libav-stable@libav.org
Bug-Id: CID 700568 / CID 700569 / CID 700570 /
CID 700571 / CID 700572 / CID 700573
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732232
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 703629
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 733712
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 1026767
|
|
|
|
|
|
|
|
|
| |
The new function wraps errno so that its value is correctly reported
when other functions overwrite it (eg. in case of logging).
CC: libav-stable@libav.org
Bug-Id: CID 1135748
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
|
|
|
|
|
|
|
|
| |
At "mimetype[len] = 0;" mimetype is a 64 element array and len might be
equal to or greater than that.
CC: libav-stable@libav.org
Bug-Id: CID 1061055
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 1087077
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 1087078
|
|
|
|
| |
Most importantly, it contains the encoder delay and replaygain info.
|
|
|
|
|
|
|
| |
The quality scale field is only supposed to be present if the fourth bit
is set. In practice, lame always sets it, but other tools might not.
CC:libav-stable@libav.org
|
|
|
|
|
|
|
|
|
| |
The ones left using av_gettime are NTP timestamps (for RTCP,
which is specified to send the actual current realtime clock
in RTCP SR packets), and the NUT muxer timestamper, which is
documented as using wallclock time.
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 733713
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 703721
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 90558
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 733714
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732242
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 718141
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732248
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 1238797
|
|
|
|
|
|
| |
Chapters do not have an event_flags field.
Bug-Id: CID 1231990
|
|
|
|
|
|
| |
len is always >=1 in that case.
Bug-Id: CID 1238784
|
|
|
|
|
|
|
| |
Expression already evaluated before, redundant since
053386864219eccbcca1886c55f902f9555428a5.
Bug-Id: CID 732199
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 718002
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 1198258
|
|
|
|
|
|
|
| |
Avoid a possible null pointer dereference.
CC: libav-stable@libav.org
Bug-Id: CID 1135769
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732284
|
|
|
|
|
| |
CC: libav-stable@libav.org
Bug-Id: CID 732198
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prevent possible memory leaks.
Connect to nginx and request a non-existent resource to
trigger the issue.
CC: libav-stable@libav.org
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Signed-off-by: Uwe L. Korn <uwelk@xhochy.com>
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
|
|
|
|
| |
It is a remnant of the old interrupt callback API.
|
|
|
|
| |
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
|
|
|
| |
Some RTMP commands need the most recent timestamp as their parameter, so
keep track of it. This must be the most recent one and not e.g. the max
received timestamp as it can decrease again through seeking.
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
|
|
|
|
|
| |
In (non-live) streams with no metadata, the duration of a stream can
be retrieved by calling the RTMP function getStreamLength with the
playpath. The server will return a positive duration upon the request if
the duration is known, otherwise either no response or a duration of 0
will be returned.
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
|
|
|
|
| |
Packets that contain a number as a result to a rtmp function call are
structured the same way (String, Number, Null, Number). This new method
also includes more bounds checks to better handle packets that are not
structured as expected.
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
|
|
|
| |
Work as the other free()-like functions.
Bug-Id: CID 1087081
CC: libav-stable@libav.org
|
|
|
|
|
| |
CC: libav-stable@libav.org
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
| |
Signed-off-by: Martin Storsjö <martin@martin.st>
|
|
|
|
| |
Signed-off-by: Martin Storsjö <martin@martin.st>
|