Hey all,

I'm hoping for some assistance from the forum to add clarity to my thinking as much as technical assistance here:

This is the situation;
I'm part of a laptop improvisation ensemble with currently pd(me), chuck (or whatever the caps are), Max and Renoise as the apps.

We've decided to get into some OSC shared parameter stuff which has some interesting and fun audio results.

Now the problem I'm having is in trying to tame the sheer amount of OSC messages I'm receiving. We've taken a firm decision that we will not define our namespaces beforehand as this will limit what we will send, and as it's improv-based we want to be able to decide there and then what we are doing.

So...
What I think I'm after is some method of collecting and being able to visualise the incoming OSC messages so that appear in a list of some kind (like [playlist] or [entry] but only once, with a new entry appearing for a new OSC message in the list, rather than the huge wodge of virtually unreadable OSC headers that are currently streaming down my terminal window at 80mph.

Then I would like to click on an item from the list, extract the integers or whatever at the end of the OSC string and route them to wherever the bejeezus I want to with [splitfilename] or some such object(s).

But I think it's the 1st problem that is the immediate concern.

Any thoughts, tips, tricks, or visions appreciated.

Very best wishes,

Julian

I don't know if there's a better way to do this, but here is a way that takes advantage of using symbols instead of numerical indices for [coll]. It takes incoming OSC messages and uses the address as the index. If it has received a message from that address before, it updates it; otherwise, it makes a new entry into [coll]. Then, it just clears [entry] and dumps the [coll] into it.

http://www.pdpatchrepo.info/hurleur/OSC-moniter.mmb.pd

Hey Maelstorm,

Wow, that is really very good indeed. I'm having a very quick test of it now but will explore more properly in the morning and reply in full.

Many thanks and big props,

Julian

Hello again,

Apologies for the delay in responding...

I have discovered some serious looking tcl errors with the use of [entry] on my install. I had been feeling a bit smug as I finally had installed Pd from source. There had been occasional tcl errors but I'd just ignored them, the entry problem however was too much - so 1 forced install of the pde nightly build later and here we go. I will sort out my install problems when I have a little more time!

Well - thank you again Maelstorm (I keep wanting to write Maelstrom for some reason?), yip yip that's really good and sorts out part 1 of the issue nicely. I'm in a rehearsal for the next hour or so and will see how it goes in practice and try to figure out where to go with it all next.

Back later.

Cheers,

Julian