-
Notifications
You must be signed in to change notification settings - Fork 209
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
Would pion/interceptor be useful? Anything I can change/add #19
Comments
hello @Sean-Der, of course i'm willing to contribute to the project, especially since the RTCP part is missing from pion/webrtc and at the same time is essential in SFUs in order to tune the bitrate, my only problem is lack of time :) Anyway, i already did a research work about webrtc and RTCP for a commercial project, and it involved
The biggest difference between the RTCP implementation of this project and the one fit for pion/webrtc is that mine doesn't parse RTCP/RTP packets for performance reasons - therefore at the moment they cannot share a common library, but it's not a big deal and i already have a version fit for the pion/webrtc. What is missing is
Therefore i will publish as soon as i can. |
awesome! Another great one will be statistics. I am going to write an interceptor that feeds Thanks for the optimism. It is really great to have other projects doing RTC in Go, feels like momentum is growing |
moved here #22 |
This issue is being locked automatically because it has been closed for more than 6 months. |
Hey @aler9
I just finished up the README/examples for https://github.com/pion/interceptor and wanted to see if I could convince you to get involved :)
I want to be re-usable RTP/RTCP infrastructure we can work together on. You can opt in/out of different interceptors and then we could benefit from each others work! I am also hopeful this will kickstart other RTP/RTCP based projects in go. The overlap I see is.
The text was updated successfully, but these errors were encountered: