About this project
I want to implement and refine an API to provide streamlined discovery of Open Sound Control applications and inter application communication.
Inspiration for this project comes from my participation in the Monome and NoisePages community. One beautiful aspect of OSC is that it is intentionally left open. It provides enough to construct meaningful messages and tries not to provide much else. The downside to this are differences in message formats that arise out of necessity.
Wouldn't it be grand if your OSC patches spoke to one another without so much fiddling with low level details? Don't you want to reclaim a LITTLE bit of that MIDI 'plug and play' vibe?
What needs to be done
I already have a spec worked out. I am sure that I will have to make changes, but not too many. The real work is making a convincing implementation.
What is the money for?
$1800 would afford two months of focused (almost exclusive) work on this project. So, Food, lights, and a place to keep well-lit food. Anything beyond goes to extend the time i can devote to the project and allows me to bring other people in for pay.
A word about libmapper - http://www.idmil.org/software/libmapper
After looking libmapper over, I still believe there is good reason to continue development of crosstalk. Currently, libmapper only supports single argument osc messages. IDMIL plans to add support for more messages as time passes, but I hope to provide broader message format at an early stage. I also believe that built in support for libmapper is completely attainable, though not in early releases.
Have a question?
If the info above doesn't help, you can ask the project creator directly.