nnneuromodulator

Okay, I've tracked down an error in my patch to the attached object.

I wanted to translate incoming OSC messages so that the "/" characters were all replaced by " " (blank spaces), so that I could then use "route" objects to sort them.

The problem is in my use of [thresh], to recombine the string after it goes through the [if]. It works fine most of the time, but if I get two separate OSC messages within the threshold interval, they get combined into one message.

I need to keep each incoming OSC message distinct. The OSC messages are not of equal length. How else could I do this?

Okay, I've tracked down an error in my patch to the attached object.  

The problem is in my use of [thresh], to recombine the string after it goes through the [if].  It works fine most of the time, but if I get two separate OSC messages within the threshold interval, they get combined into one message.  

I need to keep each incoming OSC message distinct.  The OSC messages are not of equal length.  How else could I do this?

another-way-to-do-this

There is an object which handles OSC message strings. Use [osc-route] in

your application, it's very easy to use. you can download the object at

Also download the objects [OpenSoundControl] and [osc-unroute] they may

> Okay, I've tracked down an error in my patch to the attached object.

> I wanted to translate incoming OSC messages so that the "/" characters

> were all replaced by " " (blank spaces), so that I could then use "route"

> The problem is in my use of [thresh], to recombine the string after it

> goes through the [if]. It works fine most of the time, but if I get two

> separate OSC messages within the threshold interval, they get combined into

> I need to keep each incoming OSC message distinct. The OSC messages are

> not of equal length. How else could I do this?

> #P newex 50 135 141 196617 if $i1 == 47 then 32 else $i1;

> #P newex 50 49 86 196617 udpreceive 8000;

Hello Adam,
There is an object which handles OSC message strings. Use [osc-route] in
your application, it's very easy to use. you can download the object at
http://cnmat.berkeley.edu/downloads .
Also download the objects [OpenSoundControl] and [osc-unroute] they may
become handy.
cheers,
Jeroen.

> Okay, I've tracked down an error in my patch to the attached object.
>
> I wanted to translate incoming OSC messages so that the "/" characters
> were all replaced by " " (blank spaces), so that I could then use "route"
> objects to sort them.
>
> The problem is in my use of [thresh], to recombine the string after it
> goes through the [if].  It works fine most of the time, but if I get two
> separate OSC messages within the threshold interval, they get combined into
> one message.
>
> I need to keep each incoming OSC message distinct.  The OSC messages are
> not of equal length.  How else could I do this?
>
> Appreciate the help.
>
> max v2;
> #N vpatcher 337 117 937 517;
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P newex 50 226 64 196617 fromsymbol;
> #P newex 50 180 49 196617 route 32;
> #P newex 50 253 44 196617 s OSCin;
> #P newex 50 203 40 196617 itoa;
> #P newex 50 135 141 196617 if $i1 == 47 then 32 else $i1;
> #P newex 50 114 25 196617 iter;
> #P newex 50 92 40 196617 atoi;
> #P newex 50 156 48 196617 thresh 1;
> #P newex 50 71 51 196617 tosymbol;
> #P newex 50 49 86 196617 udpreceive 8000;
> #P connect 0 0 1 0;
> #P connect 1 0 3 0;
> #P connect 3 0 4 0;
> #P connect 4 0 5 0;
> #P connect 5 0 2 0;
> #P connect 2 0 8 0;
> #P connect 8 0 6 0;
> #P connect 6 0 9 0;
> #P connect 9 0 7 0;
> #P pop;
>
>
>
>
>

Check out regexp - it makes these sort of substitutions really easy.

Also, if it's just routing you're after, there's osc-route from CNMAT, 

that has the added bonus of pattern matching magic:

> I wanted to translate incoming OSC messages so that the "/"

> characters were all replaced by " " (blank spaces), so that I could

> The problem is in my use of [thresh], to recombine the string after

> it goes through the [if]. It works fine most of the time, but if I

> get two separate OSC messages within the threshold interval, they get

> I need to keep each incoming OSC message distinct. The OSC messages

> are not of equal length. How else could I do this?

Check out regexp - it makes these sort of substitutions really easy.
like:

Also, if it's just routing you're after, there's osc-route from CNMAT, 
that has the added bonus of pattern matching magic:

