Add experimental NVENC-backed VA-API encode support - #438
Open
ntoskrnl7 wants to merge 11 commits into
Open
Conversation
This file contains hidden or 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
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.
Summary
This PR adds experimental VA-API encode support backed by NVENC while keeping the existing decode-focused behavior intact.
The new encode path exposes
VAEntrypointEncSliceonly after runtime NVENC capability probing, so the advertised profiles should match the target GPU, driver, and NVENC API support.What changed
vainfoandffmpeg.Limitations
This is intentionally experimental and aimed at transcoding-style workloads.
ntoskrnl7/chrome-vaapi-hotpatch; this PR does not make stock Chrome use the driver by itself.Testing
Tested with:
meson testvainfo --display drm --device /dev/dri/renderD128ffmpegVA-API encode/decode checks for H.264 and HEVCdriver-runtime-vaapi-smokeReference validation documented in the README: