Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
CasparCG Server vs HOMER
A side-by-side editorial comparison of CasparCG Server and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
CasparCG Server vs HOMER: at a glance
What is CasparCG Server?
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.
What is HOMER?
Homer's storage churn pauses long enough to ship a catalog backup CLI.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
CasparCG Server vs HOMER: editorial side-by-side
CasparCG Server
0.0MEETINGS
Broadcast playout server reaches for HDR and sets a hardware floor to get there
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
HOMER
5.0MEETINGS
Homer's storage churn pauses long enough to ship a catalog backup CLI.
◆ 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. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, 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. A backup and restore path for the catalog is the logical next admission that the catalog is the thing most likely to break, and shipping it inside another release rather than tagging it separately fits a project releasing several times a week. 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.
Alternatives to CasparCG Server and HOMER
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 HOMER.
mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
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
See all CasparCG Server alternatives → · See all HOMER alternatives →
Recent activity from CasparCG Server and HOMER
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3h agoHOMERCatalog backup/restore CLI ships; QoS axes follow dashboard timezone
- 1d agoHOMERNative compaction made safe for live catalogs; retention in hours
- 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
- 8mo agoCasparCG Server2.5.0 brings initial HDR, headless Linux and an AVX2 baseline ⚡
- 1y agoCasparCG Server2.4.3 clears crashes across FFmpeg, Decklink and HTML producers
- 1y agoCasparCG Server2.4.2 restores Decklink driver 14.3 compatibility
- 1y agoCasparCG Server2.4.1 fixes Decklink subregions, EXIF rotation and NDI source listing
- 2y agoCasparCG Server2.4.0 adds 8K and 4K DCI frames plus AMCP command batching
- 2y agoCasparCG Server2.4.0 RC1 preview of the 2.4 feature set
Frequently asked questions
What is the difference between CasparCG Server and HOMER?
They serve adjacent needs but don't currently overlap on shipped themes. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.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.
Is CasparCG Server better than HOMER?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.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.
What are the best alternatives to CasparCG Server?
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.
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.