text: 03 March 2020, 11:24 AM
  Subsurfaces are something else entirely. Just because they don't exist in X, doesn't mean dmabuf doesn't. I can only repeat - mpv uses dmabuf in the same way on X and Wayland. Of course that means mpv isn't using subsurfaces, but they aren't a necessity for zero-copy video.
  What X compositors support dmabuf then?
  03 March 2020, 11:25 AM
  No it is not. I realize this is a subjective opinion up to a point, but is not. I am writting this comment on Firefox right now having tens of tabs open, on Wayland, while a youtube video is playing on the background. I have no issue using Firefox/Wayland, right, now. If you do, well, don't use it. But saying it is "unusable" it is just FUD.
  Are you using Gnome on Arch? Try full-screening that video.
  03 March 2020, 11:26 AM
  Wake me when this supports X and VP9.
  It be cool if VDPAU could also be supported.
  Yeah, but I wouldn't hold my breath. There's always vdpau-va-driver and there's even a version that supports VP9 now: https://github.com/xtknight/vdpau-va-driver-vp9
  03 March 2020, 11:27 AM
  Ignoring your trolling, this question has already been answered.
  It's easier and faster under Wayland, which unlike X, isn't legacy technology.
  Last edited by birdie; 03 March 2020, 11:30 AM.
  03 March 2020, 11:28 AM
  X compositors deal with X drawables - pixmaps to be exact. And they do so in a zero-copy way using the GLX_EXT_texture_from_pixmap extension, which was designed specifically for zero-copy composition. dmabuf-ing of the video data happens at a far lower level, way before X gets involved.
  03 March 2020, 11:30 AM
  All of them basically, because dma-buf and other buffer sharing stuff is handled inside Xorg. dma-buf is just a unified buffer sharing API, it's not magic. Zero copy buffer sharing has been possible for a really long time... much longer than dma-buf exists.
  Last edited by brent; 03 March 2020, 11:33 AM.
  03 March 2020, 11:32 AM
  Yeah, I'm trolling. Try harder next time. Stating facts nowadays is called trolling.
  You're confusing so many things here.
  1) They're KDE Wayland bugs, they don't exist in Sway, GNOME etc.
  2) Right, and X crashing won't bring down GUI apps either?
  3) Remote desktop is working fine here.
  4) Windows is not comparable. It has a display system where it's normal that applications could loose access to the compositor (graphics driver updates etc), and applications don't usually talk it directly. Additionally, on newer versions of Windows it shouldn't be possible to run without dwm without crashing.
  03 March 2020, 11:35 AM
  Right, but applications can't directly share a dmabuf buffer with the X compositor, in the way FIrefox is doing here with the Wayland compositor (and using it with a subsurface)?
  Last edited by Britoid; 03 March 2020, 11:38 AM.
  Right, but applications can't directly share a dmabuf buffer with the X compositor, in the way FIrefox is doing here with the Wayland compositor?
  Because they DON'T NEED TO. There are X-specific ways to share buffers efficiently. They may or may not use dma-buf behind the scenes.