Wayland. It comes up a lot: “Bug X fixed in the Plasma Wayland session.” “The Plasma Wayland session has now gained support for feature Y.” And it’s in the news quite …

  • uis@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    3 years ago

    As long as it launches after pipewire

    Why? Why plasma nailed own screensharing to audio server? There already are wayland extensions for this.

        • Ullebe1@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          3 years ago

          Because Pipewire only handles and understands media streams, so it can stream the output of a window or the whole desktop, but only because the Wayland compositor has already composed the windows and other data it gets from the application to a visual and hands the final result to Pipewire.

          • uis@lemmy.world
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            3 years ago

            Which goes back to oroginal question. Why pipewire if there are already wayland extensions?

            • Ullebe1@lemmy.ml
              link
              fedilink
              arrow-up
              1
              ·
              3 years ago

              Because it is convenient for programs to use Pipewire for screensharing, as those programs can then also use the same Pipewire support for all their audio and webcam needs. Also Pipewire is good at multiplexing the various media streams.