Rename/rejig stepwise functions

[yaxu]

Tracking developments in tidalcycles/strudel#1207

Tweaks to do along the way

• polymeter should fit a cycle, the lowest common multiple being the step count. This should probably apply in mininotation to {} as well
• As @matthewkaney pointed out, step count of euclid should be used e.g. "x(3,8)" should have step count of 8
• Look at bringing back old 'preplace' functionality, ref Preplace update #718

[sss-create]

Should we implement as breaking change or alias the old functions to the new?

[yaxu]

Should we implement as breaking change or alias the old functions to the new?

I made deprecated aliases in strudel, but the old function names aren't in a release and not many people are running dev, so I think no need for tidal.

[sss-create]

hm, so renaming setTactus was easy, however I don't get how to use it or what it does exactly (neither code nor videos).

• is expand in strudel elongate in tidal? Others from the list in Strudel are not implemented in Tidal yet, right? Like grow/shrink?

[yaxu]

I've been jumping between tidal and strudel, so Tidal is more advanced having patterned tactus/steps, and strudel has cleaner function names.

This page is trying to explain it: https://strudel.cc/learn/stepwise/

[yaxu]

Hmm tidal doesn't have an elongate function? But yes expand is similar to @ in mininotation.

[yaxu]

The count here should probably be multiplied to "6 4"

tidal> steps (fastcat ["a b c", "d e"] :: Pattern String)
Just (0>½)|3 % 1
(½>1)|2 % 1

The count pattern here should also be time shifted:

tidal> steps (rotL 0.1 $ fastcat ["a b c", "d e"] :: Pattern String)
Just (0>½)|3 % 1
(½>1)|2 % 1

[sss-create]

this is more like tidal 2.0 now, right?

[yaxu]

this is more like tidal 2.0 now, right?

No but work will continue past 1.10 - I expect to continually work on and merge tweaks and enhancements around this.

[sss-create]

I have the feeling that this issue and #1039 and maybe #1144 could be merged into one issue, @yaxu?

Additionally, maybe a 'function' label to mark other issues that deal with concrete function bugs/feature request is a good idea.

[yaxu]

I've closed #1144. #1039 is best left as a separate issue I think, as this is focussed on stepwise changes. Feel free to tinker with labels..