davidestevens

I made this so that I could easily move patterns of points in a matrix around for a lighting sequencer, but it's probably got other uses. And it demonstrates using jitter for storing and manipulating long lists. There may well be a more elegant way of doing this, but in the meantime, here's my effort...

share-easily-scroll-on-points-in-a-matrix

Here's another way of doing it - note that this doesn't shift the original entry box about, which I find preferable in most instances:

Cool. And much neater. Thanks for that. This old dog just learnt a new trick :-)

(Although, now that I've replaced the 14 old versions, it doesn't seem quite so responsive - there's a bit of a lag between clicking the "move" button, and the on points moving. Any thoughts on why that might be?)

Hm. I had to go back to my way of doing it. 15 copies of the simpler patch uses up around 90% cpu (according to Activity Monitor), as opposed to 30% in my more fiddly version. I wouldn't have thought 15 simple jitter patches would consume so much cpu/ any thoughts about why that would be?

because you're constantly banging them, instead of banging when the state changes, I guess. It's the [metro 20] or whatever that was that was the problem, I think.

IDK, I haven't seen your big many-copy-one, of course - if you're using 90% cpu on this system*15 then there's something quite wrong.

Normally, running things in a poly helps scale things a lot, too - it feels somewhat "dirty" to be copying things a lot.

IDK, I haven't seen your big many-copy-one, of course - if you're using 90% cpu on this system*15 then there's something quite wrong. 

Normally, running things in a poly helps scale things a lot, too - it feels somewhat "dirty" to be copying things a lot.


This does away with the metro altogether, it should be much lighter:

Thanks Andreas, I think that's where i was headed next. Another thing that had never occurred to me to do - include ,bang in a message box! After all these years!

Tried it out, and things are fine until you try to feed the altered position back to the matrix ctrl. You get a stack overflow. Using an additional matrix for the return eliminates that problem .

[Share] Easily scroll "on" points in a matrix