gstreamer-devel Digest, Vol 29, Issue 22

[George Demetriades]

> Date: Wed, 05 Jun 2013 11:15:57 +0100
> From: Tim-Philipp M?ller <t.i.m at zen.co.uk>
> To: gstreamer-devel at lists.freedesktop.org
> Subject: Re: appsink buffer size control
> Message-ID: <1370427357.2998.4.camel at zingle>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, 2013-06-05 at 11:11 +0100, George Demetriades wrote:
> > I'm writing a C++ program which involves passing a whole uncompressed
> > video frame from my gstreamer pipeline through to my own application
> > for processing, but I'm not able to make the pulled buffer the correct
> > size. The I420 frame I want to pull is at 480 x 360, with 8 bits per
> > pixel: including the chroma segment of the frame, this should be
> > 259,200 bytes. Instead, GST_BUFFER_SIZE shows the pulled frame to only
> > be 26,496 bytes large - obviously far too small.
> >
> >
> > Would anyone be able to tell me how to fix the size of the buffer
> > coming from my pipeline into the appsink? Is that even a parameter
> > that the developer can control, or is it an internally-decided size?
> >
> >
> > For reference, I'm running h264-encoded video from a udpsrc, through
> > flutsdemux (to strip out the audio), through a fluh264dec (to decode
> > the video into raw frames) and then into my appsink.
> >
> >
> > Any help or guidance would be greatly appreciated, I've been
> > struggling with this for a few days now.
>
> Did you print the GST_BUFFER_CAPS() on the buffer to see what the format
> is ?
>
> Cheers
>  -Tim
>
>
I've just tried that, and it's a bit baffling: the caps are not what I've
set, but they still do not correspond to the amount of memory taken up by
the buffer.

George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20130605/c7f8964e/attachment.html>