Greetings,

I'm having trouble with a patch I've built, which is just sending too much information at once.

I've created an abstraction to handle converting midi messages into OSC messages. In my patch, I have 16 instances of this abstraction. I need to make sure that OSC messages are sent out by only one instance of this abstraction at a time.

That is, i need to delay the output of the other instances of the abstraction until the instance previous to it has completed.

Could anybody offer me some advice on how to most readily achieve this?

Many thanks!

• Peter

could you attach a patch?
couldn't you use [trigger] and storage objects like [float] or

or whatever to order the events?

Posting the patch won't help much, as it requires particular hardware to test (256 light grid), and some amount of setup. I can describe it quickly here, however.

• There are 16 instances of 'ctleuclid'.

• ctleuclid takes in OSC messages sent out of another patch, analyzes them, and sends back out corresponding messages.

• For every press of a button on the 256 grid, ctleuclid sends out 17 messages (all staggered by ~1ms.). The first 16 messages turn off the lights on the selected column, the last message turns on the light for the selected button press.

• An example message is this:

send /box/led/set 0 0 1

---which will turn on the light for button X0Y0.

So, I need to wait for all of these 17 messages to come in before allowing OSC output on any other instance of ctleuclid.

However it is quite likely that I will press another button before this process has finished, so I need to record the OSC outputs from the other instances of ctleuclid before sending them out after the previous instance has completed its output.

I was thinking of using qlist or something similar, but I'm not totally sure how to approach this. Any help would be really appreciated.

Thanks!

Further, I have each instance of ctleuclid outputting to a different send ($0-oscreceive1 - $0-oscreceive16).

So I need to create some kind of test to see if a message has passed through, and if so, it needs to turn off the output of all other $0-oscrecieve's, and set them to just record the output, and bang it out after the previous instance has completed it's process.

Basically 'm having trouble in two places:

1. Determining if a message is coming out.

2. Recording all 17 messages each time a button is pressed, and sending them back out properly.

update_
god bless [list-drip]