I think of jit.matrixset as being comparable to tapin~/tapout~ in the sense that you can store the recent past sequence of video frames in a (potentially circular) buffer and access it at any point. See,Example 35: A delay buffer for Jitter matrices.

Yeah, I tried with jit.matrixset, but It doesn´t seem to have the same kind of layering possibilities as tapin~/tapout~? By that I mean, you can`t record a matrix on top of the other without automatically deleting the first one. So I guess the question is, would I have to make use of some type of poly-structure based on, say jit.matrixset, or Is there another way around. I´m concerned about cpu if the poly-option is the only way.

Thanks for your reply, by the way!

The process you're describing with tapin~/tapout~, as in the MSP Tutorials "27 Delay Lines" and "28 Delay Lines with Feedback", involves three stages: delay, scaling, and addition. The delay is accomplished by making a circular buffer of recent past samples (tapin~) and accessing that buffer at the desired point(s) (tapout~), the scaling is achieved by multiplying that delayed signal by some coefficient (usually less than 1), and the original is then added to the delayed-and-scaled past input (or, in the case of feedback, past output).

In video you could think of that as delay, modification, and compositing. You can make a circular buffer of past frames (jit.matrixset), retrieve and alter a past frame (with jit.op or any other matrix processing object), then composite it with the original (by addition or subtraction, alphablend, or any other method you want). If you want to do that repeatedly, you can record the result back into the jit.matrixset.

I hope that I'm understanding your question correctly, and that that explanation helps.

Well, that makes a lot of sense!

Thank´s again