[Bug 755072] vaapi: expose memory:DMABuf capsfeature

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=755072

--- Comment #28 from sreerenj <bsreerenj at gmail.com> ---
(In reply to Víctor Manuel Jáquez Leal from comment #26)
> (In reply to sreerenj from comment #25)
> 
> > "v4l2src io-mode=dmabuf-import ! vaapipostrpoc" was the only working
> > pipeline when I was testing last time. Now the "v4l2src io-mode=dmabuf " is
> > also testable.
> 
> In my setup (HSW) only io-mode=dmabuf works. With dmabuf-import this error
> is shown:
> 
> 0:00:03.311454792  9392      0x2494e30 ERROR          v4l2allocator
> gstv4l2allocator.c:735:gst_v4l2_allocator_start:<v4l2src0:pool:src:
> allocator> error requesting 2 buffers: Invalid argument
> 0:00:03.311484207  9392      0x2494e30 ERROR         v4l2bufferpool
> gstv4l2bufferpool.c:848:gst_v4l2_buffer_pool_start:<v4l2src0:pool:src> we
> received 0 buffer from device '/dev/video0', we want at least 2
> 0:00:03.311494158  9392      0x2494e30 ERROR             bufferpool
> gstbufferpool.c:531:gboolean gst_buffer_pool_set_active(GstBufferPool *,
> gboolean):<v4l2src0:pool:src> start failed
> 
> And this looks to me an error in v4l2, not vaapi.

See the commit 82fc406dfda4d477396c1396d0cf2d03b4417d6a

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.