Well, it’s not always 20ms. There’s 20ms of pre-roll, but the onset detection algorithm always catches that +/- a few samples, so in (a version of) my folder iterating patch, I go through fluid.bufamplslice~ first, and take the first slice output of that as my startframe. This works ok in my own subpatches, but it’d be good to utilize the p featureExtractor subpatch, to not have to faff around with buffers etc…
I could be not following what’s happening when the dict(s) get passed around, but it looks like the entire contents of the dict are passed into fluid.processsegments and then the iteration happens internally. If I follow the feedback loop of bangs, it looks like it’s copying bits from “the big buffer”, so not sure how that would work if I change the contents of the buffer for every loop.