Repository navigation
vp8: reconstruct frame headers from VA-API parameters - #469
Merged
Merged
Conversation
Prepared from local commits: aa1b571.
donbernhardo
marked this pull request as ready for review
September 30, 2026 20:50
Owner
|
Thanks for the patch, I was never happy with that hack but VP8 just isn't used that much now. |
yevhen-sychov
pushed a commit
to yevhen-sychov/nvidia-vaapi-driver
that referenced
this pull request
Oct 1, 2026
Brings in upstream elFarto#469 (vp8: reconstruct frame headers from VA-API parameters) and elFarto#460 (AV1 frames smaller than the sequence maximum). Conflict resolution: - src/vp8.c: take upstream. It rebuilds the same uncompressed data chunk this branch already synthesized, and adds slice bounds checking and a guard for slice data without slice parameters. - src/vabackend.c: keep the NVENC coded-buffer path; drop this branch's VP8 note and the always-zero offset in favour of upstream's equivalent. - meson.build: keep this branch's test block, which already registers av1_frame_size_override; upstream's standalone registration would duplicate the test name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yevhen-sychov
added a commit
to yevhen-sychov/nvidia-vaapi-driver
that referenced
this pull request
Oct 1, 2026
Brings in upstream elFarto#469 (vp8: reconstruct frame headers from VA-API parameters) and elFarto#460 (AV1 frames smaller than the sequence maximum). Conflict resolution: - src/vp8.c: take upstream. It rebuilds the same uncompressed data chunk this branch already synthesized, and adds slice bounds checking and a guard for slice data without slice parameters. - src/vabackend.c: keep the NVENC coded-buffer path; drop this branch's VP8 note and the always-zero offset in favour of upstream's equivalent. - meson.build: keep this branch's test block, which already registers av1_frame_size_override; upstream's standalone registration would duplicate the test name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
You"re welcome! I think as long as we have NVDEC hardware fixed-function pipelines in our GPUs for these codecs, we might as well have a driver that makes them accessible ;) |
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.
vp8: reconstruct frame headers from VA-API parametersVP8 decoding can return a frozen image while reporting success. The driver attempts to recover the frame header by reading before the client's slice-data pointer and also extends slice reads beyond the copied data.
This change reconstructs the VP8 frame tag and key-frame header from the VA-API picture and slice parameters, then appends the submitted partition data. It removes the alignment-based read before the client buffer and checks slice ranges before copying.
Reproduce and verify
Requires:
libvpx/dev/dri/renderD128Build the driver and run the following commands from the repository root. Repeat the test in the unpatched and patched checkouts, each using its own build directory.
Verified on an RTX 3070:
f77ef1c): hardware output differs from the software reference.cmpproduces no output and exits with status0.31,104,000bytes each. Frame count alone does not detect the bug.Additional validation
The Meson/Ninja build succeeds.
A separate 90-frame VP8 clip and a 90-frame H.264 control also match software decode byte-for-byte.