Hallo, enrike hat gesagt: // enrike wrote:
this wouldnt work of course, my problem is a bit different than i thought.
in my path I will have many similar objects, far more that 20 possibly. And the OSCroute object is limited to 20 addresses. So I use a normal route object to route the info to the objects.
First: You can of course use more than one OSCroute object in a patch. The last outlet of OSCroute passes on messages, that don't match. Just connect another OSCroute there:
[OSCroute /spin /vol ...] | [OSCroute /file /help]
I need to send several types of messages to that object. Lets think its a sample playr. When i play the sample i need to pass numbers like freq, voluume, etc... but at some other point i also need to pass the object the path to load the sample from the harddrive.
I would say, that a filename and a frequency value are very different things, and thus you should not use the same OSC selector for both. It feels wrong. A better approach IMO would be, to use the hierarchies possible in OSC like "/spin/freq 60" and "/spin/filename theFile.wav".
See attached patch for example implenetations of both ideas.
ciao
Frank Barknecht _ ______footils.org__