Víctor Manuel Jáquez Leal af3e6a8d16 vaapiencode: h264: find profile in available and allowed caps ... The commit 67e33d3de2 ("vaapiencode: h264: find best profile in those available") changed the code to pick a profile that is actually supported by the hardware. Unfortunately it dropped the downstream constraints. This can cause negotiation failures under certain circumstances. The fix is split in two cases: 1\ the available VA-API caps doesn't intersect with pipeline's allowed caps: * The best allowed profile (pipeline's caps) is set as the encoding target profile (it will be adjusted later by the available profiles and properties) 2\ the available VA-API caps does intersect with pipeline's allowed caps: * The intersected caps are fixed, and its profile is set as the encoding target profile. In this case the is not the best profile, but the minimal one (if VA-API reports the profiles in order). Setting the minimal profile of the intersected caps is better for compatibility. This patch fixes other tests related with caps negotiation, for example, it handles baseline profile, even when VA only supports constrained-baseline. Original-patch-by: Michael Olbrich <m.olbrich@pengutronix.de> https://bugzilla.gnome.org/show_bug.cgi?id=794306		2018-06-06 11:04:02 +02:00
..
vaapi	vaapiencode: h264: find profile in available and allowed caps	2018-06-06 11:04:02 +02:00
Makefile.am	build: use git.mk	2015-05-18 16:14:46 +02:00
meson.build	vaapi: add meson build	2017-02-09 11:27:44 +01:00