Linux

48328 readers

659 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

137

Wayland Merges New Screen Capture Protocols (www.phoronix.com)

submitted 3 months ago by pnutzh4x0r@lemmy.ndlug.org to c/linux@lemmy.ml

8 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] daq@lemmy.sdf.org 6 points 3 months ago (1 children)

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.org 10 points 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.