[PD] seperate GUI communication protocol?
shift8
shift8 at digitrash.com
Fri Sep 9 22:57:11 CEST 2005
if your goal is simply to control pd from an external GUI while running
pd -nogui, it's pretty easy to do using OSC and your favorite language
and/or gui toolkit.
i just did this the other day with glade-2, perl,
Net::OpenSoundCountrol.
to use sends in pd for this purpose, you can just do something like
dumpOCS - symbol2list - route to drop the "/", pack,
[; $1 $2{
On Fri, 2005-09-09 at 19:05 +0200, Thomas Grill wrote:
> >Out of curiousity I just had a look at this document:
> >http://puredata.info/community/projects/convention04/lectures/tk-grill/
> >
> >This seems to be exactly what I need (with or without Python wrapper).
> >Why is dyn~ better?
> >
> >
> >
> It's not that dyn~ is better, it's just different - it provides an easy
> way for in-patcher scripting, but for that it internally uses the
> current m_pd.h API.
> The dyn API is far more general, it is a proposal for a C interface to
> replace this current PD API, but at the moment it's not integrated into
> the PD kernel, therefore needing much more resources than necessary.
> This is ok for smaller applications but not for larger ones, as a
> replacement for a patcher system would be.
> However, you are welcome to use it and i'm happy about any feedback.
>
> best greetings,
> Thomas
>
>
> _______________________________________________
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>
--
More information about the Pd-list
mailing list