[Gstreamer-openmax] Proposal of new implementation
felipe.contreras at gmail.com
Wed Jan 26 05:59:41 PST 2011
2011/1/25 Clark, Rob <rob at ti.com>:
> 2011/1/25 Victor Manuel Jáquez Leal <ceyusa at gmail.com>:
>> 2011/1/25 Benjamin Gaignard <benjamin.gaignard at linaro.org>:
>>> you are right, the operation flow are very similar but we create an
>>> overloaded gst buffer (gstomxbuffer) to allow zero copy in gstreamer graph
>> Aha, the same strategy used in gst-goo . There was a reason why
>> Felipec didn't use it, but I don't recalled it right know :s
>> 1. https://github.com/mrchapp/gst-goo/blob/master/src/gstgoobuffer.c
> it is similar.. but not really intended for "ghost buffers" (tunneling)..
> I guess for most common scenario's Felipec was not using an omx based
> sink element.. and also didn't have the same constraints about
> physically contiguous buffers in the decoder/encoder elements. And
> also not the same complications of reference counting when sharing
> buffers with the decoder.
Huh? Physically contiguous buffers? Are we talking about linux here?
More information about the Gstreamer-openmax