The Intel binary iHD driver does not support the
VASurfaceAttribMemoryType, so surface allocation will fail when using
it.

Adds a wrapper function for downmixing which detects channel count changes
and updates the selected downmix function accordingly.

Simplification and porting to current x86inc infrastructure by Diego Biurrun.
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

This is about 200% faster for in-decoder downmixing of 5.0 and 5.1 content.
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

Also use (float **) instead of (float (*)[2]). This matches the matrix
layout in libavresample so we can reuse assembly code between the two.
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

Move the doxy above the definition, change the value itself to the
(1 << n) pattern, which is more readable for flags.

It is supposed to be a flag. The only currently defined value is
AVIO_SEEKABLE_NORMAL, but other ones may be added in the future.
However all the current lavf code treats this field as a bool (mainly
for historical reasons).
Change all those cases to properly check for AVIO_SEEKABLE_NORMAL.

This fixes decoding corruption on 64 bit windows.
Signed-off-by: NMartin Storsjö <martin@martin.st>

This avoids SIMD-optimized functions having to sign-extend their
stride argument manually to be able to do pointer arithmetic.

ptrdiff_t is the correct type for array strides and similar.

ptrdiff_t is the correct type for array strides and similar.

ptrdiff_t is the correct type for array strides and similar.

This avoids SIMD-optimized functions having to sign-extend their
stride argument manually to be able to do pointer arithmetic.

ptrdiff_t is the correct type for array strides and similar.

ptrdiff_t is the correct type for array strides and similar.

ptrdiff_t is the correct type for array strides and similar.

Also rename all such parameters to "stride" for consistency.

While outwardly bizarre, this change makes the behaviour consistent
with other VAAPI encoders which sync to the encode /input/ picture in
order to wait for /output/ from the encoder.  It is not harmful on
i965 (because synchronisation already happens in vaRenderPicture(),
so it has no effect there), and it allows the encoder to work on
mesa/gallium which assumes this behaviour.

This improves behaviour with drivers which do not support packed
headers, such as AMD VCE on mesa/gallium.

This allows better checking of capabilities and will make it easier
to add more functionality later.

It also commonises some duplicated code around rate control setup
and adds more comments explaining the internals.

It is used to select functions that work with 9-15bits.

Make sure the scaling functions for the 9-15bits are used for
9-15bits bit depths correctly.

Follow a 420, 422, 444 order instead of a random one.
This simplifies double-checking additions of new formats.
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
Signed-off-by: NDiego Biurrun <diego@biurrun.de>

Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
Signed-off-by: NDiego Biurrun <diego@biurrun.de>
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>

And use a macro to reduce the boilerplate.
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
Signed-off-by: NDiego Biurrun <diego@biurrun.de>
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>