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
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