Best way to run overlapping instances of a single-shot RGB Matrix

[questionmark]

Hello Everyone,

I have a single-shot RGB Matrix that runs the wave animation. I can put this in a chaser to run my wave animation multiple times, but I am not able to overlap the runs. I am trying have multiple waves show up at the same time.

I am kinda guessing there is not a way to do this with a chaser. If if I just had a button that would create another wave every time it was clicked, that would be great as long as the waves could overlap instead of stopping each other.

I put together a demo file to show what I mean. When the hold time is not long enough for the wave to finish running, the wave is cut off. Can I keep the previous wave running while I start a new one?

I am attaching a workspace that shows what I am running into. Hopefully this all makes sense. I would love to provide any additional details for anyone who is kind enough to take a look!

All the best!

Thanks,
Mark

[GGGss]

My best guess is to copy the RGB Matrix and in your chaser, you flip flop between the 2 identical Matrici.
I'm downloading your project now

[GGGss]

Yep - succes
I changed your project - see annex

[questionmark]

Hi GGGsss,

Thank you very much for taking a look at this!

I might be missing something here, but I am getting the same results when I try to use multiple RGB Matrici. In the demo file you sent, the effect looks great, but that is only because each instance has enough time to finish before the next one starts. When I putt the hold time at 300ms, each wave gets stopped in the middle when the next one starts (see attached).

I am still guessing that this cannot be done with a single chaser. The only option I am seeing right now is to have multiple staggered chasers that are all running the RGB Matrix in sequence. Is there a better way than that?

Thanks again for your help!

Mark

[Edit] Forgot to attache the file...

[GGGss]

Aahh ... oke now I get you.
You want to start multiple instances of the same matrix over each other.

Pfieuw - this is something else. You cannot 'shoot and forget' I'm afraid. Things have to run as long as they are instructed to.
The main problem here I can think of is that you cannot enter a 'start-wait-time'...

But hey - try the Matrix to Sequence function.

And then clone them 2 or 3 times.
Change the cloned ones with a dummy first step (start-wait-time)

Now use a collection, add the main sequence and the clones together.
With a collection, you can start multiple things at once.
This should do the trick.
The outcome would be that the RBG Matrix is played 3 times on top of each other and spread in time.
Astonished about myself here very nice effect indeed - #thisisakeeper

[edogawa]

I've also played a bit with your workspace, I''ve managed to make a show with two tracks and put several instances of the red wave matrix on both tracks so that they interleave and indeed the output adds up. Then I added a button in virtual console to start this show.

But this approach leaves me with a fixed in time mix of overlapping waves that runs once and stops, without a way to loop or anything, which probably also isn't what you want.

You can create a row of buttons to fire the matrix (each its own copy as obviously you can't start a function while it's already running), assign a keystroke or a midi controller to it and fire them by this controller.

[questionmark]

GGGsss:

I have never used the dump to sequence before. That is probably as good a solution as I am going to get. It is a really neat effect! Thank you so much for your help!

The bit I don't get from this is the ability to adjust the tempo on the fly (hopefully the song doesn't change much), but I should be able to get my sequence set up and make that work. I'll just have to get my starting cue perfect...

edogawa:

You can create a row of buttons to fire the matrix (each its own copy as obviously you can't start a function while it's already running), assign a keystroke or a midi controller to it and fire them by this controller.

Yeah, the other annoying thing about that setup is that I would have to toggle buttons off after each run before I can use them again.

[GGGss]

Yeah, the other annoying thing about that setup is that I would have to toggle buttons off after each run before I can use them again.

Solo frame with a dummy 'zero' function. You can select whatever effect you like; selecting a new effect will kill the previous, and a 'reset all' is done by tapping the dummy button.

[questionmark]

Solo frame with a dummy 'zero' function. You can select whatever effect you like; selecting a new effect will kill the previous, and a 'reset all' is done by tapping the dummy button.

The point was to keep the previous effect from stopping when the next one is started. A solo frame would stop the wave just like my original chaser did, right?

Anyway, I am planning to go use sequences like you suggested earlier. Thank you for your help!