Thank you @fishcrystals for the explanation and @jameslo for the test results. Very helpful!

Thank you both for the clarification

I'm writing a paper where I measure the latency of an instrument I built that synthesizes sound with PD, and was wondering what to call this 'delay' parameter. I'm used to seeing it described as something like an 'I/O Vector Size' as in Max...

Thanks again for the help

Very helpful. Thanks for the reply.

So the purpose of this buffer is to accommodate the IO hardware?

And does this type of buffer have a name?

It seems to have something to do with the in/out buffer? But is not the same as the block size? Looking for a technical, under-the-hood explanation. Or a referral to any existing documentation... Thx

nice implementation and very resourceful approach using the vanilla objects. thx for sharing! will save this for future reference

I've updated ambiNilla (v.3.5) to include a signal rate implementation (ambiNilla3~). Works well for fast moving sources

thx for the response @seb-harmonik.ar . I've just fixed it. In short I had a few layers of switches nested within various subpatches. I realized that turning on/off the lowest layered switch was redundant, and it seems to be fine now.

It sounds (sonically) like it may be related to the issue you posted. I'm PD 0.55-0. thanks again!

Theoretically, I'm still not sure why it was causing that issue, But regardless, I'm happy it's fixed

I'm having problems with a strange distortion sound a patch of mine is making, perhaps related to FFT processing.

The patch uses a preset system to change between settings. The system will mute the input to FFT objects during preset changes to avoid audio issues. However, when the preset changes I'm often getting a sort of distortion, which strangely clears up if I add & delete an object.

I've demonstrated it here:

My DAW is looping audio which is sent to PD for processing. The loop is on top of a preset change to demonstrate the issue.

Any clues as to what this could be?

actually macos. APFS filesystem, which i'm just reading is case-insensitive by default.

now i'm a bit worried that other patches I've shared might have similar issues ...

@alexandros thx for catching that! (for some reason my pd runs it ok even with the case mixup?) i've updated the source files for consistency. thx again