Start tidalcycles and superdirt for the first time

From TidalCycles userbase
Revision as of 16:27, 21 March 2019 by Yaxu (talk | contribs)
Jump to: navigation, search

There are two steps to starting up TidalCycles each time:

  1. start SuperDirt inside SuperCollider
  2. start TidalCycles inside Atom

Start SuperDirt inside SuperCollider

To start SuperDirt, paste the following code into a SuperCollider window:


Then click on the code, hold down shift and press enter. The post window should show the SuperDirt startup progress, and at the end you should see:

SuperDirt: listening to Tidal on port 57120

Automatic SuperDirt Startup

If you want SuperDirt to start automatically when you open SuperCollider, add the SuperDirt.start line to the SuperCollider startup file. You can edit the SuperCollider startup file from within SuperCollider itself by choosing File -> Open Startup File from the top menu. If you wish to use a more comprehensive SuperDirt startup file with more options, refer to this example.

Start TidalCycles inside Atom

  1. Start Atom
  2. create a new file and save it with a filename that ends in .tidal, e.g. test.tidal.
  3. open the Packages menu and select TidalCycles -> Boot TidalCycles. A small window will open at the bottom of the window and display some text to tell you that the GHCi interpreter is running.

Try running a simple pattern by typing in the code below and holding down shift and pressing enter to evaluate it (Holding down control and pressing enter will also work, this evaluates multiple lines).

d1 $ sound "bd sn"

If you hear sound, congratulations!

If you get stuck, you are very welcome to ask questions and share problems on the forum, or on the #tidal channel of the Lurk RocketChat.

As is common with free software, you have alternative choices for the different components that make up a TidalCycles system. Atom and SuperDirt might be all you ever need, but there are other editors and synths you can use.