"GStreamer" (GNOME Bugzilla)
2018-04-19 08:21:45 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=795372
Bug ID: 795372
Summary: vaapi encoding requires stream-format=byte-stream on
radeonsi since 1.14
Classification: Platform
Product: GStreamer
Version: 1.14.0
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gstreamer-vaapi
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: haagch+***@frickel.club
QA Contact: gstreamer-***@lists.freedesktop.org
CC: ***@gmail.com, ***@igalia.com
GNOME version: ---
RX 480, latest mesa git.
Since gstreamer 1.14 a simple vaapi encoding pipeline that has been working on
1.12.4 never starts encoding and produces a 0 byte output file when pressing
ctrl+c:
$ LANG=en gst-launch-1.0 videotestsrc ! vaapih264enc !
"video/x-h264,profile=baseline" ! h264parse ! matroskamux ! filesink
location=output.mkv
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Got context from element 'vaapiencodeh264-0': gst.vaapi.Display=context,
gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayGLX\)\ vaapidisplayglx0";
^Chandling interrupt.
Interrupt: Stopping pipeline ...
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
^C
I was told this is something that should be reported, so here it is.
The workaround for now is to specify stream-format=byte-stream yourself, like
this:
gst-launch-1.0 videotestsrc ! vaapih264enc !
"video/x-h264,profile=baseline,stream-format=byte-stream" ! h264parse !
matroskamux ! filesink location=output.mkv
this pipeline works fine with gstreamer 1.14.
The same is true for an equivalent h.265 pipeline:
gst-launch-1.0 videotestsrc ! vaapih265enc !
"video/x-h265,stream-format=byte-stream" ! h265parse ! matroskamux ! filesink
location=output.mkv
Bugzilla shows a few other issues that may be relevant, for example maybe bug
732167.
Bug ID: 795372
Summary: vaapi encoding requires stream-format=byte-stream on
radeonsi since 1.14
Classification: Platform
Product: GStreamer
Version: 1.14.0
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gstreamer-vaapi
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: haagch+***@frickel.club
QA Contact: gstreamer-***@lists.freedesktop.org
CC: ***@gmail.com, ***@igalia.com
GNOME version: ---
RX 480, latest mesa git.
Since gstreamer 1.14 a simple vaapi encoding pipeline that has been working on
1.12.4 never starts encoding and produces a 0 byte output file when pressing
ctrl+c:
$ LANG=en gst-launch-1.0 videotestsrc ! vaapih264enc !
"video/x-h264,profile=baseline" ! h264parse ! matroskamux ! filesink
location=output.mkv
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Got context from element 'vaapiencodeh264-0': gst.vaapi.Display=context,
gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayGLX\)\ vaapidisplayglx0";
^Chandling interrupt.
Interrupt: Stopping pipeline ...
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
^C
I was told this is something that should be reported, so here it is.
The workaround for now is to specify stream-format=byte-stream yourself, like
this:
gst-launch-1.0 videotestsrc ! vaapih264enc !
"video/x-h264,profile=baseline,stream-format=byte-stream" ! h264parse !
matroskamux ! filesink location=output.mkv
this pipeline works fine with gstreamer 1.14.
The same is true for an equivalent h.265 pipeline:
gst-launch-1.0 videotestsrc ! vaapih265enc !
"video/x-h265,stream-format=byte-stream" ! h265parse ! matroskamux ! filesink
location=output.mkv
Bugzilla shows a few other issues that may be relevant, for example maybe bug
732167.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.