Repository navigation
feat: encoded frame transforms in the client API - #481
Merged
Merged
Conversation
PeerOptions take a send and a receive transform, set on each sender before negotiation and on each receiver before onTrack. Sender.transform and RemoteTrack.transform replace them for one sender or track. EncryptedRecordingExample now uses the client API.
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.
PeerOptions take a send and a receive transform. The peer sets them on each sender before negotiation and on each receiver before onTrack hands out the track, so they are in place from the first frame. Sender.transform and RemoteTrack.transform replace them for one sender or track. A frame a transform throws on is dropped, and the first failure goes to the peer's onError handlers.
EncryptedRecordingExample now uses the client API.