TidalCycles vs Strudel

Strudel is TidalCycles’ pattern language reimplemented in JavaScript. The patterns are near-identical; everything around them is different.

Side by side

Where they actually differ

The patterns transfer, the muscle memory mostly does

Strudel deliberately mirrors Tidal’s pattern functions, so every, fast, jux, rev and mini-notation largely behave as you expect. Moving between them is far easier than moving between unrelated systems — but the ecosystems around them are not interchangeable.

Zero install changes who can use it

Strudel needs no toolchain. That makes it dramatically better for teaching, for workshops, for trying an idea on someone else’s machine, and for sharing a patch as a link that just plays. Tidal’s setup is a genuine barrier that Strudel simply removes.

SuperDirt is still the richer instrument

Tidal drives SuperDirt on SuperCollider, which brings a deep sample-playback engine, effects, and the whole SuperCollider synthesis world underneath. Strudel’s Web Audio engine is capable and improving, but it is not the same depth of instrument.

Timing is tighter on the native stack

Browser audio scheduling is good enough for most performance, but SuperCollider’s native engine has the edge for tight timing and heavy DSP. If you are running a demanding set, that gap is worth knowing about.

Which should you choose?

Choose TidalCycles when…

• You want SuperDirt and the SuperCollider engine
• You need the most mature library and community
• Tight timing under heavy load matters
• You already have the stack running

Choose Strudel when…

• You want to start immediately, with no install
• You are teaching or running a workshop
• You want to share a patch as a link
• You are on a machine you cannot install software on

Strudel cheat sheet → · TidalCycles cheat sheet →

← All comparisons