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

  • Mactan@lemmy.ml
    294·
    3 months ago

    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”

    • gbin@lemmy.ca
      163·
      3 months ago

      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.

  • red@lemmy.zip
    11·
    3 months ago

    I hope this can mean I can use my android tablet as a 3rd screen with vnc with usable lag and frame rate

  • daq@lemmy.sdf.org
    6·
    3 months ago

    Pipewire works well enough for sharing screen even though it isn’t well supported by shit software like Slack. Would this replace it?

    • pnutzh4x0r@lemmy.ndlug.orgOPEnglish
      10·
      3 months ago

      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_v1 object that has various methods such as create_source and destroy. 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.

  • ashaman2007@lemm.ee
    36·
    3 months ago

    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?