Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team around kevinvenalainen/allow create encoded streams #301

Merged
merged 6 commits into from
Jun 13, 2024

Conversation

ibc
Copy link
Member

@ibc ibc commented Jun 13, 2024

NOTE: No idea how I ended creating yet another branch. In theory I was pushing to PR #300...

Fixes #299

Allows calling clients to add sender and receiver callback functions which are executed synchronously after RTCRTPSender/Receiver creation. This feature is targeted to Chromium browsers and allows applications to call createEncodedStreams() in the callback functions in order to create WebRTC Encoded Transforms.

Example Usage

const consumer = await recvTransport.consume({
  xxxxx,
  xxxxx,
  onRtpReceiver: (receiver) => {
    const { readable, writable } = receiver.createEncodedStreams();
    readable.pipeTo(writable);
  }
});

@ibc ibc merged commit 9baf645 into v3 Jun 13, 2024
6 checks passed
@ibc ibc deleted the TeamAround-kevinvenalainen/allow-createEncodedStreams branch June 13, 2024 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Allow createEncodedStreams on PCs without encodedInsertableStreams parameter
2 participants