coturn
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
A side-by-side editorial comparison of JW Player and rtpengine — release velocity, themes, recent moves, and the top alternatives to consider.
JW Player is rebuilding its VOD pipeline around CMAF, one workflow fix at a time
JW Player's releases split between the CMAF VOD pipeline (automatic renditions, duration-scaled seek thumbnails, in-place source re-uploads) and player and SDK work on captions, accessibility, casting and display options. The latest entry makes Motion Thumbnails a per-player setting. Ad-serving analytics gained content and placement dimensions twice in six weeks.
rtpengine backports the same DTLS and socket fixes across four maintenance branches at once.
Sipwise's rtpengine media proxy is maintaining several release lines in parallel (mr13.5, mr14.1, mr26.0, mr26.1, mr26.2), and most recent entries are coordinated backports. The September 16 batch fixes hash-table updates, nested string lookups and stop_forwarding mixups across four branches, and adds DTLS negotiation corrections (setup=actpass logic, ignoring incorrect DTLS=passive, keeping TLS IDs on answer role changes) to the mr26.0 and mr26.1 lines.
JW Player's releases split between the CMAF VOD pipeline (automatic renditions, duration-scaled seek thumbnails, in-place source re-uploads) and player and SDK work on captions, accessibility, casting and display options. The latest entry makes Motion Thumbnails a per-player setting. Ad-serving analytics gained content and placement dimensions twice in six weeks.
The CMAF workflow is being brought to parity with the legacy pipeline feature by feature, which points to a migration of publishers onto it. In parallel, player UX settings, SDKs and analytics are tuned for publishers who monetize through ads and need fine control over how players present content.
More CMAF VOD parity features are the likeliest next releases, possibly followed by a deprecation notice for the older pipeline; the entries don't yet signal a date.
Sipwise's rtpengine media proxy is maintaining several release lines in parallel (mr13.5, mr14.1, mr26.0, mr26.1, mr26.2), and most recent entries are coordinated backports. The September 16 batch fixes hash-table updates, nested string lookups and stop_forwarding mixups across four branches, and adds DTLS negotiation corrections (setup=actpass logic, ignoring incorrect DTLS=passive, keeping TLS IDs on answer role changes) to the mr26.0 and mr26.1 lines.
The work is focused on correctness in media negotiation, especially DTLS role handling and ICE on closed sockets, rather than new features. The newest branch, mr26.2, also brought AMR fmtp defaults, mirroring of generated RTCP sender reports to Homer, and recording cleanup hardening, which points to better interop and observability for carrier deployments.
More synchronized backport releases across the mr13.5 through mr26.2 lines are the clear pattern; feature work will most likely keep landing on mr26.2 first.
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 JW Player or rtpengine.
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
OpenSIPS 4.0 is in release-candidate testing, with two RCs a month apart.
Kamailio's tracked feed shows one thing: a quiet, schema-stable 5.8 maintenance release.
Restream's webinars get a registration page and a CSV of leads, turning broadcasts into a pipeline
BigBlueButton 4.0 rc.4 is a security-only release as the LiveKit stack hardens.
Fourwaves is polishing participant messaging after a pricing reset.
See all JW Player alternatives → · See all rtpengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. JW Player and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. JW Player and rtpengine are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top JW Player alternatives in Meetings are ranked by recent ship velocity. Browse the "JW Player alternatives" section above for the current picks, or visit /alternatives/jwplayer for the full list with editorial commentary on each.
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.