My Gem GOPs all have OSC hooks (named by the creation argument) I also have two objects v_oscin and v_oscout that route the messages over network. I'm also using OSC names interally to control the GOPs...
I'll put up the current state of the abstractions in CVS and in pure-data later tonight.
Ben
Hallo, e skogen hat gesagt: // e skogen wrote:
i've been moving toward this type of reusable idea with my patches, and i think it's a good idea to support something like this as a group. the problem has always been creating abstractions than can mingle. everyone has varying programming styles, and with a system as open as pd, having abstractions communicate in a common way can be difficult.
one thing i've found useful is routing abstractions using OSC. each abstraction is given a name as it's first argument, and it can automatically be referenced from that point on with:
/pd/synth/(name)
so the user just needs to know how to create the abstraction and give it a name, and then set a sequencer to send OSC commands to that synth using a standard interface. this way, i can have lots of different synth abstractions controlled the same way.
That's interesting. I never thought of that, cool idea. And it even works over networks, so that two or more people could jam together.
i'll try to post some examples soon, but i guess what i'd like to see is some collaboration on a higher level framework. i'm with you on this idea frank.
I'd love to see some examples. So there are already proposed solutions for:
- persistance (state saving): pool
- communication (send messages in a unified way between patches): OSC,
send/receive,...
ciao
Frank Barknecht _ ______footils.org__
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list