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.
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,
I'm sure there will be some crossover as I posted these on the pd-announce list last week but I do have some recent recordings I would very much like to share:
HELOpg (Huddersfield Experimental Laptop Orchestra post-grad) recently recorded 3 Text Scores of mine and they are here:
Software is a combination of Pd and Puredyne (me), Max/MSP, Renoise and ChucK. Plus mic's, sensors and other stuff. All tracks recorded live in one take.
Here's a video of a piece for acoustic instrument and electronics which was recorded with Pat Allison on clarinet.
I'm aware that the documentation is a bit sketchy and the video is very basic; it's the first technical run through but hopefully you get the gist.
All made in Pd and I'm happy to share the patch but it's well sketchy (patch also includes an extensive list of thank you's to the various people who helped me get this thing together.
Of course, I take all the credit for any errors.
Be really good to get some feedback on all of these and I will be back asking the community if they can help me tighten up the video piece as it's an uncontrolled beast decimating my laptop in its current state. Definitely needs some serious streamloining (ho ho, just noticed the sp but I kind of like it)
Very best wishes,
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.