Difference between revisions of "Configuration"
Line 10: | Line 10: | ||
= Controlling latency = | = Controlling latency = | ||
+ | |||
+ | There are two configuration values which control overall latency, 'frame timespan' and 'latency'. To find the maximum total latency, add them together. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | == Latency == | ||
If you get late messages in supercollider, you can increase the latency by changing the startTidal line to e.g.: | If you get late messages in supercollider, you can increase the latency by changing the startTidal line to e.g.: | ||
Line 17: | Line 27: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
− | + | By default this is currently set to 0.02. | |
− | |||
= SuperDirt running in another host = | = SuperDirt running in another host = | ||
Line 25: | Line 34: | ||
<syntaxhighlight lang="Haskell"> | <syntaxhighlight lang="Haskell"> | ||
− | tidal <- startTidal (superdirtTarget {oAddress = "192.168.0.23"}) defaultConfig | + | tidal <- startTidal (superdirtTarget {oAddress = "192.168.0.23", oPort = 57120}) defaultConfig |
</syntaxhighlight> | </syntaxhighlight> | ||
− | In case you need to alter multiple settings for superdirtTarget, just separate them by a comma (''{oAddress = "1.2.3.4", oLatency = 0.04}''). | + | In case you need to alter multiple settings for superdirtTarget, just separate them by a comma (''{oAddress = "1.2.3.4", oLatency = 0.04}''). |
+ | |||
+ | Note that in emacs (and possibly other editor) configuration files, you'll need to escape the quotation marks. | ||
[[Category:Tidal-1+]] | [[Category:Tidal-1+]] |
Revision as of 23:13, 3 December 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.
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
There are two configuration values which control overall latency, 'frame timespan' and 'latency'. To find the maximum total latency, add them together.
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.
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
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 = "192.168.0.23", oPort = 57120}) 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}).
Note that in emacs (and possibly other editor) configuration files, you'll need to escape the quotation marks.