Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
From the JUCE documentation:
That's not managed by the plugin and I guess that's why there are clicks or audio glitches when looping in Reaper (see this thread).
After more tests on Reaper, it seems really necessary because sometimes the size of the block can really be any value. For the moment, the plugin can't crash even if the number of samples varies because the current version avoid to process when such cases happend but the perform method can lost some samples.
A good solution seems a bit complicated to implement and implies a minimum 64 samples of latency (pd block size) that can be compensated using the latency option of the plugin. So I guess it will also be the time to add a better support for a dynamic latency that could depends on the sample rate or whatever (see the suggestion by Alfonso #62). So the real latency of the plugin will be user-latency+pd-block-size.