Adam Barnett wrote:
> Okay, I've tracked down an error in my patch to the attached object.
>
>
> I wanted to translate incoming OSC messages so that the "/"
> characters were all replaced by " " (blank spaces), so that I could
> then use "route" objects to sort them.
>
> The problem is in my use of [thresh], to recombine the string after
> it goes through the [if].  It works fine most of the time, but if I
> get two separate OSC messages within the threshold interval, they get
> combined into one message.
>
> I need to keep each incoming OSC message distinct.  The OSC messages
> are not of equal length.  How else could I do this?
>
> Appreciate the help.
>
> max v2;


there is the dedicated [osc-route] object available from CNMAT to 

to cut a string (ahem, 'symbol') at a specific delimiter, i ported the 

c-string function [strtok] to a max external: 

http://www.cplusplus.com/reference/clibrary/cstring/strtok.html

as for simple substitutions there's also the stock [substitute] 

there is the dedicated [osc-route] object available from CNMAT to  
route using slash-delimited addresses.

to cut a string (ahem, 'symbol') at a specific delimiter, i ported the  
c-string function [strtok] to a max external: http://www.jasch.ch/dl
http://www.cplusplus.com/reference/clibrary/cstring/strtok.html

as for simple substitutions there's also the stock [substitute]  
object, see patch below

Ah, thank you. [substitute] just did the trick. I don't want to mess about with [osc-route] at this point, since everything downwind in my patch would need replacing, but next time...

I have an etiquette question, since I'm new to mailing list-type forums. Is it customary to thank people for their help, and/or update posts when a problem has been solved, or is that considered unnecessary noise?

Ah, thank you.  [substitute] just did the trick.  I don't want to mess about with [osc-route] at this point, since everything downwind in my patch would need replacing, but next time...

I have an etiquette question, since I'm new to mailing list-type forums.  Is it customary to thank people for their help, and/or update posts when a problem has been solved, or is that considered unnecessary noise?

On Sat, Apr 12, 2008 at 11:23 AM, Adam Barnett wrote:

> I have an etiquette question, since I'm new to mailing list-type forums. Is it customary to thank people for their help, and/or update posts when a problem has been solved, or is that considered unnecessary noise?

It's good to thank people. Makes 'em more willing to help next time.

Plus it's always good to get verification that a suggested solution

On Sat, Apr 12, 2008 at 11:23 AM, Adam Barnett wrote:
>
>  I have an etiquette question, since I'm new to mailing list-type forums.  Is it customary to thank people for their help, and/or update posts when a problem has been solved, or is that considered unnecessary noise?

It's good to thank people. Makes 'em more willing to help next time.
Plus it's always good to get verification that a suggested solution
actually works.

Quote: Adam Murray wrote on Sat, 12 April 2008 21:13

----------------------------------------------------

> On Sat, Apr 12, 2008 at 11:23 AM, Adam Barnett wrote:

> > I have an etiquette question, since I'm new to mailing list-type forums. Is it customary to thank people for their help, and/or update posts when a problem has been solved, or is that considered unnecessary noise?

> It's good to thank people. Makes 'em more willing to help next time.

> Plus it's always good to get verification that a suggested solution

Personally, when I have spent 5, 10, 15 minutes of my time to try answer a question and post an example patch, I like to know if it helped or not. When I get no verification/reply/thank you I will be less motivated to reply to a question by this person again.

Even if the patch/answer posted makes no sense at all, reply and explain why. 9 out of 10 times it is just because the original question was not phrased clearly enough. So, phrase questions carefully and be appreciative for any help offered to you.

Quote: Adam Murray wrote on Sat, 12 April 2008 21:13
----------------------------------------------------
> On Sat, Apr 12, 2008 at 11:23 AM, Adam Barnett wrote:
> >
> >  I have an etiquette question, since I'm new to mailing list-type forums.  Is it customary to thank people for their help, and/or update posts when a problem has been solved, or is that considered unnecessary noise?
>
> It's good to thank people. Makes 'em more willing to help next time.
> Plus it's always good to get verification that a suggested solution
> actually works.
>
> -the other Adam
>

I agree with mister Murray. 
Personally, when I have spent 5, 10, 15 minutes of my time to try answer a question and post an example patch, I like to know if it helped or not. When I get no verification/reply/thank you I will be less motivated to reply to a question by this person again.

another way to do this?