mystran wrote:point is, the actual block size is variable and simply has an upper bound.
Correct, and it's done that way to improve memory allocation, by only having to allocate once at the start.
mystran wrote:The thing that's important to remember is that the buffer size as reported by the host is the maximum size of what you might get asked to process at once. The number of samples you actually get into your processReplacing (or whatever equivalent function) can actually vary quite a bit (which is why there's an argument for it. In some cases like FL Studio it's basically guaranteed to vary all the time, in some other hosts it's "usually buffersize" with an odd shorter buffer once in a while (eg. when hitting loop point or something) and then some hosts just always use fixed size buffers all the way... but point is, the actual block size is variable and simply has an upper bound.
meneervermeer wrote:I found following post on the Juce forums: