Configuration

From TidalCycles userbase
Revision as of 19:19, 29 November 2018 by Mauro (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: https://github.com/tidalcycles/Tidal/blob/master/BootTidal.hs

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

Vim

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

Controlling latency

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

In the old tidal, this value used to be 0.3, but by default is currently set to 0.01.


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 = "192.168.0.23"}) defaultConfig

In case you need to alter multiple settings for superdirtTarget, just separate them by a comma ({oAddress = "1.2.3.4", oLatency = 0.04}). Finally, if by change this fails, make sure to escape the quotation mark.