[Bug 619500] It is not possible to "recycle" buffers without subclassing GstBuffer object
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Tue Feb 22 07:19:10 PST 2011
https://bugzilla.gnome.org/show_bug.cgi?id=619500
GStreamer | gstreamer (core) | 0.10.29
--- Comment #12 from Tommi Myöhänen <tommi.myohanen at digia.com> 2011-02-22 15:19:07 UTC ---
(In reply to comment #11)
> > So, ultimately what I'd like to achieve:
> >
> > 1) My (source) element wants to pre-allocate a pool of buffers from downstream
> > 2) The element wants to know when the pushed buffer has been rendered, so that
> > it can revive it back to the pool
>
> what is the point of (2)? when the buffer is rendered it will go back to the
> owner of the pool (xvimagesink) why would a downstream element be interested in
> when that happens?
The point is that this source element wants to get that pre-allocated buffer
back to its own pool. It doesn't want it to go into the owner's pool.
For example, if you run v4l2src ! xvimagesink pipeline, there will be one
memcpy() per frame, when xvimagesink (or X window system in general) copies the
video frame to video hardware memory. How can we eliminate that memcpy()
operation?
--
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.
More information about the gstreamer-bugs
mailing list