I didn’t use Max Delay very often, so I’m not fully sure what the practical impact of its removal is.
My current understanding is that, since Reset allows us to clear the delay buffer at an arbitrary timing, Max Delay may no longer be necessary.
Is this interpretation correct?
Are there any potential side effects or limitations caused by the removal of Max Delay, especially for long-delay setups?
(I’m currently building a long-delay network, so this caught my attention…)
Thanks for your quick reply, @snaut
(And Max Delay was removed from the documentation even faster than my reply… )
I think I understand the intention behind this change now.
By the way, for achieving long delays similar to a Roland-style tape echo, I found that a setup using Trail CHOP + Shift CHOP + Time Slice CHOP, as mentioned in other threads on this forum, works better than using Delay CHOP.
One thing I noticed is that any small frame drop immediately introduces click noise, so for stable real-time operation, it seems that running this inside an Engine COMP (or otherwise isolating it from UI-related frame drops) may be necessary.
As always, I really appreciate how active and precise the responses are in the TouchDesigner community.
Thanks again!
Hi Peachman, please have a look at this file for a really nice way of making an audio delay network with variable pitch etc. Many other time-based effects can be derived from it. Using an engine COMP for this task is gonna be a headache and introduces undesirable signal delay.
edit: I just noticed that the file is missing a few of the things I learned since then. Notably, in the delay example I use an analyze CHOP and use the channel information to cook a transparent pixel but all that can be removed by placing a null CHOP with cook set to “always” at the end of your delay line.