mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-11-09 10:59:39 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/ext/wayland/wldisplay.h

85 lines
2.7 KiB
C
Raw Normal View History

waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +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_DISPLAY_H__
#define __GST_WL_DISPLAY_H__
#include <gst/gst.h>
#include <wayland-client.h>
waylandsink: Use wl_scaler/wl_viewport to scale the surface in the compositor/hardware
2014-03-11 11:14:00 +00:00
#include "scaler-client-protocol.h"
waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +00:00
waylandsink: add G_BEGIN/END_DECLS on all headers for consistency
2014-05-22 07:10:51 +00:00
G_BEGIN_DECLS
waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +00:00
#define GST_TYPE_WL_DISPLAY (gst_wl_display_get_type ())
#define GST_WL_DISPLAY(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), GST_TYPE_WL_DISPLAY, GstWlDisplay))
#define GST_IS_WL_DISPLAY(obj) (G_TYPE_CHECK_INSTANCE_TYPE ((obj), GST_TYPE_WL_DISPLAY))
#define GST_WL_DISPLAY_CLASS(klass) (G_TYPE_CHECK_CLASS_CAST ((klass), GST_TYPE_WL_DISPLAY, GstWlDisplayClass))
#define GST_IS_WL_DISPLAY_CLASS(klass) (G_TYPE_CHECK_CLASS_TYPE ((klass), GST_TYPE_WL_DISPLAY))
#define GST_WL_DISPLAY_GET_CLASS(obj) (G_TYPE_INSTANCE_GET_CLASS ((obj), GST_TYPE_WL_DISPLAY, GstWlDisplayClass))
typedef struct _GstWlDisplay GstWlDisplay;
typedef struct _GstWlDisplayClass GstWlDisplayClass;
struct _GstWlDisplay
{
GObject parent_instance;
/* public objects */
struct wl_display *display;
struct wl_event_queue *queue;
/* globals */
struct wl_registry *registry;
struct wl_compositor *compositor;
waylandsink: create and maintain the subsurface inside the sink This means that the given surface in set_window_handle can now be the window's top-level surface on top of which waylandsink creates its own subsurface for rendering the video. This has many advantages: * We can maintain aspect ratio by overlaying the subsurface in the center of the given area and fill the parent surface's area black in case we need to draw borders (instead of adding another subsurface inside the subsurface given from the application, so, less subsurfaces) * We can more easily support toolkits without subsurfaces (see gtk) * We can get properly use gst_video_overlay_set_render_rectangle as our api to set the video area size from the application and therefore remove gst_wayland_video_set_surface_size.
2014-05-23 15:18:32 +00:00
struct wl_subcompositor *subcompositor;
waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +00:00
struct wl_shell *shell;
struct wl_shm *shm;
waylandsink: Use wl_scaler/wl_viewport to scale the surface in the compositor/hardware
2014-03-11 11:14:00 +00:00
struct wl_scaler *scaler;
waylandsink: handle the list of supported formats properly enum wl_shm_format is not a flags enum, as it may have been in the past, so multiple formats cannot be stored in a bitfield. Use an array instead.
2014-02-26 16:35:29 +00:00
GArray *formats;
waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +00:00
/* private */
gboolean own_display;
GThread *thread;
GstPoll *wl_fd_poll;
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: take into account the case where a pool may be destroyed together with GstWlDisplay There are two cases covered here: 1) The GstWlDisplay forces the release of the last buffer and the pool gets destroyed in this context, which means it unregisters all the other buffers from the GstWlDisplay as well and the display->buffers hash table gets corrupted because it is iterating. 2) The pool and its buffers get destroyed concurrently from another thread while GstWlDisplay is finalizing and many things get corrupted.
2014-07-02 10:29:55 +00:00
GMutex buffers_mutex;
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
GHashTable *buffers;
waylandsink: take into account the case where a pool may be destroyed together with GstWlDisplay There are two cases covered here: 1) The GstWlDisplay forces the release of the last buffer and the pool gets destroyed in this context, which means it unregisters all the other buffers from the GstWlDisplay as well and the display->buffers hash table gets corrupted because it is iterating. 2) The pool and its buffers get destroyed concurrently from another thread while GstWlDisplay is finalizing and many things get corrupted.
2014-07-02 10:29:55 +00:00
gboolean shutting_down;
waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +00:00
};
struct _GstWlDisplayClass
{
GObjectClass parent_class;
};
GType gst_wl_display_get_type (void);
GstWlDisplay *gst_wl_display_new (const gchar * name, GError ** error);
GstWlDisplay *gst_wl_display_new_existing (struct wl_display * display,
gboolean take_ownership, GError ** error);
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
/* see wlbuffer.c for explanation */
void gst_wl_display_register_buffer (GstWlDisplay * self, gpointer buf);
void gst_wl_display_unregister_buffer (GstWlDisplay * self, gpointer buf);
waylandsink: add G_BEGIN/END_DECLS on all headers for consistency
2014-05-22 07:10:51 +00:00
G_END_DECLS
waylandsink: process display events in a separate thread This also moves the display-related code into a new GstWlDisplay class, which takes care of the new thread
2014-02-12 10:28:40 +00:00
#endif /* __GST_WL_DISPLAY_H__ */
Reference in a new issue Copy permalink