Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of rtpengine and Wowza — release velocity, themes, recent moves, and the top alternatives to consider.
rtpengine opens the mr26.3 branch with a rollback message and leaner call state.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Wowza is rebuilding around one idea: run computer vision inside the streaming pipeline.
Wowza's feed is a marketing blog, not a changelog — every entry is a short teaser ending in an ellipsis, with the substance behind the link. Read for direction rather than scope, it is almost entirely about the Video Intelligence Framework: object detection, scene analysis, vision-language models, synthetic video detection, and custom model support, all running on the same media server that ingests and delivers the stream. The one release-shaped item in this window remains NVIDIA's Synthetic Video Detector shipping as a VIF module; the newest post is a customer story rather than a capability.
Sipwise's rtpengine media proxy opened a new mr26.3 branch on October 19. Its first build, mr26.3.1.1, carries everything from mr26.2.1.5 plus a rollback NG control message, relaxed loop detection for duplicate packets arriving over a second apart or from endpoints no longer local, ICE agent teardown when a peer drops ICE, inject-audio mixing fixes, and a long run of "lightweight string" refactors across call IDs, tags, SDP and recording fields. Three days earlier, a hardening batch went to four branches, followed by compile-fix releases.
Development continues on two levels: correctness fixes backported across every supported branch, and newer work, such as the rollback message and memory-lighter call state, landing on the newest line. Opening mr26.3 adds a fifth maintained branch, so the backport load grows.
Expect mr26.3.1.x point builds and continued synchronized backports to mr12.5 through mr26.2. The entries don't show when older branches stop receiving fixes.
Wowza's feed is a marketing blog, not a changelog — every entry is a short teaser ending in an ellipsis, with the substance behind the link. Read for direction rather than scope, it is almost entirely about the Video Intelligence Framework: object detection, scene analysis, vision-language models, synthetic video detection, and custom model support, all running on the same media server that ingests and delivers the stream. The one release-shaped item in this window remains NVIDIA's Synthetic Video Detector shipping as a VIF module; the newest post is a customer story rather than a capability.
Wowza is repositioning from media server to inference point, and the marketing has shifted from explaining the idea to proving it. The earlier posts argued that analysis belongs inside the pipeline rather than in a second system downstream; the recent ones supply a named deployment — Oceaneering running VIF on live subsea ROV video — and press the installed base still on Streaming Engine 4.8 to upgrade. A reference account and upgrade pressure arriving together is what a vendor does when it is converting an existing base rather than chasing new ones.
With a named customer now published and upgrade pressure already applied, expect more vertical case studies in industrial and infrastructure monitoring rather than new VIF capability announcements. The teaser-only feed will not reveal VIF pricing or packaging.
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 rtpengine or Wowza.
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.
Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.
JW Player moves CMAF VOD into the dashboard, adds AV1, and opens Broadcast Live to audio-only feeds.
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 rtpengine alternatives → · See all Wowza alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Wowza is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Wowza is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 rtpengine alternatives in Meetings are ranked by recent ship velocity. Browse the "rtpengine alternatives" section above for the current picks, or visit /alternatives/rtpengine for the full list with editorial commentary on each.
Top Wowza alternatives in Meetings are ranked by recent ship velocity. Browse the "Wowza alternatives" section above for the current picks, or visit /alternatives/wowza for the full list with editorial commentary on each.