Forums > MaxMSP

method of collecting incoming osc namespaces?

September 20, 2013 | 10:23 am

hey,
so what I’m trying to do is have each incoming osc namespace to a port create its own storage slot in something like coll or whatever (dict?) by itself – the process would go:

incoming, for instance /aw/tempo
is it stored already?
if yes, update
if not, create new slot (or dictionary)

Any pointers on how to go about this? I’m fairly stumped with this one.

cheers, and happy friday.


September 20, 2013 | 11:29 am

Coincidentally I just downloaded and started to check the odot library from CNMAT http://cnmat.berkeley.edu/downloads/odot . When I eyed this post. o.dict seems the thing that may help you get started at least…

Or there’s a rudimentary way with coll…

<code>

– Pasted Max Patch, click to expand. –

</code>


September 21, 2013 | 3:01 pm

hey, good lookin’ out! Been meaning to look into o. for a while now, any system that gets me into dict is worth my time, for sure.

Also, wow, was I having a brainfart there, look how simple the patching is! :) Yay.

I’m going for something along these lines – has four "presets", etc. good fun! :-D

thanks for your time, I really appreciate it. I hope this turns out to be useful for folks, I know a lot of people are using osc these days, thankfully.

<code>

– Pasted Max Patch, click to expand. –

</code>


September 21, 2013 | 6:12 pm

Be careful with the latest odot package.. o.dict has been crashing Max on my machine. 6.1.3 on mpb 10.8.4


September 22, 2013 | 12:38 pm

cheers – it still seems like o.dot is far too immense for what we need; and there we were thinking our band was "complicated", when in fact we were way vanilla.


September 22, 2013 | 1:05 pm

There is so much awesomeness in the library known as odot that I am without the words to express it. Object-oriented Sound Control.


Viewing 6 posts - 1 through 6 (of 6 total)