Add a note in README explaining how to use this with Chrome #341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nerijus
reviewed
Dec 2, 2024
| Accelerated video decoding has been reported to work on Chrome version >= 129 with NVIDIA driver version >= 565.57.01. It might work on slightly older versions of | ||
| Chrome and/or NVIDIA driver, but glitches and bugs have been reported. | ||
|
|
||
| These flags should suffice: `--enable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks`. Note that the [direct backend](#direct-backend) must be used. |
There was a problem hiding this comment.
I use the following flags - --use-gl=angle --use-angle=vulkan --enable-features=VaapiOnNvidiaGPUs,AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecode,UseMultiPlaneFormatForHardwareVideo.
There was a problem hiding this comment.
Yes, but using Vulkan is not required (it has nothing to do with acceleration) and UseMultiPlaneFormatForHardwareVideo does nothing since 129 (it is the default).
There was a problem hiding this comment.
and AcceleratedVideoDecode?
There was a problem hiding this comment.
I believe that is redundant with AcceleratedVideoDecodeLinuxGL. I never had that flag enabled.
There was a problem hiding this comment.
what about VaapiIgnoreDriverChecks - is it needed? I don't use it and get C in nvidia-smi.
There was a problem hiding this comment.
It is required for some devices, and it can do no harm even if it's not needed - so it's better to include
|
doesn't seem to work for me EDIT: after testing, latest chromium seem to be working, but latest electron doesn't... |
============================== |
| Decoding : | |
| Decode h264 baseline : | 48x16 to 4096x4096 pixels |
| Decode h264 main : | 48x16 to 4096x4096 pixels |
| Decode h264 high : | 48x16 to 4096x4096 pixels |
| Decode vp9 profile0 : | 128x128 to 8192x8192 pixels |
| Decode vp9 profile2 : | 128x128 to 8192x8192 pixels |
| Decode hevc main : | 144x144 to 8192x8192 pixels |
| Decode hevc main 10 : | 144x144 to 8192x8192 pixels |
| Decode hevc main still-picture: | 144x144 to 8192x8192 pixels |
| Encoding : |
Log Messages
============
============
- [12171:12171:0204/202620.491978:WARNING:sandbox_linux.cc(430)] : InitializeSandbox() called with multiple threads in process gpu-process.
- [12171:12171:0204/202620.497426:WARNING:viz_main_impl.cc(85)] : VizNullHypothesis is disabled (not a warning)
- [12171:12424:0204/202635.548757:ERROR:vaapi_video_decoder.cc(1223)] : failed Initialize()ing the frame pool
Actually it's not working when playing a video
|
Does AV1 work for you with this? VP9 and H264 work great but AV1 uses CPU decode. Using a 4090 with 570.86.16 I tried chroium, ungoogled-chromium, and edge. |
I don't have a card that supports AV1, unfortunately. |
Yeah You can see successful hardware decode on a VP9 video with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Chrome is now widely reported to work, there is no need to pretend that it will not function, as long as we explain that the support is not official.