Skip to content

feat: send encoded frames through RTP sender injectors - #365

Merged
devopvoid merged 1 commit into
fix/network-thread-observersfrom
feat/encoded-frame-injectors
Oct 13, 2026
Merged

devopvoid merged 1 commit into
fix/network-thread-observersfrom
feat/encoded-frame-injectors

Conversation

@devopvoid

Copy link
Copy Markdown
Owner

Wraps WebRTC's encoded frame injectors (new in M155), which send frames that are already encoded in place of a sender's track.

  • RTCRtpSender.createEncodedVideoFrameInjector(...) / createEncodedAudioFrameInjector(...), with observers for key frame requests and bitrate changes, called on the callback thread from fix: call network thread observers on a callback thread #364.
  • RTCPeerConnection.addTransceiver(MediaType, init) for senders without a track.
  • WebRTC's frame factory is outside its default build, so the CMake build now builds and links a list of extra targets; an existing WebRTC install rebuilds once.
  • A section on injectors in the encoded transforms guide.

Stacked on #364.

Wraps WebRTC's encoded video and audio frame injectors, which send frames that are already encoded in place of a sender's track, and adds RTCPeerConnection.addTransceiver(MediaType, init) for senders without one. The frame factory they use is outside WebRTC's default build, so it is built and linked as an extra target.
@devopvoid
devopvoid added this pull request to stack #367 October 13, 2026 21:36
@devopvoid
devopvoid merged commit bc03153 into main Oct 13, 2026
25 checks passed
@devopvoid
devopvoid deleted the feat/encoded-frame-injectors branch October 13, 2026 22:35
SendableMetatype added a commit to EduGeyser/webrtc-java that referenced this pull request Oct 15, 2026
Brings in the work upstream added from October 11 to 15: hardware video
codecs on every platform, through Media Foundation, VideoToolbox, VA-API
and NVDEC, with WebRTC built with H.265 (devopvoid#346 to devopvoid#348, devopvoid#352, devopvoid#353, devopvoid#356,
devopvoid#359, devopvoid#371 to devopvoid#377); HEVC and AV1 decoding in the media player, with
dav1d and Vulkan Video (devopvoid#331, devopvoid#345); encoded frame injectors (devopvoid#365);
receiver source changes and audio packet infos (devopvoid#366); audio codec
factories (devopvoid#340); network thread observers called on a callback thread
(devopvoid#364); screen capture with ScreenCaptureKit (devopvoid#354); Windows audio
devices that mix more than two channels (devopvoid#358); autoninja (devopvoid#357); and
the release channels of the docs site (devopvoid#361).

Fork-side adaptations:
- The factory keeps the CreatePeerConnectionFactory overload without a
  worker thread, and still switches device capture on the network
  thread. devopvoid#355 copies WebRTC's factory setup and has the audio module
  learn a worker thread, which only matters for a worker thread distinct
  from the network thread, and WebRTC is removing those. The audio codec
  factories and hardware codec switches of devopvoid#340 and devopvoid#359 go to that
  overload.
- WebRTC stays on a commit on main, so the move to branch 8059 (devopvoid#360)
  and its fixed clang package are left out.
- The data channels variant builds WebRTC without H.265 and without the
  extra targets, leaves out the audio codec factory bindings and
  addTransceiverOfType, and skips the new tests that need audio or
  video.
- dav1d is built against the sysroot on native Linux builds as well, as
  FFmpeg is. CI installs Meson for the full variant only, checks out the
  dav1d submodule, and adds its commit to the FFmpeg cache key. The
  fork's Windows SDK step stays, without upstream's second one.
- The release workflow records the docs' version in the tagged commit,
  as upstream's now does. The docs site still builds from main, since
  this fork publishes none.
- The Maven files stay deleted: Jetty is bumped in the version catalog,
  and the docs lockfile takes upstream's bumps on top of the fork's
  newer VitePress.
- The media module's README builds with Gradle.
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