Announcement

Collapse
No announcement yet.

Firefox 75 On Wayland Now To Have Full WebGL, Working VA-API Acceleration

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

  • #71
    Originally posted by darkbasic View Post

    As far as I remember all 60 fps videos didn't have any high quality h264 version.
    I've just re-installed h264ify and enabled it, and looking at one of my videos it still uses vp9 for *all* the resolutions: https://www.youtube.com/watch?v=qBh6-Pd5Otw
    I don't know if the extension is broken or 60 fps is simply not supported, but I also remember not being able to watch most of the youtube videos at 60 fps with my early Talos ppc64le system which didn't have vp9 support compiled in.
    Works fine for me on that video. I get AVC1, [email protected], Firefox Nightly.
    GrayShade
    Senior Member
    Last edited by GrayShade; 03 March 2020, 03:31 PM.

    Comment


    • #72
      Originally posted by GrayShade View Post

      Works fine for me on that video. I get AVC1, [email protected]
      That's weird... it works only if I block 60 fps videos in the extension. Arch Linux and Chromium 80 here.
      ## VGA ##
      AMD: X1950XTX, HD3870, HD5870
      Intel: GMA45, HD3000 (Core i5 2500K)

      Comment


      • #73
        Originally posted by darkbasic View Post

        it works only if I block 60 fps videos in the extension
        Here is a snippet of output from a certain cli program with the --list-formats flag:

        Code:
        136 mp4 1280x688 720p 328k , avc1.4d401f, 30fps, video only, 3.59MiB
        298 mp4 1280x688 720p60 354k , avc1.4d4020, 60fps, video only, 3.94MiB
        247 webm 1280x688 720p 359k , vp9, 30fps, video only, 3.96MiB
        302 webm 1280x688 720p60 452k , vp9, 60fps, video only, 4.78MiB
        137 mp4 1920x1030 1080p 555k , avc1.640028, 30fps, video only, 6.16MiB
        299 mp4 1920x1030 1080p60 605k , avc1.64002a, 60fps, video only, 6.59MiB
        248 webm 1920x1030 1080p 680k , vp9, 30fps, video only, 7.21MiB
        303 webm 1920x1030 1080p60 849k , vp9, 60fps, video only, 8.52MiB
        271 webm 2560x1374 1440p 1464k , vp9, 30fps, video only, 14.98MiB
        308 webm 2560x1374 1440p60 1770k , vp9, 60fps, video only, 18.23MiB
        Not sure about Chromium, but Firefox uses some internal benchmark to determine if it can play VP9 fast enough (about:config → media.benchmark.vp9.threshold).
        andreano
        Senior Member
        Last edited by andreano; 03 March 2020, 03:44 PM.

        Comment


        • #74
          Originally posted by darkbasic View Post

          As far as I remember all 60 fps videos didn't have any high quality h264 version.
          I've just re-installed h264ify and enabled it, and looking at one of my videos it still uses vp9 for *all* the resolutions: https://www.youtube.com/watch?v=qBh6-Pd5Otw
          I don't know if the extension is broken or 60 fps is simply not supported, but I also remember not being able to watch most of the youtube videos at 60 fps with my early Talos ppc64le system which didn't have vp9 support compiled in.
          Code:
          $ youtube-dl -F qBh6-Pd5Otw
          [youtube] qBh6-Pd5Otw: Downloading webpage
          [youtube] qBh6-Pd5Otw: Downloading video info webpage
          [info] Available formats for qBh6-Pd5Otw:
          format code extension resolution note
          249 webm audio only tiny 58k , opus @ 50k (48000Hz), 944.16KiB
          250 webm audio only tiny 76k , opus @ 70k (48000Hz), 1.22MiB
          140 m4a audio only tiny 130k , m4a_dash container, [email protected] (44100Hz), 2.39MiB
          251 webm audio only tiny 152k , opus @160k (48000Hz), 2.42MiB
          160 mp4 256x138 144p 31k , avc1.4d400c, 30fps, video only, 421.86KiB
          278 webm 256x138 144p 43k , webm container, vp9, 30fps, video only, 571.20KiB
          242 webm 426x228 240p 54k , vp9, 30fps, video only, 735.05KiB
          133 mp4 426x228 240p 67k , avc1.4d4015, 30fps, video only, 815.12KiB
          243 webm 640x344 360p 103k , vp9, 30fps, video only, 1.25MiB
          134 mp4 640x344 360p 123k , avc1.4d401e, 30fps, video only, 1.37MiB
          244 webm 854x458 480p 174k , vp9, 30fps, video only, 2.05MiB
          135 mp4 854x458 480p 188k , avc1.4d401f, 30fps, video only, 2.02MiB
          136 mp4 1280x688 720p 328k , avc1.4d401f, 30fps, video only, 3.59MiB
          298 mp4 1280x688 720p60 354k , avc1.4d4020, 60fps, video only, 3.94MiB
          247 webm 1280x688 720p 359k , vp9, 30fps, video only, 3.96MiB
          302 webm 1280x688 720p60 452k , vp9, 60fps, video only, 4.78MiB
          137 mp4 1920x1030 1080p 555k , avc1.640028, 30fps, video only, 6.16MiB
          299 mp4 1920x1030 1080p60 605k , avc1.64002a, 60fps, video only, 6.59MiB
          248 webm 1920x1030 1080p 680k , vp9, 30fps, video only, 7.21MiB
          303 webm 1920x1030 1080p60 849k , vp9, 60fps, video only, 8.52MiB
          271 webm 2560x1374 1440p 1464k , vp9, 30fps, video only, 14.98MiB
          308 webm 2560x1374 1440p60 1770k , vp9, 60fps, video only, 18.23MiB
          18 mp4 640x344 360p 258k , avc1.42001E, [email protected] 96k (44100Hz), 4.77MiB
          22 mp4 1280x688 720p 322k , avc1.64001F, [email protected] (44100Hz) (best)
          Stupid forum software broke the layout, but you can still read the list and find that 1080p h264 is there, both 30fps (format 137) and 60fps (format 299).

          Comment


          • #75
            Originally posted by andre30correia View Post
            pipewire is alpha software yet, the point here is wayland is not ready for desktop multi use propose.
            Not sure what a "desktop multi use propose" is.
            I'm using Gnome/Wayland as main OS for work and it works without an issue (including remote desktop & ssh -X). On a multi-user production machine-learning box with Nvidia GPUs, I am switching between X and Gnome/Wayland. Gnome/Wayland + proprietary Nvidia driver also works but with limited multi-display support (blame Nvidia...).

            Not sure what the clinging onto X is about. X currently does not have a maintainer and causes a number of issues that are resolved but stuck in the devel tree.
            And btw, since when did X have an out-of-the-box production-ready remote desktop solution?

            Comment


            • #76
              Originally posted by treba View Post
              Anyhow, I don't need to convince you, I just don't want your IHMO badly informed comments to stand uncontested.
              Sorry I don't hear you over the sounds of Gnome is so cool it already implements everything. Wayland, despite being over 10 years old, doesn't provide any useful APIs for creating a rich DE which is why each DE must invent the wheel for the things which are available in X.org out the box. I.e. if you don't like Gnome or if you're an NVIDIA user, you're shit of out luck. That means IceWM, XFCE, failsafe DE, almost a dozen of other DEs for Linux are all ... dead in the water. Open Source is desperately lacking developers and instead of helping them, yeah, let's create a brand new graphics server which is unusable by itself. I mean in X.org you can run xdm/twm/xterm with all the required features working out of the box: clipboard: works, VNC: works, global shortcuts: work, window management and switching between applications: work. Under Wayland go write a compositor and a ton of hacks just to make everything work.What a nice proposition. Yeah, totally convincing. Year, your arguments are strong, I meant practically invalid if the user for some reasons doesn't like Gnome. I for one hate this DE and last used it in 2000 (that's not a mistake).

              Yeah, I'm totally unconvinced. We have a working graphics server which just works, and here people are going mad over something which still requires alpha-quality software to be considered complete over ten years of development. It's a joke... it's all a joke, mother forgive me - comedian.

              Again all the arguments in this topic boil down, you must use Gnome with Wayland or GTFO. I'm sorry, I will reply with: I'm not going to use brain-damaged Gnome any time soon. I will use anything but Gnome, even TWM.

              Comment


              • #77
                It's great to see Firefox providing WebGL and VA-API on Wayland! Before I can use Firefox Wayland, it needs copy & paste and window resizing working well on Plasma Wayland, these are the main issues for me right now.

                Comment


                • #78
                  Originally posted by birdie View Post
                  Sorry I don't hear you over the sounds of Gnome is so cool it already implements everything. Wayland, despite being over 10 years old, doesn't provide any useful APIs for creating a rich DE which is why each DE must invent the wheel for the things which are available in X.org out the box. I.e. if you don't like Gnome or if you're an NVIDIA user, you're shit of out luck. That means IceWM, XFCE, failsafe DE, almost a dozen of other DEs for Linux are all ... dead in the water. Open Source is desperately lacking developers and instead of helping them, yeah, let's create a brand new graphics server which is unusable by itself. I mean in X.org you can run xdm/twm/xterm with all the required features working out of the box: clipboard: works, VNC: works, global shortcuts: work, window management and switching between applications: work. Under Wayland go write a compositor and a ton of hacks just to make everything work.What a nice proposition. Yeah, totally convincing. Year, your arguments are strong, I meant practically invalid if the user for some reasons doesn't like Gnome. I for one hate this DE and last used it in 2000 (that's not a mistake).

                  Yeah, I'm totally unconvinced. We have a working graphics server which just works, and here people are going mad over something which still requires alpha-quality software to be considered complete over ten years of development. It's a joke... it's all a joke, mother forgive me - comedian.

                  Again all the arguments in this topic boil down, you must use Gnome with Wayland or GTFO. I'm sorry, I will reply with: I'm not going to use brain-damaged Gnome any time soon. I will use anything but Gnome, even TWM.
                  Its not Wayland's fault if your DE does not support it well. It's also not Vulkan's fault if your GPU driver (or game) does not support it.

                  If you don't like Gnome, you can enjoy wayland with sway. Good luck trying to convince the maintainer to support the proprietary Nvidia driver (that has more issues than just wayland support), ... it is not wayland's fault if Nvidia's driver don't support it ...

                  PS. Wayland libraries are not alpha quality for a long time now. Your DE on wayland may be but, again, it is not wayland's fault.....
                  mppix
                  Senior Member
                  Last edited by mppix; 03 March 2020, 04:38 PM.

                  Comment


                  • #79
                    All this rage...

                    And so many ...lets face it... stupid comments. Like this one:

                    It's broken, it doesn't support VP9!
                    Answer:
                    The effort is ongoing. We're the early birds here, we see the first results. The scope of efforts and codecs will be broadened soon. Do your homework, read the information, think. You just need to wait a little longer, not even that much.

                    Another thing:
                    I really don't think X11 will be supported by this. See stransky's blog from today:
                    https://mastransky.wordpress.com/202...on-on-wayland/

                    So X11 people will never get this, which makes sense to me, because X11 is a dead end. Hell, they don't even get bugfix releases out of the door anymore...

                    Comment


                    • #80
                      Originally posted by mppix View Post

                      Its not Wayland's fault if your DE does not support it well. It's also not Vulkan's fault if your GPU driver (or game) does not support it.

                      If you don't like Gnome, you can enjoy wayland with sway. Good luck trying to convince the maintainer to support Nvidia, ... it is not waylands fault if Nvidia GPUs don't support it ... (see above).
                      In open source it's always someone else's fault. I'm done with this "fruitful" discussion of something which was created solely for Gnome.

                      Let's just call Wayland, Gnome Graphics Server and be done with this. Too bad you cannot even say GTK Graphics Server because Firefox, based on GTK, is still barely functional under Wayland. LMAO.
                      birdie
                      Senior Member
                      Last edited by birdie; 03 March 2020, 04:36 PM.

                      Comment

                      Working...
                      X