Separate audio outputs

From TidalCycles userbase
Revision as of 18:20, 27 July 2019 by Yaxu (talk | contribs) (Automatically sending d1, d2 to different orbits)
Jump to: navigation, search

How can I output/record separate audio channels?

Lets say you wanted to make a multi-track recording, with different patterns playing at the same time, but recorded separately.. Or wanted to route the audio from some patterns into external effects processor. How is this possible?

Tidal's audio engine is (most often) SuperDirt, and the key to routing audio channels is understanding how to configure and use orbits. You can think of each orbit as an audio output, with its own set of global effects (by default, reverb and delay).

Have a look at SuperDirt's documentation, in particular the example superdirt_startup.scd file. You'll want to paste the setup code into the supercollider editor window. If you save it in your supercollider startup file it will automatically run when you open supercollider - you can find that file via the menus.

There are probably only two bits that you will want to change in the setup code. If you wanted six stereo outputs, that would require 12 channels in total, so you would set the number of output bus channels accordingly, i.e.:

s.options.numOutputBusChannels = 12;

You assign the orbits to separate stereo channels by offsetting each one, like this:

~dirt.start(57120, [0, 2, 4, 6, 8, 10]);

You might also be tempted to change the number in this line:

~dirt = SuperDirt(2, s);

However if you want to work in stereo, you should keep this number to 2, i.e. the number of channels per orbit.

Then to send a tidal pattern to a particular orbit, you just use a parameter, e.g. d1 $ sound "bd sn" # orbit 2 to send it to the third one (counting from 0). You're now free to route the audio to a DAW for e.g. effects processing or recording, or record all the channels straight from supercollider into a single multichannel file. Have a look around the SuperDirt hacks folder for more fun with orbits.

Automatically sending d1, d2 to different orbits

Please note, if your plugin (or BootTidal.hs file) is up to date, the following behaviour is now default

You might want to always send d1 to the first orbit, d2 to the second, and so on. You can do that by running the following:

let d1 = p 1 . (|< orbit 0) 
    d2 = p 2 . (|< orbit 1) 
    d3 = p 3 . (|< orbit 2) 
    d4 = p 4 . (|< orbit 3) 
    d5 = p 5 . (|< orbit 4) 
    d6 = p 6 . (|< orbit 5) 
    d7 = p 7 . (|< orbit 6) 
    d8 = p 8 . (|< orbit 7) 
    d9 = p 9 . (|< orbit 8)
    d10 = p 10 . (|< orbit 9)
    d11 = p 11 . (|< orbit 10)

You can make this permanent by modifying the default definitions in your BootTidal.hs file