Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
Comparison · Meetings
HOMER vs mediasoup
A side-by-side editorial comparison of HOMER and mediasoup — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs mediasoup: at a glance
What is HOMER?
Homer's native compaction engine goes from do-not-touch to safe-to-try in one day.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. The last two entries tell one story: 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held, and explicitly told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog. Around that sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, an Arrow timestamp-unit fix, opt-in time-range routing, and two inline GHSA fixes hardening node /query auth.
What is mediasoup?
After weeks of one-line subchannel patches, mediasoup rebuilt its RTCP timing model.
The Rust line had been shipping single-PR point releases every few days, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. 0.26.0 breaks that pattern with a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when the media was actually captured. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison and fixes for an OOB write and an SCTP integer overflow.
HOMER vs mediasoup: editorial side-by-side
HOMER
5.0MEETINGS
Homer's native compaction engine goes from do-not-touch to safe-to-try in one day.
◆ Current state
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. The last two entries tell one story: 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held, and explicitly told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog. Around that sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, an Arrow timestamp-unit fix, opt-in time-range routing, and two inline GHSA fixes hardening node /query auth.
◆ Where it's heading
Homer is stabilizing a storage rewrite by moving work out of DuckDB rather than tuning it further. Native compaction merges in Go, outside DuckDB's memory_limit, and lets DuckLake alone allocate snapshot and file IDs — the exact behavior that corrupted catalogs before. The same instinct shows in the coordinator's smart routing, which avoids querying storage nodes that cannot hold the window, and in raising container memory ceilings rather than shrinking workloads. Defaults stay conservative while each escape hatch is proven.
◆ Prediction
If native compaction holds up in the field, expect it to become the default engine and the DuckDB compaction path to be deprecated; the near-term releases will likely keep closing memory and catalog-locking edges around it.
mediasoup
6.3MEETINGS
After weeks of one-line subchannel patches, mediasoup rebuilt its RTCP timing model.
◆ Current state
The Rust line had been shipping single-PR point releases every few days, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. 0.26.0 breaks that pattern with a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when the media was actually captured. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison and fixes for an OOB write and an SCTP integer overflow.
◆ Where it's heading
Two threads run through this window: finishing the subchannel mechanism so pipe transports behave like direct ones, and tightening timing correctness in the media path. The new RemoteClockOffsetEstimator and RemoteCaptureTimeEstimator classes, plus abs-capture-time rewriting in the simulcast manager, are foundations rather than endpoints — they give the worker a notion of remote capture instants it did not previously have. Expect that foundation to be used by more than Sender Reports.
◆ Prediction
The capture-time estimators look like groundwork for synchronization and delay features beyond Sender Reports; the near-term releases will likely be fixes shaking out the new timing path across simulcast and pipe transports.
Alternatives to HOMER and mediasoup
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 HOMER or mediasoup.
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.
Muvi
Muvi cleared SOC 2 and immediately turned it into the centerpiece of its enterprise pitch.
See all HOMER alternatives → · See all mediasoup alternatives →
Recent activity from HOMER and mediasoup
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoHOMERNative compaction made safe for live catalogs; retention in hours
- 1d agomediasoupmediasoup rebuilds RTCP Sender Reports around media capture time ⚡
- 2d agoHOMERCompaction merge bounded after silent OOM kills on live catalogs
- 4d agoHOMERAlerts store the firing query and replay it in search
- 5d agoHOMERDuckDB memory caps raised so high ingest stops killing the engine
- 5d agoHOMERPer-user dashboard IDs unblock multi-user installs
- 6d agoHOMERFlightSQL timestamp units fixed after captures displayed as 1882
- 8d agomediasoupmediasoup verifies DataConsumer subchannels before cloning
- 12d agomediasoupmediasoup stops checking ignoredSubchannel on piped DataConsumers
- 15d agomediasoupmediasoup adds ignored_subchannel to DirectDataProducer.send
- 19d agomediasoupmediasoup makes DataProducerOptions::new_pipe_transport public
- 20d agomediasoupmediasoup handles subchannels in pipe DataConsumers
Frequently asked questions
What is the difference between HOMER and mediasoup?
They serve adjacent needs but don't currently overlap on shipped themes. mediasoup 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 HOMER better than mediasoup?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mediasoup 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 HOMER?
Top HOMER alternatives in Meetings are ranked by recent ship velocity. Browse the "HOMER alternatives" section above for the current picks, or visit /alternatives/homer-voip for the full list with editorial commentary on each.
What are the best alternatives to mediasoup?
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.