Adam, The Paradiddle thing is really great (now if I could only get Pd to do anything I really want it to do) I've had some luck using it to make an app to control a pd patch. It would be cool to see it be able to receive as well as send.
I need to figure out more about how to use project builder before I can give much valuable feedback... It would be ideal if projectbuilder could somehow make an app that could run pd inside itself, without having to launch pd itself and could stand alone...
Thanks, Damion
"I'd appreciate feedback from interested parties on where to go next. I can imagine a variety of directions:
Builder (not my favourite direction, but a possibility)
Hi, Damion, all,
Just catching up on mail while I was away...
I believe damion romero said this around Fri, 13 Dec 2002:
Adam, The Paradiddle thing is really great (now if I could only get Pd to do anything I really want it to do) I've had some luck using it to make an app to control a pd patch. It would be cool to see it be able to receive as well as send.
I see that as being very possible down the line... the question is, how to do it *simply*? A good place to start is to describe what you want the interface to receive...
A little snag is that I don't yet know how to make an external process "listen" to Pd's own messages that are not explicitly netsend-ed.
I need to figure out more about how to use project builder before I can give much valuable feedback...
Hopefully, in this and the next couple releases, I relieve you (the developer-user) from having to know anything about ProjectBuilder (which is good, because I don't know that much about it, myself....)
It would be ideal if projectbuilder could somehow make an app that could run pd inside itself, without having to launch pd itself and could stand alone...
That would be nice. I've been thinking about how that sort of thing could happen, and I need to figure out more about making a library out of 98% percent of Pd's code. A Pd.framework working as a generalised synthesis framework? Hmmm...
But in the meantime, Paradiddle 0.2 will have the capability of auto- connecting with a Pd process, and 0.3 will (hopefully) launch Pd by itself. I can't plan any longer-term... :)
Thanks for the feedback, adam
Adam Lindsay +44(0)1524 594 537 atl@comp.lancs.ac.uk http://www.comp.lancs.ac.uk/computing/users/atl/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam, Here's an interesting one... I used the PD installer for OSX and had no problems with it, but now... This may be something I did, but I can't figure it out.. When I launch the Terminal.app and/or open any shell, alI get is the Wish Shell PD launch. I can't use the Terminal for anything but PD.
Anybody else have this problem?
Damion
Hmmm...
My first suspicion is that you might have changed a default somewhere--your default terminal is launching pd instead of your shell. It's a fun trick to use with a specific terminal setting, but annoying as a default.
Look at the menu Terminal -> Preferences... Does the first option say, "When creating a new Terminal window... Execute the default login shell"? It should be selected. A weaker possibility is that you're opening a saved .term file when you shouldn't.
If those don't work, feel free to email me off-list.
adam
On Thursday, December 19, 2002, at 11:26 PM, damion romero wrote:
Adam, Here's an interesting one... I used the PD installer for OSX and had no problems with it, but now... This may be something I did, but I can't figure it out.. When I launch the Terminal.app and/or open any shell, alI get is the Wish Shell PD launch. I can't use the Terminal for anything but PD.
Anybody else have this problem?
Damion