Peiman

Why is it that one cannot create feedback using delay~, but tapin/tapout works?

delay-feedback-question

I think there might be 2 issues here which you'd be interested in.
-delays in MSP are limited to the vector size (which is not relevant to this context)
-MSP has a safety mechanism, whereby signals cannot be connected in a feedback loop directly... instead you can use send~ and receive~ in the middle of the feedback loop but it will introduce a vector's worth of delay if it is a true feedback loop(it's a safety mechanism since before i can remember...since max3?)... tapin~/tapout~ was designed to bypass this restriction, but it is still limited to delays only as small as the vector size.

To get a fully capable delay with feedback, you'd want to build it all in gen~(including the feedback portion), much like i did here:
https://cycling74.com/forums/sharing-is-for-asswipes-anaechowat-a-unique-delay-made-in-gen/

Thanks for your explanation. That all makes sense. So to be sure, when using send~/receive~, is the vector size delay added to the delay that's already programmed in the patch (delay~ object)? Or is it only added if such delay does not exist?


Not added, but it determines the absolute minimum of delaytime you could achieve with delay~ or tapin~/tapout~(Hehe, it so happens this is described in Eric Lyon's book, too ;)


delay~ & feedback question