Max, poly~ and parallel processing

[rodrigo.constanzo]

@weefuzzy

However, there is scope to lower the memory footprint for your patch, which might well help. FluidBufMFCC uses quite a lot of memory internally because it needs to maintain a matrix of stuff big enough to cope with its maximum FFT size. Given that your FFT size is fixed, changing your boxes to specify 4096 as a maximum up front should help:
[fluid.bufmfcc~ 4096 @source htsound @features fluid_mfcc @numcoeffs 20 @fftsettings 4096 2048 4096]

Interesting. I didn’t know this.

So would this also “speed things up” some? For the patch I was working on the hybrid splitting thread I kept massaging settings to eek out every bit of speed I could as it’s doing loads of stuff in a tiny time frame, and given that I often use a Max fft size of 512, wondering if it would benefit to specify that up front.