After having a bit of a discussion about this object with @tremblap (and the team) a few months ago (and having bounced a version of the Max-based version of the patch with @tremblap for years before that) I left somewhat understanding the complxity of the parameters and what they do.
That being said, having those things assigned to names that are divorced from a symbolic meaning and seeing the presentation today, I ended up fairly confused about what does what.
I can’t imagine a way that you can communicate all of it in the helpfiles (or anywhere else) with just text. The problem is way too complex, and even the series of didactic sc examples shown in the second plenary don’t really illustrate what the parameters are doing, only the results they have.
On that, I remembered a subpatch in a little tutorial a friend (raja from the Max/monome forums) had made that helped me understand the
grooveduck abstraction fully. It used visual aids in a way that worked well and was fairly compact so it still made sense in a helpfile.
This is that subpatch:
I think you need something like this for the critical parameters in
(and for good measure, attaching the complete “lil` sampling tutorial”)
Raja’sLil’SamplingTutorial.maxpat.zip (801.8 KB)