Setting a writeable flag for the appsink blocksize property
Tim-Philipp Müller
t.i.m at zen.co.uk
Mon Jun 10 03:07:53 PDT 2013
On Mon, 2013-06-10 at 10:56 +0100, George Demetriades wrote:
>
> Would you be able to explain that a little bit further please? I'm not
> sure I understand what you mean.
Which bits are unclear?
Cheers
-Tim
> On 7 June 2013 13:14, Tim-Philipp Müller <t.i.m at zen.co.uk> wrote:
> On Fri, 2013-06-07 at 13:04 +0100, George Demetriades wrote:
>
> Hi,
>
>
> > I'm not actually using the appsrc element; instead, I'm
> using a udpsrc
> > which is then decoded. The idea is to pull whole raw frames
> out of the
> > gstreamer pipeline via the appsink element which I then
> process
> > myself. The problem is that setting the blocksize element
> doesn't
> > affect the size of the buffer I receive in my callback
> function used
> > when when the "new-buffer" signal is emitted.
> >
> >
> > I'm not sure how to control the size of the buffer passed
> through to
> > the appsink though, and that is where the problem lies.
>
>
> Sorry, my fault, I misread. The same applies to appsink
> though :-)
>
> You will get buffers as they flow through the pipeline in the
> chunking
> used there. So after udpsrc that would be udp packets as
> received, after
> an RTP depayloader that might be udp payloads (possibly whole
> frames,
> e.g. if you force the depayloader to output H.264 AVC instead
> of
> byte-stream NALs).
>
> Cheers
> -Tim
>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
More information about the gstreamer-devel
mailing list