← Back to home
Comparison · DevOps

Liquidsoap vs Meilisearch

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

Liquidsoap vs Meilisearch: at a glance

FeatureLiquidsoapMeilisearch
SectorDevOpsDevOps
Velocity score6.36.3
Sparks · 30d10
Top themesaudio-streaming, subtitles, icecast, ocamlsearch-engine, reverts, stability, experimental-flags
Last editorial update2h ago5d 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 Meilisearch?

A week of reverts and prototype tags, with tuning knobs standing in for features.

Meilisearch spent this window stabilizing rather than shipping. Three consecutive patch releases rolled back work from v1.52.0 — the SSE /tasks/stream and /batches/stream routes, a search-formatting speedup, and some search progress traces — while a set of prototype tags carried crash fixes on a side branch. The newest release adds an environment variable capping concurrent LMDB read transactions on the task queue.

Read the full Meilisearch trajectory →

Liquidsoap vs Meilisearch: 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.

M6.3

A week of reverts and prototype tags, with tuning knobs standing in for features.

◆ Current state

Meilisearch spent this window stabilizing rather than shipping. Three consecutive patch releases rolled back work from v1.52.0 — the SSE /tasks/stream and /batches/stream routes, a search-formatting speedup, and some search progress traces — while a set of prototype tags carried crash fixes on a side branch. The newest release adds an environment variable capping concurrent LMDB read transactions on the task queue.

◆ Where it's heading

The revert pattern says v1.52.0 shipped more than it could hold: the streaming routes were labeled experimental and came straight back out, and the formatting optimization followed. Version numbering has stopped being linear, with v1.53.1 and v1.53.0 landing around a v1.52.x patch train. The new work that survives is operational tuning — knobs for operators running the engine, not surface for application developers.

◆ Prediction

The reverted SSE streaming routes are the open thread; expect them to return once the crash-fix branch settles, likely still gated as experimental.

Alternatives to Liquidsoap and Meilisearch

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 Meilisearch.

See all Liquidsoap alternatives → · See all Meilisearch alternatives →

Recent activity from Liquidsoap and Meilisearch

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

  1. 15h agoLiquidsoapSubtitles become a content type and Liquidsoap ships its own Icecast server
  2. 5d agoMeilisearchEnv var caps concurrent task-queue read transactions
  3. 7d agoMeilisearchPrototype tag bumps the crash-fix build to v1.52.3
  4. 8d agoMeilisearchSecond prototype tag for the v1.52.3 crash-fix branch
  5. 8d agoMeilisearchv1.52.3 reverts the search formatting speedup
  6. 8d agoMeilisearchv1.52.2 pulls the experimental /tasks/stream and /batches/stream routes
  7. 8d agoMeilisearchv1.52.1 makes the health route blocking and drops search progress traces
  8. 9d agoLiquidsoapLiquidsoap Rolling Release 2.4.x
  9. 2mo agoLiquidsoapQueue removal commands and O(1) clock propagation in Liquidsoap 2.4.5
  10. 4mo agoLiquidsoapLiquidsoap 2.4.4 supersedes 2.4.3 days after release
  11. 4mo agoLiquidsoapRaw string literals arrive in Liquidsoap 2.4.3
  12. 7mo agoLiquidsoapLiquidsoap 2.4.1 opens the stabilization phase

Frequently asked questions

What is the difference between Liquidsoap and Meilisearch?

They serve adjacent needs but don't currently overlap on shipped themes. Liquidsoap and Meilisearch are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.

Is Liquidsoap better than Meilisearch?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Liquidsoap and Meilisearch are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Meilisearch?

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