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

Remove now redundant check.

CC: libav-stable@libav.org
Bug-Id: CID 700371

Most importantly, it contains the encoder delay and replaygain info.

Make it more structured.

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>

Signed-off-by: Martin Storsjö <martin@martin.st>

Signed-off-by: Martin Storsjö <martin@martin.st>

Whenever av_gettime() is used to measure relative period of time,
av_gettime_relative() is prefered as it guarantee monotonic time
on supported platforms.
Signed-off-by: Martin Storsjö <martin@martin.st>

Whenever av_gettime() is used to measure relative period of time,
av_gettime_relative() is prefered as it guarantee monotonic time
on supported platforms.
Signed-off-by: Martin Storsjö <martin@martin.st>

Since av_gettime() is used in a number of places where actual
real time clock is required, the monotonic clock introduced in
ebef9f5a would have consequences that are hard to handle. Instead
split it into a separate function that can be used in the cases
where only relative time is desired.

On platform where no monotonic clock is available, the difference
between the two av_gettime functions is not clear, and one could
mistakenly use the relative clock where an absolute one is
required. Therefore add an offset, to make it evident that the
time returned from av_gettime_relative never is actual current
real time, even though it is based on av_gettime.

Based on a patch by Olivier Langlois.
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
05338686.

Bug-Id: CID 732199

CC: libav-stable@libav.org

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>

Casting the left-most byte to unsigned avoids an undefined
result of the shift by 24 if bit 7 is set.

yuvPlanartouyvy_c and yuvPlanartoyuy2_c are affected.

CC: libav-stable@libav.org
Bug-Id: CID 732281 / CID 732282

Also add a note about SNDCTL_DSP_GETFMTS which may fail even if OSS is
available.

CC: libav-stable@libav.org
Bug-Id: CID 1238992
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>