~thong-u/unoptimized/+git/gstreamer-vaapi:0.6

Last commit made on 2015-09-23
Get this branch:
git clone -b 0.6 https://git.launchpad.net/~thong-u/unoptimized/+git/gstreamer-vaapi

Branch merges

Branch information

Recent commits

89dee9a... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

0.6.1

e09ba2b... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

NEWS: updates for 0.6.1

d1db1e0... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

gstcompat: add gst_buffer_copy_deep() if gst < 1.5

gst_buffer_copy_deep() was added in GStreamer 1.5. If want to use it we should
add an implementation if gstreamer-vaapi is linked to previous versions.

Signed-off-by: Víctor Manuel Jáquez Leal <email address hidden>

ab0a58a... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

vaapidecode: simplify copy of GstVideoCodecState

Signed-off-by: Víctor Manuel Jáquez Leal <email address hidden>

3bdc796... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

build: link libgstvaapi_parse against codec parser

GST_CODEC_PARSER_* variables are defined if builtin codec parsers are disabled
when running configure.

Right now, libgstcodecparsers links only to libgstvaapi, but libgstvaapi_parse
need it if builtin codec parsers are disabled.

This patch adds GST_CODEC_PARSER_* variables to libgstvaapi_parse
compilation. If builtin codec parsers are enable, this variable is null, so it
should work using libgstvaapi, as normal.

Signed-off-by: Víctor Manuel Jáquez Leal <email address hidden>

https://bugzilla.gnome.org/show_bug.cgi?id=754845

20a8be7... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

build: verify for H264 MVC and H265 SPS

Currently the H264 and H265 parsers look for MVC and SPS respectively, and
the required symbols for those were added in GStreamer 1.5

If we try to compile in GStreamer < 1.4, without enabling the builtin codec
parsers, the compilation fails, because the lack of those symbols.

This patch verifies if the installed H264 and H265 parsers have those symbols. If
they do not, the specific built in codec parsers are enabled and used.

Signed-off-by: Víctor Manuel Jáquez Leal <email address hidden>

https://bugzilla.gnome.org/show_bug.cgi?id=754845

f26a9a7... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

decoder: h264: initialize PPS's slice_group_id

When the GstVaapiParserInfoH264 is allocated, the memory is not initialized,
so it contains random data.

When gst_h264_parser_parse_pps() fails, the PPS structure keeps slice_group_id
pointer uninitialized, leading to a segmentation fault when the memory is
freed.

This patch prevents this by initializing the slice_group_id before the PPS
parsing.

Signed-off-by: Víctor Manuel Jáquez Leal <email address hidden>

https://bugzilla.gnome.org/show_bug.cgi?id=754845

b69d227... by Mark Nauwelaerts <email address hidden>

vaapidecode: proper numerator and denominator for forced latency framerate

https://bugzilla.gnome.org/show_bug.cgi?id=755040

14a27ec... by =?utf-8?q?V=C3=ADctor_Manuel_J=C3=A1quez_Leal?= <email address hidden>

vaapidecode: renegotiate if caps are not equal

The use of gst_caps_is_always_compatible() for this optimization may lead to
false positives. It is better to stick to gst_caps_is_strictly_equal() to know
if it is required a re-negotiation.

Signed-off-by: Víctor Manuel Jáquez Leal <email address hidden>

https://bugzilla.gnome.org/show_bug.cgi?id=750835

8b7b163... by Sreerenj Balachandran <email address hidden>

vaapidecode: Always keep a copy of input codec state

Currently we are sharing the input GstVideoCodecState with
GstVaapiDecoder(gst-libs/gst/vaapi) by just doing ref and unref for
each caps change. This is troublesome in many cases, for eg: if
resoultion changes with in a singe stream. Because, when ever there
is a resolution change, GstVideoDecoder will first change the Codec_state->caps
fields with new resolution, but since we are using the same codecstate (ref)
in gstvaapidecode.c, the caps check for input caps change will always fail.

https://bugzilla.gnome.org/show_bug.cgi?id=753914