Difference between revisions of "Configuration"

From TidalCycles userbase
Jump to: navigation, search
(Created page with "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. Here is the new startup code: https://git...")
 
Line 1: Line 1:
 
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.
 
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.
  
Here is the new startup code:
+
You can find the new startup code here: https://github.com/tidalcycles/Tidal/blob/master/BootTidal.hs
  https://github.com/tidalcycles/Tidal/blob/master/BootTidal.hs
 
  
 
You can just run it in a tidal buffer and all should be fine.
 
You can just run it in a tidal buffer and all should be fine.

Revision as of 19:28, 7 November 2018

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.

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.