mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
A side-by-side editorial comparison of Jitsi and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
Jitsi rebuilds its transcription stack and keeps investing in large-call performance.
Jitsi (Jitsi Meet plus its open-source backend) is an engineering-led project whose blog doubles as its changelog. Recent posts mix genuine infrastructure work, a rebuilt transcription architecture, receiver audio subscriptions, AV1 codec adoption, with community items like Google Summer of Code cohorts.
SRS opens a 7.0 line built on a Go proxy tier, and drops features it no longer wants to carry.
SRS shipped the stable 6.0 line's first release on 12 August and, three hours later, the first development build of 7.0. The 6.0 line is now in pure maintenance — the r1 changelog is seven merges of DVR, WebRTC and edge fixes. Everything new is in 7.0-d0: RTSP playback, RTMPS, IPv6 across every protocol, HEVC in both directions between RTMP and WebRTC, and HLS fMP4 segments for HEVC and LL-HLS.
Jitsi (Jitsi Meet plus its open-source backend) is an engineering-led project whose blog doubles as its changelog. Recent posts mix genuine infrastructure work, a rebuilt transcription architecture, receiver audio subscriptions, AV1 codec adoption, with community items like Google Summer of Code cohorts.
The technical arc is toward scaling and modernizing the media stack: selective audio subscriptions, SSRC rewriting, AV1, and now a from-scratch transcription architecture replacing the decade-old Jigasi approach. Jitsi is steadily shedding legacy components in favor of architecture that handles large calls and real-time features more efficiently.
The new transcription architecture likely lands broader real-time features (live captions, translation hooks) over the coming releases; expect continued media-pipeline optimization for large meetings.
SRS shipped the stable 6.0 line's first release on 12 August and, three hours later, the first development build of 7.0. The 6.0 line is now in pure maintenance — the r1 changelog is seven merges of DVR, WebRTC and edge fixes. Everything new is in 7.0-d0: RTSP playback, RTMPS, IPv6 across every protocol, HEVC in both directions between RTMP and WebRTC, and HLS fMP4 segments for HEVC and LL-HLS.
The project is trading breadth of legacy surface for a narrower, better-covered core. 7.0-d0 removes the embedded GB28181 SIP server, multi-threading, Cygwin, and most configuration hot reload, while introducing a Go proxy server and origin-cluster architecture alongside the C++ media core. Protocol coverage keeps generalizing — each release makes a codec or an address family a property of the server rather than of one delivery path.
Expect the 7.0 line to run a long alpha and beta train the way 6.0 did, with the Go proxy and origin clustering carrying most of the remaining work and 6.0 continuing to receive backported fixes in parallel.
Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Jitsi or SRS.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Every manual control Mux ships now arrives with a Robots workflow that does it for you
WebinarJam's feed is a funnel-marketing curriculum with no product releases in it.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — webrtc — within Meetings. SRS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. SRS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top Jitsi alternatives in Meetings are ranked by recent ship velocity. Browse the "Jitsi alternatives" section above for the current picks, or visit /alternatives/jitsi for the full list with editorial commentary on each.
Top SRS alternatives in Meetings are ranked by recent ship velocity. Browse the "SRS alternatives" section above for the current picks, or visit /alternatives/srs for the full list with editorial commentary on each.