Forums > MaxMSP

What's wrong with this simple delay loop?

October 11, 2009 | 6:58 pm

Hello folks. New user here… Was just wondering if anyone could help me figure out what’s wrong with this echo delay? It’s a very simple patch but I can’t figure out why it isn’t working.

It works if you remove the cord that I’ve labelled, but the essence of an echo delay filter is that the output of the delay is fed back into itself, so that’s an essential component! But when it is connected, the output mutes!

What is going on here? Is Max detecting some kind of feedback loop and automatically cutting out? If so, how can I avoid this? Thanks for your help. Patch below.

#P window setfont "Sans Serif" 9.;
#P window linecount 1;
#P comment 188 155 33 9109513 delay;
#P comment 242 164 53 9109513 attenuation;
#P flonum 247 189 35 9 0. 1. 3 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P number 184 182 35 9 0 0 1 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P user ezadc~ 52 141 96 174 0;
#P user ezdac~ 105 580 149 613 0;
#P newex 194 388 27 9109513 *~;
#P newex 161 237 64 9109513 mstosamps~;
#P newex 134 336 72 9109513 delay~ 22050 0;
#P comment 202 449 132 9109513 remove this cord to fix…;
#P connect 3 0 4 0;
#P fasten 3 0 1 0 199 464 368 464 368 332 139 332;
#P connect 3 0 4 1;
#P connect 5 1 1 0;
#P connect 5 1 4 1;
#P connect 5 0 4 0;
#P connect 5 0 1 0;
#P connect 7 0 3 1;
#P connect 6 0 2 0;
#P connect 2 1 1 1;
#P connect 1 0 3 0;
#P window clipboard copycount 10;


October 11, 2009 | 7:28 pm

Hi,
not sure, but I think delay~ was not designed to accept a feedback loop (check the title of delay~ help).
You may use a pair of tapin~ and tapout~ instead.


October 11, 2009 | 9:45 pm

That’s done it! Thanks.


October 12, 2009 | 4:24 am

you can use feedback with delay~ by using send~ and receive~, but this is more for filter design than for long delays.


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