On Fri, 15 Oct 2004, Frank Barknecht wrote:
Great idea, but again, why has this to be done with OSC ? I am very much for OSC compatibility of pd, but we should not change the style of the pd language for that. I think this would be possible to be implemented in pd messages instead of OSC messages. Just replace the "/" by a " ".
You miss one central feature of OSC: pattern matching. This is very useful, as I can access lots of values at the same time:
"/sequencer/volume* 100" will set all 64 volume sliders to 100.
I see, but that can be solved. "route" could be changed to do pattern matching.
That is a good example of what I actually wanted to say, I think that it is important to do this the "pd way". Extend the language of pd where parts are missing. This is the only way to keep the "pd language" compact and consistent.
Guenter