Having done a fair amount of investigation today (whilst at work - oops!) I reckon that first off the scripting thing will simply allow you to write PD (non DSP) externals in python. After that I will look into how much more of the PD internals you can expose. This is still a fair amount of work to make user friendly and useable - however it will allow you to create fairly interesting control objects pretty much on the fly for a patch.
cheers
mark
-----Original Message----- From: root@bestweb.net [mailto:root@bestweb.net]On Behalf Of Larry Troxler Sent: 26 February 2002 00:18 To: Thomas Grill Cc: Pd-List; mark@junklight.com Subject: Re: AW: [PD] Scripting
What concerns dsp and existing pd objects i thought that it would be desirable in the future to be able to use this (with a fairly complex glue layer and some restrictions for the usable objects, of course) inside the python code as well. Maybe, pd classes could thus be mangled into python classes and used within the script. Naturally, this would impose a lot of design and coding work (if it is possible after all...)
greetings, Thomas
Just 2$ from my own limited experience so far,
What I with my experimental scheme extern, is that I do not yet miss these features (the lack of DSP objects and the lack of the ability to embed existing PD objects into the script).
Of course it all depends on your goals. In my case, I was simply looking for a method to ease the rats-nest of interconnections, and be able to quickly come up with "one-off" (i.e. composition specific) objects that help with this. In other words my purpose was more to give me a conventional/linear framework for building constructs to simplify my patches, rather than something more complete. In other words, for probably 10% of the effort that would be needed for the full solution, It doesn't bother me that I have to interconnect my scheme object to seperate DSP boxes to do what I need.
But I don't mean to say that what you are proposing wouldn't be great indeed!
Larry