Hi,
At RjDj we're interfacing Pd with Python using a wrapper I wrote, and one of the developers had this bug report when he tried it with Pd-extended (not realising that there is another type of Pd).
We're going to be using vanilla only, but I thought I should send a heads-up to the list anyway incase someone else runs into this Pd-extended weirdness.
The bug report below doesn't happen on Pd-vanilla at all. See the attached files to try and replicate it. Basically it seems like Pd-extended is crashing, or not starting at all with Pd default command line args.
Best,
Chris.
----- Forwarded message from Martin Roth -----
From: Martin Roth To: Chris McCormick chrism@rjdj.me, Resent-Date: Thu, 09 Jul 2009 17:31:56 +0200
I have trouble being able to load pd from the command line with the -open flag, pointing at the relevant scene. That is, pd seems to load normally (though strangely showing only the console and not the editor gui). There is the following command line output: tk scaling is 0.999016715831 Pt_Start() called
When I try to send the patch a message from python (to a netreceive object in pd), then python (using Chris' PdSend object) then I receive the following error:
pdSend.Send("hello")
error: uncaptured python exception, closing channel <Pd.PdSend connected 127.0.0.1:30321 at 0x6f648> (<class 'socket.error'>:(32, 'Broken pipe') [/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/asynchat.py|initiate_send|219] [/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/asyncore.py|send|331] [/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/asyncore.py|send|331])
On the other hand, if I open PD and load the scene manually, then everything works fine. Thoughts? -Martin