After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 769253 - vaapidecodebin ! glimagesink fails performing vaapi postprocessing
vaapidecodebin ! glimagesink fails performing vaapi postprocessing
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-07-28 03:21 UTC by Matthew Waters (ystreet00)
Modified: 2018-11-03 15:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
*vaapi*:6,gl*:6,3 log (213.13 KB, text/plain)
2016-07-28 10:08 UTC, Matthew Waters (ystreet00)
Details

Description Matthew Waters (ystreet00) 2016-07-28 03:21:11 UTC
With latest gst master with vaapi available/enabled, gst-launch-1.0 playbin uri=blah video-sink=glimagesink results in pipeline failure with:

ERROR vaapipostproc gstvaapipostproc.c:803:gst_vaapipostproc_process_vpp: failed to apply VPP filters (error 2)

Running on an intel chip

Also, vaapidecode doesn't seem to exist anymore by itself so simple testing without vaapipostproc is problematic.
Comment 1 Víctor Manuel Jáquez Leal 2016-07-28 09:17:36 UTC
Hi Matthew,

I'm trying to reproduce your error, but I can't :(

Can you upload the vaapi*:6 log, the media sample (if it is possible) and post your chip model??
Comment 2 Matthew Waters (ystreet00) 2016-07-28 10:08:33 UTC
Created attachment 332268 [details]
*vaapi*:6,gl*:6,3 log

chip model: Intel(R) Core(TM) i5-3337U

Can also be reproduced with:

gst-launch-1.0 videotestsrc ! video/x-raw,width=1920,height=1080 ! x264enc tune=zerolatency ! queue ! h264parse ! vaapidecodebin ! glimagesink

But not with 320x240 which is very odd.
Comment 3 Matthew Waters (ystreet00) 2016-07-28 10:15:45 UTC
It seems that it fails if either the width or height is not a multiple of 16.
Comment 4 Víctor Manuel Jáquez Leal 2016-07-28 13:41:43 UTC
I have run the pipeline from comment 2, in my haswell laptop, using master, and it works. Your microarchitecture is Ivy bridge. I believe I have a laptop with that cpu. I'll check it.
Comment 5 Sjoerd Simons 2017-01-30 23:27:41 UTC
I'm seeing the same issue on an "Intel(R) Celeron(R) CPU  N2930  @ 1.83GHz", seemingly postprocessing wants to crop the image from 1920x1088 to 1920x1080 and hits: 
0:00:02.266265988 11502 0x7fba8001b680 DEBUG                  vaapi gstvaapiutils.c:53:vaapi_check_status: vaEndPicture(): invalid VASurfaceID

after which everthing falls apart.
Comment 6 Sjoerd Simons 2017-02-03 23:15:47 UTC
This seems to be due to https://github.com/01org/intel-vaapi-driver/issues/20, downgraded the vaapi driver to 1.5.x makes things work happily again.
Comment 7 Fabrice Bellet 2017-03-06 22:18:45 UTC
I have the same problem, and it seems to me that commit bd018d61 in intel-vaapi-driver introduced this bug.
Comment 8 GStreamer system administrator 2018-11-03 15:48:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/41.