There are few options for NVIDIA users how to run it. It also correctly handles decoding of intermediate frames which is recent AMD NAVI2 bug ( Bug 1772028, Bug 1802844) so the playback is smooth and I haven’t seen any glitches or CPU usage peaks. Nvidia-vaapi-driver playback performance is similar to what I see on AMD/Intel. There’s a complete how-to for Firefox/NVIDIA/Fedora 37 available on Fedora wiki. That’s being worked on as Bug 1813500 and Bug 1787182. Broken graphics hardware may freeze whole browser on start or spread coredumps on every start. Next one is a bug in recent NVIDIA 525 driver series (which I got from rpmfusion) and I needed to use direct mode (whatever it is). Right now you need to disable the sanbox by MOZ_DISABLE_RDD_SANDBOX=1 env variable. It was adjusted by Mozilla folks for VA-API decode on Intel/AMD but NVIDIA needs some extra tweaks. Firefox runs media decode in extra process (RDD) which restricts where decoder can access. I think you also need a decently fresh NVIDIA drivers which supports DMABuf (which is used to transfer decoded images between Firefox processes and render them as GL textures). The driver translates VA-API calls from Firefox to VPDAU used by NVIDIA. Thanks to nvidia-vaapi-driver by Stephen “elFarto” Firefox may directly decode video on NVIDIA hardware. Both Wayland and X11 Gnome sessions popped up, Firefox picked up HW accelerated backend (WebRender) with DMABuf support so it’s time to check VA-API. I installed proprietary drivers from rpmfusion and to my surprise everything worked smoothly (except Atom on XWayland). Some time ago I got borrowed NVIDIA GeForce GTX 1070 from my employer (Red Hat) and I finally managed to put it to a workstation instead of my own AMD RX 6600 XT.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |