webrtc
webrtc copied to clipboard
webrtc-rs
A pure Rust implementation of WebRTC
…value (#226)" This reverts commit 823c3f80f13b40a7454efebc8f40ddbc04c24099. As pointed out in [the original PR](https://github.com/webrtc-rs/webrtc/pull/226#issuecomment-1202028922), this commit broke the API guarantees we had before. I don't think I have time right now...
hi This is a bug similar to bug 195, the out come is udp port not closing. It seems when I try to deploy a TURN server, the candidate would...
The feasibility of replacing google libwebrtc with webrtc-rs, We need to port several key modules of libwebrtc, NetEQ, audio 3A(AEC, AGC, NS), audio/video codec, and other parts that can be...
webrtc-rs is currently almost a line-by-line port of [Pion](https://github.com/pion/webrtc). Pion is written in Go, a garbage collected language, and this causes some awkwardness for webrtc-rs both internally and externally (API-wise)....
Hiiiii! ^^ Does Webrtc-rs supports [Pipewire](https://pipewire.org/)? It's required on Linux because of security requirements implemented on Wayland and Flatpak. Thanks!!
### Problem I experimented with setting transceivers to sendonly like this: ```rust for transceiver in peer_connection_offer.get_transceivers().await { transceiver.set_direction(RTCRtpTransceiverDirection::Sendonly).await; } ``` I do the necessary renegotiation, but (for simplicity) i have...
Currently many API surfaces related to RTP support reading both parsed RTP packets and raw RTP data. This complicates the API surface and means that interceptors often have to redundantly...
This PR implements inbound and outbound RTP stats according to the [specification](https://www.w3.org/TR/webrtc-stats/), with some limitations. ## Todo - [x] Inbound RTP - [x] Outbound RTP - [ ] Tests ##...
When running against chromium the following message appears: ``` Buffer too small (16 bytes) to fit a FeedbackPacket. Minimum size = 18 ``` It is caused by the chromium code...
The [Perfect Negotiation](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Perfect_negotiation) document says that the set local description method shouldn't receive a argument for a perfect negotiation. Is this feature already on the roadmap?
