Skip to content

docs: list the hardware codecs in tables - #378

Merged
devopvoid merged 7 commits into
mainfrom
docs/hardware-codec-tables
Oct 15, 2026
Merged

devopvoid merged 7 commits into
mainfrom
docs/hardware-codec-tables

Conversation

@devopvoid

Copy link
Copy Markdown
Owner

Puts the hardware encoders and decoders per platform, interface and codec into tables, with what goes to software and what each interface needs.

Describes AV1 over VA-API, so it belongs after #376, #377 and the temporal layers PR.

@devopvoid
devopvoid merged commit 26f7532 into main Oct 15, 2026
10 checks passed
@devopvoid
devopvoid deleted the docs/hardware-codec-tables branch October 15, 2026 22:36
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