TidalCycles is split across two repos: the Tidal pattern language (Codeberg) and SuperDirt sound engine (GitHub)

A TidalCycles setup is not one program but two cooperating projects, each with its own repository and issue tracker. The Tidal Cycles repository (on Codeberg) holds the Haskell pattern language and pattern library — the part you type patterns into. The SuperDirt repository (on GitHub) holds the sound-synthesis engine that runs inside SuperCollider and actually makes the audio from the messages Tidal sends. Knowing this split matters when reporting bugs: a pattern-syntax or scheduling problem belongs on Codeberg (Tidal), while a sample-playback, synth, or SuperCollider audio problem belongs on GitHub (SuperDirt). It also explains why installing Tidal requires SuperCollider plus SuperDirt alongside the Haskell package.

Examples

‘every behaves unexpectedly’ → Tidal repo on Codeberg; ‘my samples crackle / a synthdef errors in SuperCollider’ → SuperDirt repo on GitHub.

Assessment

Given a bug report, decide whether it belongs to the Tidal (Codeberg) or SuperDirt (GitHub) repository, and justify which layer is responsible.