We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The examples won't work as written for more than one sender:
const rtpTransport = pc.createRtpTransport(); pc.getSenders().forEach((sender) => { pc.createEncodedStreams().readable. pipeThrough(createPacketizingTransformer()).pipeTo(rtpTransport.writable); });
...because multiple streams cannot be piped into a single writable.
It's not super-clear what a single "transport" is meant to be scoped to.
Is it just a packetizer sink? — In #14 I end up with number 4.
Conceptually, is this just be some option on a transform to change expected inputs and outputs? E.g. on the sender:
If so, this proposal may be closer to @alvestrand's than I previously appreciated.
The text was updated successfully, but these errors were encountered:
The example has multiple problems:
So there is a lot to fix.
Sorry, something went wrong.
Piping multiple streams into a single writable
03ce242
Fix for #15
This issue was mentioned in WEBRTCWG-2023-12-05 (Page 62)
aboba
No branches or pull requests
The examples won't work as written for more than one sender:
...because multiple streams cannot be piped into a single writable.
It's not super-clear what a single "transport" is meant to be scoped to.
Is it just a packetizer sink? — In #14 I end up with number 4.
Conceptually, is this just be some option on a transform to change expected inputs and outputs? E.g. on the sender:
If so, this proposal may be closer to @alvestrand's than I previously appreciated.
The text was updated successfully, but these errors were encountered: