[gst-devel] Re: bufferpools

[Julien MOUTTE]

if an element use gst_buffer_new_and_alloc but the peer element
implements a bufferalloc function the bufferalloc function is never used
right ?

so basically a first thing to do would be to implement bufferalloc in
ximagesink, that would be transparent and unused for the rest of plugins
and then implement the gst_pad_alloc_buffer in possible peers of
ximagesink such as ffcolorspace, videoscale, videotestsrc etc..

am i right ?

On Fri, 2004-01-09 at 00:53, David Schleef wrote:
> On Fri, Jan 09, 2004 at 12:03:48AM +0100, Julien MOUTTE wrote:
> > 
> > 
> > > The hard part is going through each element, and every time it
> > > allocates a buffer using gst_buffer_new_and_alloc () that is then
> > > sent to a sink pad, the call should be replaced with
> > > gst_pad_alloc_buffer (sinkpad, offset, size).
> > 
> > does that means fixing the way all plugins allocate buffers ?
> 
> Yes.  But then, with bufferpools, every element needed to be fixed
> to allocate buffers using the sink's bufferpools.  Only a few
> actually implemented this.  Now, it's nearly trivial to add support
> to elements, so I expect that by 0.8.0, a lot higher percentage
> of elements will be using sinkpad-provided buffers.
> 
> 
> 
> dave...
-- 
Julien MOUTTE - jmoutte at electronic-group.com
C.T.O.
_________________________________________________________

ELECTRONIC GROUP INTERACTIVE - www.electronic-group.com
World Trade Center, Moll de BARCELONA
Edificio Norte 4 Planta
08039 BARCELONA SPAIN
Tel : +34 93600 23 23 Fax : +34 93600 23 10
_________________________________________________________