mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Comparison · Meetings
Fourwaves vs SRS
A side-by-side editorial comparison of Fourwaves and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
Fourwaves vs SRS: at a glance
What is Fourwaves?
Fourwaves is quietly building out the payments layer under its conference admin tools.
Fourwaves publishes a near-daily, one-line changelog covering small changes to the conference organiser's admin surface. The August window is dominated by payments and money administration: transaction filtering by organisation and by payment gateway, the Free plan surfaced in the upgrade checkout, and now Authorize.net added as a supported processor. Around that sits a steady thread of attendee-facing clarity work — a sidebar showing existing form entries, Tracks usable as an email variable — and routine fixes.
What is SRS?
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.
Fourwaves vs SRS: editorial side-by-side
Fourwaves
5.0MEETINGS
Fourwaves is quietly building out the payments layer under its conference admin tools.
◆ Current state
Fourwaves publishes a near-daily, one-line changelog covering small changes to the conference organiser's admin surface. The August window is dominated by payments and money administration: transaction filtering by organisation and by payment gateway, the Free plan surfaced in the upgrade checkout, and now Authorize.net added as a supported processor. Around that sits a steady thread of attendee-facing clarity work — a sidebar showing existing form entries, Tracks usable as an email variable — and routine fixes.
◆ Where it's heading
The work is aimed at multi-event organisations rather than single-conference organisers; transaction filtering and a second payment processor only matter if you run several events through shared gateways. Adding Authorize.net alongside the existing gateway support turns payments from a fixed part of the platform into something an organisation can choose, which is the prerequisite for selling to institutions that already have a processor relationship. Individually each change is minor; together they describe a platform being made to hold more events per customer.
◆ Prediction
Expect the payments thread to continue — further gateway options or per-organisation payment configuration are the natural next step now that transactions can be filtered by gateway. The date-stamped daily format suggests the cadence holds regardless of the size of what ships.
SRS
6.3MEETINGS
SRS opens a 7.0 line built on a Go proxy tier, and drops features it no longer wants to carry.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Fourwaves and SRS
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 Fourwaves or SRS.
Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Mux
Every manual control Mux ships now arrives with a Robots workflow that does it for you
WebinarJam
WebinarJam's feed is a funnel-marketing curriculum with no product releases in it.
See all Fourwaves alternatives → · See all SRS alternatives →
Recent activity from Fourwaves and SRS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6d agoFourwavesAuthorize.net added as a payment processor
- 6d agoSRSSRS 7.0-d0: Go proxy tier, RTSP playback, IPv6 across protocols ⚡
- 6d agoSRS6.0-r1: DVR, WebRTC and edge fixes on the stable line
- 7d agoFourwavesFree plan shown as a card in upgrade checkout
- 8d agoFourwavesTracks field usable as a confirmation-email variable
- 9d agoFourwavesFix: Website section shown to program chairs
- 13d agoFourwavesSidebar shows attendees their existing form entries
- 14d agoFourwavesFilter transactions by payment gateway
- 8mo agoSRSSRS 6.0 goes stable with H.265 across RTMP, HLS, TS and SRT ⚡
- 9mo agoSRS6.0-b3: use-after-free and HLS cleanup fixes
- 10mo agoSRS6.0-b2: configurable SRT stream IDs and a WHIP transcoding fix
- 11mo agoSRS6.0-b1: RTC crash fixes, Windows binary dropped
Frequently asked questions
What is the difference between Fourwaves and SRS?
They serve adjacent needs but don't currently overlap on shipped themes. 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.
Is Fourwaves better than SRS?
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.
What are the best alternatives to Fourwaves?
Top Fourwaves alternatives in Meetings are ranked by recent ship velocity. Browse the "Fourwaves alternatives" section above for the current picks, or visit /alternatives/fourwaves for the full list with editorial commentary on each.
What are the best alternatives to SRS?
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.