mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-20 00:31:13 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/ext/wayland/wlbuffer.h

69 lines
2.3 KiB
C
Raw Normal View History

waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
/* GStreamer Wayland video sink
*
* Copyright (C) 2014 Collabora Ltd.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Library General Public
* License as published by the Free Software Foundation; either
* version 2 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Library General Public License for more details.
*
* You should have received a copy of the GNU Library General Public
* License along with this library; if not, write to the Free
* Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
* Boston, MA 02110-1301 USA.
*/
#ifndef __GST_WL_BUFFER_H__
#define __GST_WL_BUFFER_H__
waylandsink: stack the video subsurface into another subsurface that covers the whole render rectangle The main reason behind this is that when the video caps change and the video subsurface needs to resize and change position, the wl_subsurface.set_position call needs a commit in its parent in order to take effect. Previously, the parent was the application's surface, over which there is no control. Now, the parent is inside the sink, so we can commit it and change size smoothly. As a side effect, this also allows the sink to draw its black borders on its own, without the need for the application to do that. And another side effect is that this can now allow resizing the sink when it is in top-level mode and have it respect the aspect ratio.
2014-07-01 08:43:20 +00:00
#include "wldisplay.h"
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
G_BEGIN_DECLS
#define GST_TYPE_WL_BUFFER (gst_wl_buffer_get_type ())
#define GST_WL_BUFFER(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), GST_TYPE_WL_BUFFER, GstWlBuffer))
#define GST_IS_WL_BUFFER(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), GST_TYPE_WL_BUFFER))
#define GST_WL_BUFFER_CLASS(klass) (G_TYPE_CHECK_CLASS_CAST ((klass), GST_TYPE_WL_BUFFER, GstWlBufferClass))
#define GST_IS_WL_BUFFER_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((klass), GST_TYPE_WL_BUFFER))
#define GST_WL_BUFFER_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS ((obj), GST_TYPE_WL_BUFFER, GstWlBufferClass))
typedef struct _GstWlBuffer GstWlBuffer;
typedef struct _GstWlBufferClass GstWlBufferClass;
struct _GstWlBuffer
{
GObject parent_instance;
struct wl_buffer * wlbuffer;
waylandsink: Update stale GstBuffer references in wayland buffer cache "waylandsink: use GstMemory instead of GstBuffer for cache lookup" changes the cache key to GstMemory, but the cached data still needs a pointer to the GstBuffer to control the buffer lifecycle. If the GstMemory used as the cache key moves from one GstBuffer to another, the pointer in the cached data will be out-of-date. Update the current GstBuffer pointer for each frame so that it always represents the currently in use (from attach to release) GstBuffer for each wl_buffer. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1473>
2020-07-22 07:32:37 +00:00
GstBuffer *current_gstbuffer;
GstMemory *gstmem;
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
GstWlDisplay *display;
gboolean used_by_compositor;
};
struct _GstWlBufferClass
{
GObjectClass parent_class;
};
GType gst_wl_buffer_get_type (void);
waylandsink: stack the video subsurface into another subsurface that covers the whole render rectangle The main reason behind this is that when the video caps change and the video subsurface needs to resize and change position, the wl_subsurface.set_position call needs a commit in its parent in order to take effect. Previously, the parent was the application's surface, over which there is no control. Now, the parent is inside the sink, so we can commit it and change size smoothly. As a side effect, this also allows the sink to draw its black borders on its own, without the need for the application to do that. And another side effect is that this can now allow resizing the sink when it is in top-level mode and have it respect the aspect ratio.
2014-07-01 08:43:20 +00:00
GstWlBuffer * gst_buffer_add_wl_buffer (GstBuffer * gstbuffer,
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
struct wl_buffer * wlbuffer, GstWlDisplay * display);
waylandsink: Keep per display wayland buffer caches Instead of attaching a single wayland wl_buffer to each GStBuffer as qdata, keep a separate cache for each display. A unique wl_buffer and associated metadata is created for each display. This allows for sharing of GstBuffer objects between multiple displays, such as when using tee elements. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1401>
2020-07-08 10:06:38 +00:00
GstWlBuffer * gst_buffer_get_wl_buffer (GstWlDisplay * display, GstBuffer * gstbuffer);
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
waylandsink: Keep per display wayland buffer caches Instead of attaching a single wayland wl_buffer to each GStBuffer as qdata, keep a separate cache for each display. A unique wl_buffer and associated metadata is created for each display. This allows for sharing of GstBuffer objects between multiple displays, such as when using tee elements. Part-of: <https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1401>
2020-07-08 10:06:38 +00:00
void gst_wl_buffer_force_release_and_unref (GstBuffer *buf, GstWlBuffer * self);
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
waylandsink: stack the video subsurface into another subsurface that covers the whole render rectangle The main reason behind this is that when the video caps change and the video subsurface needs to resize and change position, the wl_subsurface.set_position call needs a commit in its parent in order to take effect. Previously, the parent was the application's surface, over which there is no control. Now, the parent is inside the sink, so we can commit it and change size smoothly. As a side effect, this also allows the sink to draw its black borders on its own, without the need for the application to do that. And another side effect is that this can now allow resizing the sink when it is in top-level mode and have it respect the aspect ratio.
2014-07-01 08:43:20 +00:00
void gst_wl_buffer_attach (GstWlBuffer * self, struct wl_surface *surface);
waylandsink: rework the mechanism for keeping buffers out of the pool until wl_buffer::release This also removes the GstWlMeta and adds a wrapper class for wl_buffer which is saved in the GstBuffer qdata instead of being a GstMeta. The motivation behind this is mainly to allow attaching wl_buffers on GstBuffers that have not been allocated inside the GstWaylandBufferPool, so that if for example an upstream element is sending us a buffer from a different pool, which however does not need to be copied to a buffer from our pool because it may be a hardware buffer (hello dmabuf!), we can create a wl_buffer directly from it and first, attach it on it so that we don't have to re-create a wl_buffer every time the same GstBuffer arrives and second, force the whole mechanism for keeping the buffer out of the pool until there is a wl_buffer::release on that foreign GstBuffer.
2014-06-20 11:47:57 +00:00
G_END_DECLS
#endif /* __GST_WL_BUFFER_H__ */
Reference in a new issue Copy permalink