Announcement

Collapse
No announcement yet.

GNOME Shell + Mutter Off To A Good Start For Summer 2020

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by kravemir View Post
    I use Xorg session, because I need screensharing.
    Screensharing, screencast, as well as remote-desktop works, thanks to pipewire. If not, ask your app development to implement it.

    Why they don't start focusing on Wayland's usability, first?
    Think about it. You're commenting on a "wayland usability features", that they should focusing on wayland usability first. Thats what they do for the last 5 years. Mostly background work. If you like it or hate it, wayland is where the priority is. X11 is only a compatibility layer. Nothing to extend support even more.


    Comment


    • #32
      Originally posted by lumks View Post

      Screensharing, screencast, as well as remote-desktop works, thanks to pipewire. If not, ask your app development to implement it.
      Pipewire is mutlimedia framework for GNOME. It's not some kind of standard API for screensharing and screencasting. Or, is it? If it's a standard, then it makes sense to address this issue at Slack's developers. However, I doubt they will be implementing specific solution for (currently) very-niche Linux+GNOME+Wayland combination.

      Originally posted by lumks View Post
      Think about it. You're commenting on a "wayland usability features", that they should focusing on wayland usability first. Thats what they do for the last 5 years. Mostly background work. If you like it or hate it, wayland is where the priority is. X11 is only a compatibility layer. Nothing to extend support even more.
      I didn't imply, that they should focus on X11 (although, it would be nice to have this feature for both systems). However, to be able to productively work, there are certain features, which are considered as basic. So, good performance won't motivate developers working in teams to switch to Wayland, when they need convenient screensharing support out-of-the-box.

      Comment


      • #33
        Originally posted by kravemir View Post

        Pipewire is mutlimedia [sic] framework for GNOME. It's not some kind of standard API for screensharing and screencasting. Or, is it? If it's a standard, then it makes sense to address this issue at Slack's developers. However, I doubt they will be implementing specific solution for (currently) very-niche Linux+GNOME+Wayland combination.
        From reading the blurbs at pipewire.org I strongly suspect that screen sharing and screen casting functionality will be one of the use cases where using pipewire will eventually provide an obvious benefit to Linux application developers.

        But we shall see as the Zen Master says.
        Last edited by ermo; 07-03-2020, 05:10 AM.

        Comment


        • #34
          Originally posted by kravemir View Post

          Pipewire is mutlimedia framework for GNOME. It's not some kind of standard API for screensharing and screencasting. Or, is it? If it's a standard, then it makes sense to address this issue at Slack's developers. However, I doubt they will be implementing specific solution for (currently) very-niche Linux+GNOME+Wayland combination.



          I didn't imply, that they should focus on X11 (although, it would be nice to have this feature for both systems). However, to be able to productively work, there are certain features, which are considered as basic. So, good performance won't motivate developers working in teams to switch to Wayland, when they need convenient screensharing support out-of-the-box.
          I assume you talk about the slack app, which again uses electron and thus is based on chromium. Well, pipewire support in chromium is already there but still experimental, proper wayland support in general is coming: https://www.phoronix.com/scan.php?pa...land-Next-Year

          So thinks are coming together

          Comment


          • #35
            Originally posted by andyprough View Post
            Brutal critique of Ubuntu 20.04 and Gnome today: https://www.youtube.com/watch?v=Sez8qPipGbc
            50% cpu usage just to move a small window around.
            Let me guess, NVIDIA? RX560, i5 2500 (CPU from 2011!) and it's about 12% of 1 core, and there is an additional few percent for FullHD at 60fps screen recording - sorry about that.

            Proof: https://streamable.com/ury9jc or https://youtu.be/G5BJtWeCc1o
            Last edited by gedgon; 07-03-2020, 07:29 AM.

            Comment


            • #36
              Pipewire in Debian is outdated. Screen sharing depends on them updating their stuff.

              Comment


              • #37
                Originally posted by kravemir View Post

                I did manage to setup different framerate support with Compton, [...]
                A compositor on Xorg cannot do this at all.

                Comment


                • #38
                  Why there's no forum thread regarding variable refresh rate support? Is someone jealous? Oh, and it's Wayland only feature.

                  Comment


                  • #39
                    Originally posted by andyprough
                    Brutal critique of Ubuntu 20.04 and Gnome today: https://www.youtube.com/watch?v=Sez8qPipGbc
                    50% cpu usage just to move a small window around.
                    So I just tried the same thing and didn’t see more than 20% cpu usage. This is on Intel graphics and Wayland though.

                    Comment


                    • #40
                      Originally posted by SilverFox View Post
                      i7-7700k with nvidia on debian bullseye and i get 29% tops in gnome - xfce got 60% tops.
                      That is still waaaay too much. Now, I'm not one of the "every MB or Hz counts!!!" guys, but 29% just for moving a window is ridiculous.

                      Comment

                      Working...
                      X