Plutonia
#1965
Replies: 1 comment
-
A huge thanks to everyone for this release! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Pion WebRTC v3.1.0 is now available. Pion WebRTC is a Go implementation of WebRTC. If you haven't used it before check out awesome-pion or example-webrtc-applications for what people are doing. We maintain a feature list and other helpful resources in our README.md
This release includes 170 commits from 36 authors. This release was primarily focused on adding features to improve media quality/experience and making it easier to scale with Pion.
New Features
Serve many PeerConnections with one UDP port
You can now serve all your PeerConnections with a single UDP port. This makes deploying and scaling in environment like Kubernetes easier.
Most WebRTC implementations (including Pion) will listen on a random UDP port for each remote peer.
To use this you create a
ICEUDPMux
and then share across all your PeerConnections via the SettingEngine. Your code will look like the following.This was implemented in d0a525.
FireFox Simulcast Support
We now support SSRC based Simulcast, before we only supported reading RID/MID from the RTP Extension Header as defined in ietf-mmusic-sdp-simulcast.
This was implemented in d570b7.
H265 Support
You can now packetize/depacketize H265. This allows you to read from a video file and send it over RTP, or the reverse.
This was implemented in 6cf5e9
Sender/Receiver Report
Sender/Receiver Reports are now enabled by default via pion/interceptor
This means that remote peers will now get metadata from Pion and be able to do things like Bandwidth Estimation.
No code changes are needed to use them, but if you wish to disable them create a PeerConnection without passing a
InterceptorRegisty that
RegisterDefaultInterceptors
has been called on. This can be useful if performance is criticalor you want to ship your own implementation.
This was implemented in bc3016
Transport Wide Congestion Control Feedback
Transport Wide Congestion Control Feedback is now enabled by default via pion/interceptor
This allows remote peers to perform even better Congestion Control over Receiver Reports.
No code changes are needed to use them, but if you wish to disable them create a PeerConnection without passing a
InterceptorRegisty that
RegisterDefaultInterceptors
has been called on. This can be useful if performance is criticalor you want to ship your own implementation.
This was implemented in c8a26a
This discussion was created from the release Plutonia.
Beta Was this translation helpful? Give feedback.
All reactions