[Bug 739332] Failing to connect vaapisink directly to decodebin

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=739332
  GStreamer | gst-plugins-base | git

--- Comment #17 from Gwenole Beauchesne <gb.devel at gmail.com> 2014-11-18 18:02:49 UTC ---
(In reply to comment #16)
> (In reply to comment #14)
> > (In reply to comment #13)
> > > You only need to ensure that it works properly with video/x-raw(sysmem) and
> > > also works properly without GstVideoMeta. That is, it should be possible to
> > > read-write map the memory!
> > 
> > Does this mean we might need to perform in-place postprocessing of decoded
> > surfaces? wrt. to comment about R/W map the memory.
> 
> It means that downstream elements must be able to read and/or write to the
> memory, without vaapidecode interfering with that... so that the modified data
> arrives further downstream.
> 
> What do you mean with in-place postprocessing?

IMHO, read *and* write to the memory could only occur for "in-place
postprocessing", i.e. modifying the same input buffer. Otherwise, most use
cases would be either reading from the memory, or writing to it.

Put it differently, in which cases, do we actually need to read and write to
the same memory handed over by the upstream element?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.