Handling OSC messages – Is there a better approach than explicit route objects?

Sep 21, 2012 at 10:55am

Handling OSC messages – Is there a better approach than explicit route objects?

When handling OSC messages I’m stuck creating many route objects to filter the incoming messages. This soon gets a bit messy as indicated by this patch.

– Pasted Max Patch, click to expand. –

I’m working with the assumption that the messages can only handled with a switch case like scenario as they need to be explicitly known beforehand. However, if anyone has any suggestions for a more elegant and flexible method when filtering a large number of incoming OSC messages it would be most welcome.

#64448
Sep 21, 2012 at 12:52pm

CNMAT’s [OSC-route] might help. Plenty of references to it on this site…

#232468
Sep 21, 2012 at 1:14pm

By being based on route it pretty much uses the same method for filtering. I think I’m looking for something that doesn’t exist so I shall end my search and just use route.

#232469
Sep 21, 2012 at 6:20pm
#232470
Sep 21, 2012 at 8:40pm

I read through the paper (briefly). There’s some nice ideas but not the one I am after. It’s not a problem, I can work around it.

#232471

You must be logged in to reply to this topic.