Resending an event? (Bang a event again)

[hesspet]

Hello,

I have a matrix which creates an "array data event" that works fine. The event is received somewhere, if something is changed in the matrix. And now - I've the need, that the whole array event must be send again, without any chance on the surface. But how to do that? Usine has no "bang" link we have this in MAX/MSP.

I'm looking for a way to send the event more than one time. Maybe I've tomatos on the eyes, but know im stuck.

How to solve this?

Is there a way to store a event and resend/create it many times?

Help needed to save the weekend

Thanks for all support.

Peter

[nay-seven]

The store array script can do this
15 presets (more if you want) where you can store and get ( use pass/stop modules if needed)

[hesspet]

SUPER BIG TOMATOS

Thanks. That what I was looking for. Perfect.

[hesspet]

Help!

I'm pretty deep in the water... "store" does not work or I undertand something wrong!

If I run this test patch:



Walk-Through:

- klick some spots in the first matrix
- press "button store"
Result: spots are visible(copied) in the second matrix

From my point of view the array is stored.

- then I press "reset b"
Result: the second matrix is not cleared. ->OK
- then I press "button get"

Result: ----> nothing happend., the second matrix should be filled again, but this does not happen.

The "get" does not fire anything. I put some traces into the script. I see, that the arrayOut is filled, but I get no output.
Is my understanding/usage here wrong?

Peter

[nay-seven]

the idea :

matrix A created
current number =0
Store

change matrix A
current num=1
store

now :
current num=0
Get
will recall first preset on matrix B

num=1
Get
will recall second preset on matrix B

[hesspet]

Thanks for you answer!

OK, the recal I get working. So the "magic" is setting explicit the num before the "get"
But when I follow your rule, and I try a second get on num=1, cause I need the pattern 2 or more times to feed into a sequencer, this will not work.

I did not understand why this happen (or not happen). My problem is the sending the same pattern a second time.
This is something I can't figure out. Maybe there is a sort of "optimisation" in Usine. The same value is not sent to an import pin, a second time?

Peter

[nay-seven]

yes, i suppose a script guru can explain and solve this
waiting for this, here a workaround : sending 2 values : preset 0 ( or any other in fact) then your preset

Download

[hesspet]

Hihihi!

You stand up earlier

my solution;



I build a "bloc sequencer" which switches 2 patterns. A empty prefilled and the pattern which should be repeated.

I'll will look into you patch after writing this.
First of all: Thanks for you helpful support!

Peter

P.S: Does not work if the repeated pattern is a empty pattern. But, ok, I can live with that...

[hesspet]

Reviewed.

Your had the same idea using a sort of a delay. I think we could mark this solved. It looks, that there is no better solution available.

Thanks again!

Peter

P.S.: If someone can explain me, why the second update of the same data is ignored, feel free to explain that. I'm sure I'm not the only user who struggles over this. (It's the quest for the "bang the same value twice")

[ynohtna]

Yeah, this is weird 'cos I've just been hit by this problem in a patch I'm hacking together. Seems that arrays inlets on downstream modules are not notified that the array has been altered if it's content remains the same. Which kinda makes sense logically but sometimes subverts expectations.

And this alteration check only seems - from what I can tell - to happen between processing frames. Altering an element of the array (or it's length) then changing it back immediately doesn't set any "modified" flags, so there must be a contents comparison occurring on the target module's Callback check.

Sorry for rambling!

[ynohtna]

Here's the weird thing that I definitely do think could be a bug:

Changing the length of an array outlet to 0 does not seem to trigger an update callback on downstream modules. So triggering "ClearAll" on the StoreArrays module does not result in downstream modules being notified that the values have been cleared.

[nay-seven]

@hesspet : here a lighter simple solution
Download

@ynohtna : can you give us a patch to illustrate your question please ?

[hesspet]

@nay-seven: Yes, that's more elegant.

My final solution is working now. I do a store and a get at the same time. Maybe I change it later on to your solution.

Tnx again!

Peter