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 771508 - [gst-vaapi][vp9][encoder] encoder errors with cropped 2K yuv content
[gst-vaapi][vp9][encoder] encoder errors with cropped 2K yuv content
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
1.9.2
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
P1
Depends on:
Blocks:
 
 
Reported: 2016-09-16 00:19 UTC by Daniel Charles
Modified: 2017-07-17 16:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Charles 2016-09-16 00:19:47 UTC
This pipeline results in an error when encoding 2K content with particular (8 pixel non-aligned) 2K resolution


gst-launch-1.0 -e filesrc location=./someyuv_2048x858.I420 blocksize=2635776 ! video/x-raw, format=I420, width=2048, height=858, framerate=30/1, pixel-aspect-ratio=1/1 ! y4menc ! y4mdec ! vaapivp9enc rate-control=cqp keyframe-period=300 ref-pic-mode=1  ! webmmux ! filesink location=./gstvp9enc_mode1ref.webm

From the error log:

0:00:00.343707212 32394      0x1adab20 ERROR                  vaapi gstvaapiencoder.c:347:gst_vaapi_encoder_put_frame: failed to encode frame (status = -1)
0:00:00.343772163 32394      0x1adab20 ERROR            vaapiencode gstvaapiencode.c:558:gst_vaapiencode_handle_frame: failed to encode frame 0 (status -1)
Comment 1 sreerenj 2016-09-16 09:07:35 UTC
Thanks for reporting, Most probalby an issue with the resolution handling.. We will have a look, but not sure whether we can include it in 1.10 release.
Comment 2 Daniel Charles 2016-09-16 15:53:34 UTC
Sure, I am also investigating this but wanted to let gstreamer-vaapi community know about it. After the release is a safer bet.
Comment 3 Hyunjun Ko 2017-07-14 06:48:54 UTC
The commit in https://github.com/01org/intel-vaapi-driver/pull/214 fixes this issue.
I confirmed this issue is fixed with the patch in the driver.
We can close this.
Comment 4 Víctor Manuel Jáquez Leal 2017-07-17 16:57:51 UTC
Following Hyunjun comment, this is a problem in the Intel's driver, thus closing as NOTGNOME.