Discussion:
[Bug 778676] New: vaapijpegenc does not work together with videotestsrc
(too old to reply)
"GStreamer" (GNOME Bugzilla)
2017-02-15 12:15:55 UTC
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778676

Bug ID: 778676
Summary: vaapijpegenc does not work together with videotestsrc
Classification: Platform
Product: GStreamer
Version: 1.11.1
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gstreamer-vaapi
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@intel.com
QA Contact: gstreamer-***@lists.freedesktop.org
CC: ***@gmail.com, ***@igalia.com
GNOME version: ---

In Gstreamer version 1.11.1, the following command is now broken. This worked
fine with earlier releases:

gst-launch-1.0 -e --gst-debug=vaapi*:5 videotestsrc num-buffers=60 !
vaapijpegenc ! multifilesink location=test%05d.jpg

It fails with:
0:00:00.904744007 2496 0x5596ca33a8a0 DEBUG vaapiencode
gstvaapiencode.c:420:gst_vaapiencode_get_caps:<vaapiencodejpeg0> Returning sink
caps EMPTY

The patch that breaks it is:
9bda7a6 vaapiencode: get surface formats in get_caps()

Possibly related to the discussion in:
https://bugzilla.gnome.org/show_bug.cgi?id=775490

libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: Intel i965 driver for Intel(R) Broxton - 1.8.0.pre1
(1.7.3-287-g05d2d25)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
"GStreamer" (GNOME Bugzilla)
2017-02-15 15:41:17 UTC
Permalink
Raw Message
https://bugzilla.gnome.org/show_bug.cgi?id=778676

Víctor Manuel Jáquez Leal <***@igalia.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED

--- Comment #1 from Víctor Manuel Jáquez Leal <***@igalia.com> ---
Thanks for filling this. But yes, it is the same issue as #775490. For this
specific case, it is already fixed in master. Hence, closing.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
Loading...