← Back to home
Comparison · DevOps

Liquidsoap vs Manticore Search

A side-by-side editorial comparison of Liquidsoap and Manticore Search — release velocity, themes, recent moves, and the top alternatives to consider.

Liquidsoap vs Manticore Search: at a glance

FeatureLiquidsoapManticore Search
SectorDevOpsDevOps
Velocity score6.35.0
Sparks · 30d00
Top themesaudio-streaming, subtitles, icecast, ocamlsearch-engine, open-source, sql, performance
Last editorial update2mo ago2d ago
WebsiteVisit →Visit →

What is Liquidsoap?

Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own

The 2.5.x rolling release carries the accumulated 2.5.0 changelog, and it is the largest body of work Liquidsoap has staged in over a year. Subtitles become a dedicated content type alongside audio and video, with native SRT decoding, FFmpeg subtitle encode and decode, bitmap passthrough, callbacks, transformations and dynamic insertion. An Icecast-compatible server ships as icecast.server, with source authentication, mount points, relay and per-listener encoding. Underneath, the source composition model was rewritten: switch, fallback, rotate and random drop their parallel list parameters for per-source methods, and switching now fades by default.

Read the full Liquidsoap trajectory →

What is Manticore Search?

Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.

Manticore Search's 31.x tags so far are fixes rather than features. 31.0.3 and 31.0.4 were CI and packaging work; 31.0.7 restores string COUNT(DISTINCT) speed after the 29.18.5 collation fix made it 2x slower (1.1 s to 2.4 s on the logs10m benchmark) by calling tolower() per byte. A lookup table replaces the call without changing hash values, so secondary indexes and histograms stay compatible.

Read the full Manticore Search trajectory →

Liquidsoap vs Manticore Search: editorial side-by-side

L6.3

Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own

◆ Current state

The 2.5.x rolling release carries the accumulated 2.5.0 changelog, and it is the largest body of work Liquidsoap has staged in over a year. Subtitles become a dedicated content type alongside audio and video, with native SRT decoding, FFmpeg subtitle encode and decode, bitmap passthrough, callbacks, transformations and dynamic insertion. An Icecast-compatible server ships as icecast.server, with source authentication, mount points, relay and per-listener encoding. Underneath, the source composition model was rewritten: switch, fallback, rotate and random drop their parallel list parameters for per-source methods, and switching now fades by default.

◆ Where it's heading

Liquidsoap is expanding on two axes at once. It is broadening what a stream can carry - subtitles are a third content modality in a system that has understood two - and it is moving up the stack from a source that feeds Icecast into something that can be the Icecast. The language work points the same way: a source(_) type for unknown content, callback release semantics, and effect-scoped clocks are the kind of changes made when scripts are getting large enough that lifetime and typing errors cost real production time.

◆ Prediction

The 2.5.0 final should follow the rolling branch within a release cycle, and the migration guide already shipped for the composition parameter changes suggests the breaking surface is considered settled. Watch whether subtitle support reaches the harbor and Icecast server paths, which the current notes do not say.

M5.0

Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.

◆ Current state

Manticore Search's 31.x tags so far are fixes rather than features. 31.0.3 and 31.0.4 were CI and packaging work; 31.0.7 restores string COUNT(DISTINCT) speed after the 29.18.5 collation fix made it 2x slower (1.1 s to 2.4 s on the logs10m benchmark) by calling tolower() per byte. A lookup table replaces the call without changing hash values, so secondary indexes and histograms stay compatible.

◆ Where it's heading

October has been correctness work on string handling (range filters, collation-aware COUNT(DISTINCT)) followed by fixing the performance cost of those fixes. The 31.x line still appears in the feed without notes on what features justified the major version.

◆ Prediction

Expect more 31.0.x patches in this vein. What new capability defines 31.x remains unclear from these entries.

Alternatives to Liquidsoap and Manticore Search

Other DevOps 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 Liquidsoap or Manticore Search.

See all Liquidsoap alternatives → · See all Manticore Search alternatives →

Recent activity from Liquidsoap and Manticore Search

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3d agoManticore Search31.0.7: string COUNT(DISTINCT) 2x slowdown fixed
  2. 6d agoManticore Search31.0.4: CI fix for bundled Debian dependencies
  3. 6d agoManticore Search31.0.3: Test Kit pinned to Executor 1.4.6
  4. 8d agoManticore Search29.18.7: Manticore Buddy sidecar bumped to 4.4.8
  5. 9d agoManticore Search29.18.6: crash dumps now name the operation and table
  6. 9d agoManticore SearchFix: COUNT(DISTINCT) on strings now respects session collation
  7. 2mo agoLiquidsoapSubtitles become a content type and Liquidsoap ships its own Icecast server ⚡
  8. 2mo agoLiquidsoapLiquidsoap Rolling Release 2.4.x
  9. 4mo agoLiquidsoapQueue removal commands and O(1) clock propagation in Liquidsoap 2.4.5
  10. 6mo agoLiquidsoapLiquidsoap 2.4.4 supersedes 2.4.3 days after release
  11. 6mo agoLiquidsoapRaw string literals arrive in Liquidsoap 2.4.3
  12. 9mo agoLiquidsoapLiquidsoap 2.4.1 opens the stabilization phase

Frequently asked questions

What is the difference between Liquidsoap and Manticore Search?

They serve adjacent needs but don't currently overlap on shipped themes. Liquidsoap 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.

Is Liquidsoap better than Manticore Search?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Liquidsoap 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 DevOps products to evaluate alongside.

What are the best alternatives to Liquidsoap?

Top Liquidsoap alternatives in DevOps are ranked by recent ship velocity. Browse the "Liquidsoap alternatives" section above for the current picks, or visit /alternatives/liquidsoap for the full list with editorial commentary on each.

What are the best alternatives to Manticore Search?

Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.