Forums > MaxMSP

old "bug" still there: tapin~/tapout~ one sample of extra delay

April 11, 2011 | 1:08 pm

Hi all, there is an old bug or issue in the tapin~ tapout~ couple, and I’d like to know if it will be corrected in the future or not (either way it’s ok for me, i just need to know what to expect).

When you set the delay time in a tapout~ object with a signal you get a delay which is always one sample longer of what you set (please note, i’m NOT talking about the minimum delay of one signal vector here).
If you set the delay time with a max message you get the exact delay you set.

Here is a patch that demonstrates the issue:

— Pasted Max Patch, click to expand. —
April 11, 2011 | 4:36 pm

Hi Maurizio,

This delay is intentional and not going to be changed any time soon.

This is due to interpolation that is used on the signal input. I believe your workaround is appropriate.


April 11, 2011 | 8:16 pm

Hi Ben,

good to know, thank you for your clarification.


Viewing 3 posts - 1 through 3 (of 3 total)

Forums > MaxMSP