
vobb
@jameslo I am very latency sensitive since this is a realtime application hooked up to a guitar. I will investigate your patch and see if the latency added is acceptable, thanks!

vobb
@whaleav Thanks, that's very useful. I am on vanilla and the docs for [block~] was a bit anemic. @katjav's site and posts have already been invaluable! I am targeting frame size = wavelength so that I do not have to worry too much about boundary effects. Unless my limited experience with FFT is wrong, the best FFT frame size will be the one that is exactly the wavelength of the monophonic sound I'm analyzing, hence the combination of her [helmholtz~] component with FFT. I may still end up writing this in some sort of external such that I have full control over the frame, upsampling etc.
I have not yet tried windowing with overlap and such, but somehow I doubt that it will be as good as a perfectly fitting rectangular window since my frame sizes are so small. If my initial plan does not work out, then I might try this.

vobb
Hello and thanks for taking the time. FFT is not restricted to poweroftwo but it runs most efficiently that way, unless this SE thread is completely off it's O(N log N) vs O(N^2))  and the frame sizes I'm targeting are very small so it shouldn't be a problem.
As to [block~], I've not been able to set it dynamically and am not finding the documentation for doing so. I think I got the hang of the relationship between how parent blocksize interacts with child blocksize beyond that enough to make it work.

vobb
Does such a thing exist? I am fairly new to pd and am having a very hard time knowing where to look for externals. I am detecting pitch using [helmholtz~] and would like to do FFT on the audio stream with frames the size of the pitch that [hh~] outputs
Thanks!