Wayland Merges New Screen Capture Protocols
(www.phoronix.com)
from pnutzh4x0r@lemmy.ndlug.org to linux@lemmy.ml on 11 Aug 2024 11:45
https://lemmy.ndlug.org/post/965376
from pnutzh4x0r@lemmy.ndlug.org to linux@lemmy.ml on 11 Aug 2024 11:45
https://lemmy.ndlug.org/post/965376
The ext-image-capture-source-v1 and ext-image-copy-capture-v1 screen copy protocols build upon wlroots’ wlr-screencopy-unstable-v1 with various improvements for better screen capture support under Wayland. These new protocols should allow for better performance and window capturing support for use-cases around RDP/VNC remote desktop, screen sharing, and more.
Merge Request: Create ext-image-capture-source-v1 and ext-image-copy-capture-v1
threaded - newest
under the definition of bike shedding in the Encyclopedia you’ll find wayland the prime example. been waiting years on one pr for them to decide on the word “may” vs “will”
It drives me crazy. Just release it 18+months ago and iterate with versions, at least your users will have the feature in their hands.
.
It is kind of shooting at the ambulance, zoom needs to also adapt to the new API. The alternative is a completely non functional Wayland for videoconferencing for years… Unusable stable is not better than unstable usable IMHO at least you have a shot at fixing it for the second option.
.
I assume they went with way land as a compromise.
I hope this can mean I can use my android tablet as a 3rd screen with vnc with usable lag and frame rate
So… does THIS mean that this doesn’t support explicit sync, right as explicit sync is about to be stable and supported in the NVIDIA 560/565 drivers? As far as I know there are currently other ways to do screen capture outside of this protocol on Wayland so its not like there are no interim solutions, why release this when it is essentially still incomplete?
Pipewire works well enough for sharing screen even though it isn’t well supported by shit software like Slack. Would this replace it?
No, most likely Pipewire would be used to implement the protocol for various compositors.
Think of the protocols as high-level descriptions of interfaces (or designs) that specify what needs to be implemented to support a particular feature (in this case capturing images of a “screen”). Looking at this one, it describes a
ext_image_capture_source_v1object that has various methods such ascreate_sourceanddestroy. Different compositors could then implement or support this interface with whatever technology they wish (most will rely on Pipewire).This is already the case with the existing screensharing protocol. For instance wlroots uses pipewire buffers in xdg-desktop-portal-wlr.