-
Notifications
You must be signed in to change notification settings - Fork 14
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
Roadmap #28
Comments
Very interesting project! Would you consider supporting AV1 RTP encoding as well? |
@davydog187 of course! When it comes to the echo example we already support it! It's as easy as telling PeerConnection to negotiate AV1. Just change this line to: {:ok, pc} =
PeerConnection.start_link(
ice_servers: @ice_servers,
video_codecs: [
%RTPCodecParameters{
payload_type: 45,
mime_type: "video/AV1",
clock_rate: 90_000
}
]
) Besides this, we will of course add AV1 RTP payloader and depayloader so that you can pack/unpack AV1 into/from RTP packets 🙂 |
#33 also adds AV1 to the default video codecs |
This is really cool! How would this interact with Membrane Framework? |
@lovebes at some point we will wrap our |
Thanks for this, the code looks very friendly to use, like I work a lot with I will eventually port everything to Elixir as it seems like things are easier to manage here over |
Hi @ris-work! |
Thank you very much for the response! I will be eagerly waiting. Unfortunately, I am neither an expert in WebRTC nor Elixir (or SCTP/RTP), but thank you for considering it for an upcoming version! |
I am also excited to see this package developing so quickly. There are a couple use cases I have in mind that would depend on data channels. For one, it would be cool to deploy gaming app with elixir-desktop, where two peers could connect directly without an external signaling server. It's still early in my WebRTC journey, but if I can find time to support implementation, I'd be happy to do so. |
Hi guys, support for DataChannels just landed in version 0.5.0! We will publish a blog post next week but I wanted to let you know right now 🙂 |
And the blog post on data channels: https://blog.swmansion.com/data-channels-in-elixir-webrtc-0853c7d0e256 :) |
0.1.0 (01.2024)
Media reading/writing:
Media
module #53PeerConnection
API:add_track/2
function to API #38Documentation:
0.2.0 (04.2024)
RTCP related:
ICE features:
0.3.0 (07.2024)
UX improvements/features:
Configuration
#120Better logsIntegrations:
Fishjam:
Experimental WebRTC Endpoint using Elixir WebRTCBroadcaster improvements:
Client-side ICE restartsbroadcaster
to Phoenix apps#110.4.0 (08.2024)
Website
Broadcaster
RecordingsExWebRTC
:missing_rtcp_mux
when streaming to firefox #149:retransmit
#137UX
Introduction to Elixir WebRTC
tutorial #136 Further improvements toIntroduction to Elixir WebRTC
tutorial #1410.5.0 (09.2024)
0.6.0 (10.2024)
Others
If you have any questions or need help with a specific topic, please create a new discussion!
telemetryThe text was updated successfully, but these errors were encountered: