Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of Element Call and Red5 — release velocity, themes, recent moves, and the top alternatives to consider.
Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.
Element Call ships a release candidate roughly every two to three weeks. v0.28.1-rc.1 adds a breaking change that falls back to publishing media on a remote SFU when possible, supports migrating to new LiveKit transport types and endpoints, and fixes room v12 power-level compatibility. It also brings in a MatrixRTC SDK and patches several dependency security advisories. The previous rc added a quick audio menu and redacted analytics IDs from rageshakes.
Red5 ships constantly and explains almost none of it.
Red5 is a Java media server built around RTMP ingest and delivery. Releases come every few days — nine tags between early May and early July — but most publish nothing beyond an auto-generated link to the commit range. Two version schemes run side by side, with v2.0.16.46 appearing in July while the v2.0.3x series was still incrementing through June, so the tag number alone does not tell you which line a build belongs to.
Element Call ships a release candidate roughly every two to three weeks. v0.28.1-rc.1 adds a breaking change that falls back to publishing media on a remote SFU when possible, supports migrating to new LiveKit transport types and endpoints, and fixes room v12 power-level compatibility. It also brings in a MatrixRTC SDK and patches several dependency security advisories. The previous rc added a quick audio menu and redacted analytics IDs from rageshakes.
With the MatrixRTC protocol cutover finished in August, the team is now working on the media transport layer itself: how calls find and publish to SFUs and how LiveKit endpoints change underneath them. Packaging the RTC logic as an SDK suggests it is meant to be reused beyond the Element Call app.
Expect a 0.28.1 final and follow-ups to the LiveKit transport migration; whether the MatrixRTC SDK gets its own release isn't clear from the entries.
Red5 is a Java media server built around RTMP ingest and delivery. Releases come every few days — nine tags between early May and early July — but most publish nothing beyond an auto-generated link to the commit range. Two version schemes run side by side, with v2.0.16.46 appearing in July while the v2.0.3x series was still incrementing through June, so the tag number alone does not tell you which line a build belongs to.
Where changelogs do exist, the work is concentrated in the RTMP hot path: cutting CPU waste and allocation churn on ingest, then addressing thread oversubscription three releases later. The one capability addition visible in this window is AV1 support. Everything else that is described is dependency maintenance — Spring, Bouncy Castle — and build plumbing like on-demand Docker image pushes. The pattern is a small maintainer group optimising a mature server rather than repositioning it.
Expect the RTMP performance thread to continue and AV1 handling to be refined in follow-up releases. The undocumented releases make anything beyond that guesswork — the changelogs would need to carry content before a direction could be read from them.
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 Element Call or Red5.
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
HOMER 11.0.369 fixes S3 auth on Ceph-based storage and stops compaction memory growth.
JW Player moves CMAF VOD into the dashboard, adds AV1, and opens Broadcast Live to audio-only feeds.
rtpengine opens the mr26.3 branch with a rollback message and leaner call state.
Nextcloud Talk Desktop 2.3.3 adds accessibility options and bundles Talk v25.0.6.
Nextcloud Talk patches v22 and v23 while v25 stable sits five weeks past its last RC.
See all Element Call alternatives → · See all Red5 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Element Call is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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. Element Call is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Element Call alternatives in Meetings are ranked by recent ship velocity. Browse the "Element Call alternatives" section above for the current picks, or visit /alternatives/element-call for the full list with editorial commentary on each.
Top Red5 alternatives in Meetings are ranked by recent ship velocity. Browse the "Red5 alternatives" section above for the current picks, or visit /alternatives/red5 for the full list with editorial commentary on each.