PDA

View Full Version : Route to First of Many Duplicates



piqant
12-08-2010, 05:58 PM
Hi Everyone,

I am trying to OSC route a button press to the first argument in a series of duplicated arguments and am having difficulty.

Example Scenario:


/128/press (receiving, has duplicated button messages)
0 (press demuxed)
0 (column 1)
0 (button)
0->0 OSC Routing -> D -> /128/led_col 0, 255 (works)
0->1
0->2
0->3
1 (unassigned)

/block/press (sending, trying to route to /128/press/0->0 above)
0 (press demuxed)
0 (column 1)
0 OSC Routing ->/128/press – > how to OSC route to 0->0 above??
1 (unassigned)

I have tried to send an OSC route to just ‘0->0’ in the /128 example, but I can’t figure out how to use the parameter tokens or arguments at /block/press/0 to isolate just the first of the duplicate velocity messages: '0->0' in /128. Is this possible?

I’ve played with various arguments and indexes via the parameters on the /block/pres/0 message, but it routes to all (0-0, 0-1, 0-2, 0-3).

Your help is appreciated. Happy Toggling!

piQant
bonzaibabybonzai@gmail.com

camille
12-08-2010, 07:40 PM
Hi piQuant,

I think you just have to create a routing with static arguments.
The rewrite address would be /128/press.
And the arguments would be 0 0 and arg[0] like in the screenshot below:

22

This way you will reconstruct the original message using the given argument that is changing.

Please let me know if this is what you want to do.

Best,
Cam

piqant
12-09-2010, 01:52 AM
Hi Cam,

Thanks for the quick reply! Using 0 0 arg[0] sends a message to all of the duplicates in the column. I restarted the routing in a new window series and had the same results.

I also tried arguments 0 0 0 arg[0] and changing the index and type for all three tokens, but the routed message fires all the duplicates. I'll keep fiddling and update us if anything else sends to just 0->0.

Thanks so much,
piQant
bonzaibabybonzai@gmail.com

camille
12-21-2010, 10:47 AM
Hey piQuant,

I'm sorry, I did not understood in the first place that you wanted to fire only one duplicate. But it has no sense, really. You could perhaps send an OSC message to a new address, and fire an event from there, that way this message would be out of the way of the duplicates.


Cam