Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
A side-by-side editorial comparison of CasparCG Server and mediasoup — release velocity, themes, recent moves, and the top alternatives to consider.
Broadcast playout server reaches for HDR and sets a hardware floor to get there
CasparCG Server ships stable releases roughly once or twice a year, with long RC and beta runs ahead of each major. The 2.4 line delivered resolution and control-surface breadth — 8K and 4K DCI frames, custom resolutions, an interlaced mixer pipeline for field accuracy, AMCP command batching. The current 2.5.0 stable turns to colour and deployment: initial HDR support, ffmpeg 7.0, headless Linux operation, and Ubuntu deb packaging.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
The Rust line spent most of this window on single-PR point releases, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. That pattern broke with 0.26.0, a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when media was captured. 0.27.0 continues in the media path with a breaking change limiting simulcast and SVC to the preferred temporal layer. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison plus fixes for an OOB write and an SCTP integer overflow.
CasparCG Server ships stable releases roughly once or twice a year, with long RC and beta runs ahead of each major. The 2.4 line delivered resolution and control-surface breadth — 8K and 4K DCI frames, custom resolutions, an interlaced mixer pipeline for field accuracy, AMCP command batching. The current 2.5.0 stable turns to colour and deployment: initial HDR support, ffmpeg 7.0, headless Linux operation, and Ubuntu deb packaging.
The project is modernizing the parts of a playout server that determine whether it can sit in a current broadcast chain — colour pipeline, pixel format fidelity, and where it can run. That comes with an explicit hardware bargain: AVX2 is recommended now and becomes a requirement in 2.6, trading compatibility with pre-2013 CPUs for the instruction set HDR and the embedded Chrome renderer need. Alongside, Decklink and NDI integration keep absorbing steady fix work.
2.6 should complete the AVX2 transition and widen HDR beyond the current subset of producers and consumers, since the 2.5 notes describe HDR as deliberately partial.
The Rust line spent most of this window on single-PR point releases, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. That pattern broke with 0.26.0, a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when media was captured. 0.27.0 continues in the media path with a breaking change limiting simulcast and SVC to the preferred temporal layer. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison plus fixes for an OOB write and an SCTP integer overflow.
The subchannel thread that dominated July has gone quiet and the media path has taken over. First timing correctness — RemoteClockOffsetEstimator and RemoteCaptureTimeEstimator gave the worker a notion of remote capture instants it did not previously have — and now layer selection, with 0.27.0 constraining which temporal layer simulcast and SVC will actually deliver. Both are behavior changes in what an SFU sends downstream rather than additions to its API surface, and 0.27.0 is labelled breaking, so integrators are being asked to absorb them.
With two consecutive releases changing media-path behavior, the near-term releases are likely to be corrections shaking out the new timing and layer-selection paths across simulcast and pipe transports. The capture-time estimators remain unused beyond Sender Reports, which leaves them the obvious foundation for further synchronization work.
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 CasparCG Server or mediasoup.
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Homer's storage churn pauses long enough to ship a catalog backup CLI.
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
See all CasparCG Server alternatives → · See all mediasoup alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mediasoup is currently shipping more aggressively (velocity 6.3 vs 0.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mediasoup is currently shipping more aggressively (velocity 6.3 vs 0.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.
Top CasparCG Server alternatives in Meetings are ranked by recent ship velocity. Browse the "CasparCG Server alternatives" section above for the current picks, or visit /alternatives/casparcg-server for the full list with editorial commentary on each.
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.