State values were recently introducted in Tidal version
1.7.2. For a more
in-depth introduction, Alex McLean prepared a Google Slides document you can take a look at. It will explain why such a feature was needed and how it was implemented.
What is the problem? It's tricky to get events to line up. Let's say that you wanted to pattern the structure independently from the notes (isorhythm?):
There are ways to fix this (e.g. with the
fix function), but they are not too satisfying/easy.
But now you can use a state value called "susan" to take values from a (circular) list:
If you change it on-the-fly then you have to wait for the list to empty before it changes:
It can cope with infinite lists, but then the list will never empty:
You can stop it and it will always start from where it left off:
You can also just count without a list:
This is the same named state as used by
setF and for reading from OSC/MIDI. So you can reset the counter like this:
Or have another pattern use it:
There is also
nCountTo to counting to a modulo:
You can pattern that.. It starts behaving in ways you wouldn't expect from a Tidal perspective though.. Because the counter runs independently from the pattern:
rev won't reverse the counter:
The structure is reversed, but the notes still go up:
You should be able to add
Take to any control, and
CountTo to any numerical control.
This feature is unstable, so these names might change.