tidalcycles / tidalcycles.github.io

Website for TidalCycles
http://tidalcycles.org
23 stars 29 forks source link

enumeration of functions from source #72

Open sfradkin opened 7 years ago

sfradkin commented 7 years ago

This is a rough list of all of the various functions found in the TidalCycles source in the 0.9 branch. More changes were added after this list was generated.

This includes some notes about functions if I could figure out what they did.

It's a combination of functions that are part of the everyday DSL and also internal functions that wouldn't normally be used. We need to decide what should be documented on the website and what does not need to be documented on the website.

compositions

conditional transformers

pattern transformers

sample transformers

synth params

tremolorate and tremolodepth

transitions

utility

lennart commented 7 years ago

the checkboxes mark, needs docs for website?

in any case, regarding your question at the end:

grp yes, although this is one of the only functions usin raw params not synth function cutoff_p not cutoff

make' no actually, since this is the general version of pF, pI and pS for producing params/synths. I'd document only the latter three, since currently we only have Float/Int/String as Value types (and make' would force us to explain what Value is, which would be something that should not directly be explain for using tidal as a DSL)

bgold-cosmos commented 7 years ago

In the past I've usually ignored functions that don't return Patterns/ParamPatterns - these are almost always "internal" things like arcCycles that I can't imagine ever using live (though maybe I just don't have enough imagination).

There are boatloads of params related to MIDI stuff, but some of them also apply to SuperDirt and I've haphazardly repurposed a few more for particular synths. There's some docs of this within the SuperDirt source itself but it'd be good to make a web page summary.

As I look through I'm actually surprised to note that I think most of the stuff is documented somewhere on the website, but I could be misremembering things...

sfradkin commented 7 years ago

@lennart: Yes, let's check the functions that we need documentation for, then after we go through this list, we can close this issue and add the function names to @bgold-cosmos's existing issue for new documentation for 0.9. We just need some way to make it clear what functions should have documentation on the website vs just in code, and then a way to keep track of whether or not that documentation has actually been written.