From TidalCycles userbase
Revision as of 00:15, 4 December 2018 by Yaxu (talk | contribs)
Jump to: navigation, search

The Tidal boot-up procedure has changed, so with Tidal 1.0.0-pre installed, you'll probably get errors when you start your editor.

You can find the new startup code here:

You can just run it in a tidal buffer and all should be fine.


If you are using vim-tidal, check out the instructions found on the file. You need to use the 1.0.0-pre branch of the plugin.

Controlling latency

There are two configuration values which control overall latency, 'frame timespan' and 'latency'. To find the maximum total latency, add them together. Here's an example configuration:

tidal <- startTidal (superdirtTarget {oLatency = 0.02}) (defaultConfig {cFrameTimespan = 1/20})

Frame timespan

This is the duration of Tidal's calculation window in seconds. The default is 0.05 seconds, in other words a calculation rate of 20 frames per second.


If you get late messages in supercollider, you can increase the latency by changing the startTidal line to e.g.:

tidal <- startTidal (superdirtTarget {oLatency = 0.04}) defaultConfig

By default this is currently set to 0.02.

SuperDirt running in another host

If you're running SuperDirt in another host (perhaps, in a multi-user setup), you need to define this in a similar fashion as with the latency, except in this case the keyname is "oAddress":

tidal <- startTidal (superdirtTarget {oAddress = "", oPort = 57120}) defaultConfig

In case you need to alter multiple settings for superdirtTarget, just separate them by a comma ({oAddress = "", oLatency = 0.04}).

Note that in emacs (and possibly other editor) configuration files, you'll need to escape the quotation marks.