The range field has been introduced in version 1.6.0

It should only be done for DEVICE_BUSY/IN_EXECUTION

Include the libmfx error code and its description

Other parameters, like the display size, should still be taken from the
codec context.

This will allow using this function for encoding as well, where the
input format is already the semi-packed version.

Currently it's memset to 0, which is YUV420P. It should be initialized
to none.

Do not hardcode NV12. This allows 10bit decoding with -hwaccel qsv.

This is required e.g. by HEVC.

The setpts filter does not signal to the rest of the filtergraph that
the stream is CFR. Just generate the timestamps manually instead.

Signed-off-by: Anton Khirnov <anton@khirnov.net>

According to the specification on the MSDN [1], 0 is valid for that
particular field, and it should be ignored in that case.

[1]: http://msdn.microsoft.com/en-us/library/windows/desktop/dd757714(v=vs.85).aspx

Bug-Id: 950
Signed-off-by: Anton Khirnov <anton@khirnov.net>

This reverts commit 0e0538ae.

The valgrind warning was a false positive due to OSX implementation of
printf (invoking a strnlen), while this code is actually fine, since the
format specifier %.*s guarantes that no more than buf_size bytes from
buf will be read.
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>

Clang normally disguises as GCC (defining __GNUC__), and thus get
all the normal GCC specific attributes.

Clang can also work as a drop-in replacement for MSVC, and in these
cases, it doesn't define __GNUC__, but defines _MSC_VER instead.

Even in these setups, it still supports the GCC style attributes,
thus use them, especially where there isn't any MSVC specific
version, or where the MSVC specific version doesn't work on clang
(for DECLARE_ASM_CONST).
Signed-off-by: Martin Storsjö <martin@martin.st>

When targeting COFF (windows), clang doesn't support this
directive (while binutils supports it for all targets).
Signed-off-by: Martin Storsjö <martin@martin.st>

There are samples with invalid stsc that may work fine as is and
do not need extradata change. So ignore any out of range index, and
error out only when explode is set.
Found-by: Matthieu Bouron <matthieu.bouron@stupeflix.com>
Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>

Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>

This will simplify the de-MpegEncContextualization.

That code is only ever initialized with that flag set.

Fixes valgrind warning "Conditional jump or move depends on
uninitialised value(s)." from avio_flush().

Drop the packet embedded in the context.

Found-By: Jan Ruge <jan.s.ruge@gmail.com>
Bug-Id: 952

The current code will ignore the init_get_bits() failure and do an
invalid read from the uninitialized GetBitContext.
Found-By: Jan Ruge <jan.s.ruge@gmail.com>
Bug-Id: 952

It does not break anything currently, but should not be done anyway.

Signed-off-by: Anton Khirnov <anton@khirnov.net>