In the example to select number of slices to match to in advance (and reprocess until it is met), zl is by default at 256, so returning nums of slices > 256 has caused problems. Suggest using argument to increase each zl (thought patch had crashed various times).
Yup, good catch. FWIW, this is one reason why buffer~
s are a good default container: zl
has this 256 item default, which can be irritating, but Max has an absolute limit of 215-1 (IIRC), that could easily be exceed with long / ticklish files.
IAC, yes: we’ll up the limit in that example, but also put a check in to more gracefully and informatively moan when it’s exceeded.
Also your profile pic is just so good.
aha! now i remember why
Hello @saguaro
I’m picking this up, and I cannot find a moment in the patch where zl is dealing with more than 2 elements. I must miss something obvious, can you help me please?
Ah it was actually in the fluid.bufstats~ helpfile code. Either [p sortStatistic] or [p indicesLookup] as far as I recall.
indeed found and sorted thanks!