Skip to content

feat: decode VP9 spatial layers with VA-API - #388

Merged
devopvoid merged 2 commits into
mainfrom
feat/vaapi-vp9-spatial-decode
Oct 16, 2026
Merged

devopvoid merged 2 commits into
mainfrom
feat/vaapi-vp9-spatial-decode

Conversation

@devopvoid

Copy link
Copy Markdown
Owner

Decodes VP9 spatial layers on Intel and AMD through VA-API, using WebRTC's layer sizes to split frames and retaining references across resolutions. Outputs the highest visible layer. Adds coverage for L2T2, L3T3 and L3T3_KEY; layer switching still needs dedicated coverage.

Use WebRTC's layer sizes to split spatial frames and retain references across resolutions. Covers L2T2, L3T3 and L3T3_KEY decoding.
@devopvoid
devopvoid merged commit 2405a22 into main Oct 16, 2026
14 checks passed
@devopvoid
devopvoid deleted the feat/vaapi-vp9-spatial-decode branch October 16, 2026 14:26
SendableMetatype added a commit to EduGeyser/webrtc-java that referenced this pull request Oct 18, 2026
Brings in the work upstream added from October 15 to 17: temporal
layers in the VA-API encoders and VP9 spatial layers in the VA-API
decoder (devopvoid#379 to devopvoid#381, devopvoid#383, devopvoid#388); a standalone voice activity
detector, and checks against using a disposed one (devopvoid#394); the removal
of Logging.logThreads (devopvoid#395); upstream's 0.20.0 release and its release
workflow changes (devopvoid#391 to devopvoid#393); and docs (devopvoid#378, devopvoid#382, devopvoid#384 to devopvoid#386,
devopvoid#389, devopvoid#390).

Fork-side adaptations:
- Logging keeps this fork's design, in which thread IDs and timestamps
  come from system properties read at load time. devopvoid#395's thread IDs that
  are always on and its runtime Logging.logTimestamps are left out. Its
  logging test change, which logs at INFO, is taken.
- The common WebRTC patches of devopvoid#394 are applied on every platform, as
  upstream does. The data channels desktop capture patch joins the patch
  list before it is recorded, so the build record covers it too.
- The data channels variant leaves out the standalone voice activity
  detector, and its test carries the media tag.
- The release workflow stays this fork's Gradle one. Upstream's
  Maven-based split into preparation and tag-scoped publication
  (release-publish.yml and the publish action) is left out, and so is
  its release notes link to jrtc.dev, which documents upstream's
  packages.
- The Maven files stay deleted, and the README and the docs' version
  stay this fork's own.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant