fraction

i ve explored a bit but didnt find a clear solution.

I would like to retrieve the argument of an abstraction into the argument of the object route within the patcher ( as #1)

This is kind of annoying, because route only accepts to report argument of the abstraction if there's a space before it in its own argument string. But my string to be routed doesnt have space obviously (it's osc formated), and route doesnt accept dynamic message on the fly.

I m sure there might be a go around solution, but i m burning my brain on this

test.maxpat

hi,
i ve explored a bit but didnt find a clear solution.
I would like to retrieve the argument of an abstraction into the argument of  the object route within the patcher ( as #1)

I m sure there might be a go around solution, but i m burning my brain on this
thx!


hi,
i ve explored a bit but didnt find a clear solution.
I would like to retrieve the argument of an abstraction into the argument of  the o

retrieve-argument-of-an-abstraction-in-route

There are a number of different ways to do this, but one way would to use [loadmess #] and [sprintf] to set the argument of [route] dynamically:

central government has launched a large number of schemes for the welfare of minorities.

http://sarkari-yojana.info/ 
     central   government has launched a large number of schemes for the welfare of   minorities.    

hi, thx, but that doesnt seem to work as i said, route doesnt listen dynamic #1 without a space before the #. Your loadmess is the equivalent of loading the # as an argument of the abstraction. That doesnt work.

hi, thx, but that doesnt seem to work as i said, route doesnt listen dynamic #1 without a space before the #.  Your loadmess is the equivalent of loading the # as an argument of the abstraction. That doesnt work.

Guess I'm not sure what you want to do then. You can change the route's args by input to it's non-leftmost inlets, which is what my patch does. It takes the first argument of the abstraction, and then uses that as the selector for matching...HTH further if you want to post a patch, maybe I'm missing something...

did you try your patch? because it doesnt work. Yes you can dynamically use left inlet to tell route what argument (in a basic format). But that was not my question.

I want to route an expression /blabla/#1 (where #1 is the patcher argument, a variable), for instance, in the form: 

/blabla/test x (test is an argument of the abstraction, x is the incoming value).

if you put /blabla/#1 route doesnt retrieve the abstraction argument because to understant it, it expect to have a space before the #.

if you /blabla/ #1 it works, but it's not the string to be routed. It created of course 2 outlet. 

Test it. save this one in your abstraction folder. Create a new object blabla with argument 1 for instance

did you try your patch? because it doesnt work.  Yes you can dynamically use left inlet to tell route what argument (in a basic format). But that was not my question.

I want to route an expression /blabla/#1  (where #1 is the patcher argument, a variable), for instance, in the form: 
/blabla/test x  (test is an argument of the abstraction, x is the incoming value).

if you put /blabla/#1 route doesnt retrieve the abstraction argument because to understant it,  it expect  to have a space before the #.
if you /blabla/ #1 it works, but it's not the string to be routed. It created of course 2 outlet. 

Test it. save this one in your abstraction folder. Create a new object blabla with argument 1 for instance

This may be something for cnmat's OSCRoute.

it's the same.. it cant retrieve in the matching address the argument if there's not space before the #1.

.. still exploring other go around options, but thats not really obvious

it's the same.. it cant retrieve in the matching address the argument if there's not space before the #1.
.. still exploring other go around options, but thats not really obvious

i kind of figured out but thats really a bit tricky.

Osc-route accepts in its argument "slash" something. Which is translate as /#1 in the case of abstraction argument retrieval. But if you do /#1 right away, it wont make this #1 understood by osc-route.

Then chaining multiple osc-route could therefore achieve the goal.

In this example bellow the abstraction argument of blabla will be 10 - the incoming address to be routed has the index 10 so it corresponds, and it will be routed. To really test it you have to save it in your abstraction folder, then create a new object blabla 10 in the patcher window.

It seems to work. let me know what you guys think.

Osc-route accepts in its argument "slash" something.  Which is translate as /#1 in the case of abstraction argument retrieval. But if you do /#1 right away, it wont make this #1 understood by osc-route. 

Then chaining multiple osc-route could therefore achieve the goal.

 In this example bellow the abstraction argument of blabla will be 10 - the incoming address to be routed has the index 10 so it corresponds, and it will be routed. To really test it you have to save it in your abstraction folder, then create a new object blabla 10 in the patcher window.

 It seems to work. let me know what you guys think.

maybe something with match and sprintf ? ( i ignore of OSC routing)

maybe something with match and sprintf ? ( i ignore of OSC routing)
zzz


You were almost there, due to simple oversight (wrong inlet in route):

route-path.zip

You were almost there, due to simple oversight (wrong inlet in route):


hey thanks but maybe i didnt myself clear. The problem with route is to have adress to be rooted that includes thee abstraction argument, not the variable (i mean yes too but that's easy).

route /source/#1/position /source/#2/color etc.

the problem with route is the space before # that make that impossible to work

means 
route /source/#1/position /source/#2/color etc.
the problem with route is the space before # that make that impossible to work

I see. If you want to use only builtin objects here is a way (which nb could be a bit more efficient – as route performs symbol (single int) matching vs osc-route full string pattern matching).

nice solution too, i will try also this one. As you said maybe a bit more efficient and doesnt require third party library.

nice solution too, i will try also this one. As you said maybe a bit more efficient and doesnt require third party library.
thx a a lot!

retrieve argument of an abstraction in route