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 795340 - vaapiencode: h264: find best profile in those available breaks encoding with mesa/AMD
vaapiencode: h264: find best profile in those available breaks encoding with ...
Status: RESOLVED DUPLICATE of bug 794306
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: 2018-04-17 20:57 UTC by Andy Furniss
Modified: 2018-06-06 08:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andy Furniss 2018-04-17 20:57:30 UTC 
fa77b2bf vaapiencode: h264: find best profile in those available

breaks eg. (The first "ERROR" is normal and seen when things work OK)

gst-launch-1.0 videotestsrc num-buffers=100  ! vaapih264enc ! "video/x-h264,profile=baseline,stream-format=byte-stream"  ! h264parse ! matroskamux ! filesink location=out.mkv
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Got context from element 'vaapiencodeh264-0': gst.vaapi.Display=context, gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayGLX\)\ vaapidisplayglx0";
0:00:00.343825398 31801      0x18869e0 ERROR       vaapivideomemory gstvaapivideomemory.c:736:gst_video_info_update_from_surface: Cannot create a VA derived image from surface 0x7f7708002800
ERROR: from element /GstPipeline:pipeline0/GstH264Parse:h264parse0: No valid frames found before end of stream
Additional debug info:
gstbaseparse.c(1329): gst_base_parse_sink_event_default (): /GstPipeline:pipeline0/GstH264Parse:h264parse0
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...
Comment 1 Víctor Manuel Jáquez Leal 2018-06-06 08:45:58 UTC 
Thanks for reporting it.

The patch on bug 794306 also fix this issue

*** This bug has been marked as a duplicate of bug 794306 ***