Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
A side-by-side editorial comparison of mediasoup and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
After weeks of one-line subchannel patches, mediasoup rebuilt its RTCP timing model.
The Rust line had been shipping single-PR point releases every few days, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. 0.26.0 breaks that pattern with a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when the media was actually captured. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison and fixes for an OOB write and an SCTP integer overflow.
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.
The Rust line had been shipping single-PR point releases every few days, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. 0.26.0 breaks that pattern with a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when the media was actually captured. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison and fixes for an OOB write and an SCTP integer overflow.
Two threads run through this window: finishing the subchannel mechanism so pipe transports behave like direct ones, and tightening timing correctness in the media path. The new RemoteClockOffsetEstimator and RemoteCaptureTimeEstimator classes, plus abs-capture-time rewriting in the simulcast manager, are foundations rather than endpoints — they give the worker a notion of remote capture instants it did not previously have. Expect that foundation to be used by more than Sender Reports.
The capture-time estimators look like groundwork for synchronization and delay features beyond Sender Reports; the near-term releases will likely be fixes shaking out the new timing path across simulcast and pipe transports.
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 mediasoup or SRS.
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.
Muvi cleared SOC 2 and immediately turned it into the centerpiece of its enterprise pitch.
See all mediasoup alternatives → · See all SRS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — webrtc — within Meetings. mediasoup and SRS are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. mediasoup and SRS are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top mediasoup alternatives in Meetings are ranked by recent ship velocity. Browse the "mediasoup alternatives" section above for the current picks, or visit /alternatives/mediasoup 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.