TidalCycles is a live-coding pattern language
For installation instructions, please visit: http://tidalcycles.org/getting_started.html
Then, you can:
shift+enter to evaluate the current line or selection
cmd+enter to evaluate multiple-lines or selection
To send patterns to SuperDirt, use
d1 $ sound "bd cp"
To send patterns to classic dirt, use
c1 $ sound "bd cp"
By default, Atom will use a default Tidal bootup sequence that doesn't really do
anything special other than create the
c1..c9 Dirt connections.
If you'd like to provide a path to your own custom boot file on your computer, use the Boot Tidal Path setting to do so.
Further, if you'd like Atom to locate a
BootTidal.hs file in the current directory,
check the Use Boot File In Current Directory option.
Boot file order of precedence:
If you create your own boot file, you may start with the default:
:set -XOverloadedStrings :set prompt "" :module Sound.Tidal.Context (cps, nudger, getNow) <- cpsUtils' (d1,t1) <- superDirtSetters getNow (d2,t2) <- superDirtSetters getNow (d3,t3) <- superDirtSetters getNow (d4,t4) <- superDirtSetters getNow (d5,t5) <- superDirtSetters getNow (d6,t6) <- superDirtSetters getNow (d7,t7) <- superDirtSetters getNow (d8,t8) <- superDirtSetters getNow (d9,t9) <- superDirtSetters getNow let bps x = cps (x/2) let hush = mapM_ ($ silence) [d1,d2,d3,d4,d5,d6,d7,d8,d9] let solo = (>>) hush :set prompt "tidal> "
If you'd like to contribute to this package, here are some guidelines:
a beautifier package (we recommend
atom-beautify) to format your changes with
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.