回复：Re: if we plan to remove TEXTURE_UPLOAD, what will be used instead?
thanks Matthew。
I know little about totem/gtk3, just wonder why not use waylandsink to render video directly to a wl_surface/wl_sub_surface.
it means to create a gtk widget which associates with a wl_sub_surface, it is a child of the main window but skip gl composition inside app.
for a dedicated video player app, texture video is just the favor of developer, not the interest of end-user.
--------------------------------
----- 原始邮件 ----- 发件人：Matthew Waters <[hidden email]> 收件人：[hidden email], Discussion of the development of and with GStreamer <[hidden email]> 主题：Re: if we plan to remove TEXTURE_UPLOAD, what will be used instead? 日期：2019年09月11日 17点10分
Hi,
1. clutter is effectively unmaintained and is really the only
major user of the gl upload meta so the first move is to remove
the clutter dependency inside totem. There are replacement Gtk
sink elements (gtkglsink and gtksink) for Gtk3 that can be used.
For Gtk4, the equivalent elements would need to written.
2. The general case for OpenGL within a Gstreamer context is to
use the libgstgl-1.0 library and the associated elements
(glupload, glcolorconvert, etc). One can pass OpenGL textures
between elements using GstGLMemory with much more information than
was ever possible with the upload meta. Currently libgstgl does
include a upload meta implementation however that implementation
will only be used if nothing else is found (except for upload from
system memory).
Cheers
-Matt
On 11/9/19 6:24 pm, HalleyZhao wrote:
Hi experts:
from the following thread, I notice that community plans to
remove TEXTURE_UPLOAD/GstGLUploadTextureMeta.
then what will be used instead?
take totem as example, it is problemtic to use clutter-sink
with hardware accerelated decoder.
then what's the decent way to render video in totem?
I removed
TEXTURE_UPLOAD support in Wayland from gstreamer-vaapi for
release 1.14, if I recall correctly, but for Canonical it
was a regression, and Daniel van Vught devoted a lot of
time to make it work, but as we confirm now, only for
Intel's driver.
We are devoting a
lot of time supporting a deprecated transfer mechanism
because people demand it. Every time I think about it, I
realized that I have said "no" when Daniel pushed for it.
Re: 回复：Re: if we plan to remove TEXTURE_UPLOAD, what will be used instead?
You can probably do that for
wayland-specific things however X11 is still used by people as
well as the cross-platform concerns for MacOS or windows that one
wouldn't want to preclude by relying specifically on wayland.
Also, resizes with wayland subsurfaces are somewhat tricky to keep
synchronised and require extra API.
Cheers
-Matt
On 12/9/19 10:16 am, HalleyZhao wrote:
thanks Matthew。
I know little about totem/gtk3, just wonder why not use
waylandsink to render video directly to a
wl_surface/wl_sub_surface.
it means to create a gtk widget which associates with a
wl_sub_surface, it is a child of the main window but skip gl
composition inside app.
for a dedicated video player app, texture video is just the
favor of developer, not the interest of end-user.
--------------------------------
----- 原始邮件 -----
发件人：Matthew Waters [hidden email]
收件人：[hidden email], Discussion of the development of and
with GStreamer [hidden email]
主题：Re: if we plan to remove TEXTURE_UPLOAD, what will be used
instead?
日期：2019年09月11日 17点10分
Hi,
1. clutter is effectively unmaintained and is really the only
major user of the gl upload meta so the first move is to
remove the clutter dependency inside totem. There are
replacement Gtk sink elements (gtkglsink and gtksink) for Gtk3
that can be used. For Gtk4, the equivalent elements would
need to written.
2. The general case for OpenGL within a Gstreamer context is
to use the libgstgl-1.0 library and the associated elements
(glupload, glcolorconvert, etc). One can pass OpenGL textures
between elements using GstGLMemory with much more information
than was ever possible with the upload meta. Currently
libgstgl does include a upload meta implementation however
that implementation will only be used if nothing else is found
(except for upload from system memory).
Cheers
-Matt
On 11/9/19 6:24 pm, HalleyZhao wrote:
Hi experts:
from the following thread, I notice that community plans
to remove TEXTURE_UPLOAD/GstGLUploadTextureMeta.
then what will be used instead?
take totem as example, it is problemtic to use
clutter-sink with hardware accerelated decoder.
then what's the decent way to render video in totem?
I removed TEXTURE_UPLOAD support in Wayland
from gstreamer-vaapi for release 1.14, if I recall
correctly, but for Canonical it was a regression, and
Daniel van Vught devoted a lot of time to make it
work, but as we confirm now, only for Intel's driver.
We are
devoting a lot of time supporting a deprecated
transfer mechanism because people demand it. Every
time I think about it, I realized that I have said
"no" when Daniel pushed for it.
Locked
signature.asc (499 bytes)