Hi Thomas,<br><br>Here's what PD says when I start it with the -verbose flag and open a pyext example patch:<br><br>tried C:\\Program Files\\pd\\doc\\examples\\py\\examples\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\pyext.dll and failed
<br>tried C:\\Program Files\\pd\\patches\\library\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\granules\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\bp-beats\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\analog-synth\\pyext.dll and failed
<br>tried C:\\Program Files\\pd\\patches\\looper\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\scripts\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\extra\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\examples\\pyext\\pyext.dll and failed
<br>tried C:\\Program Files\\pd\\patches\\pyext\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\library\\pyext\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\granules\\pyext\\pyext.dll and failed
<br>tried C:\\Program Files\\pd\\patches\\bp-beats\\pyext\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\analog-synth\\pyext\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\patches\\looper\\pyext\\pyext.dll and failed
<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\scripts\\pyext\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\extra\\pyext\\pyext.dll and failed<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\examples\\pyext.pd and failed
<br>tried C:\\Program Files\\pd\\patches\\pyext.pd and failed<br>tried C:\\Program Files\\pd\\patches\\library\\pyext.pd and failed<br>tried C:\\Program Files\\pd\\patches\\granules\\pyext.pd and failed<br>tried C:\\Program Files\\pd\\patches\\bp-beats\\pyext.pd and failed
<br>tried C:\\Program Files\\pd\\patches\\analog-synth\\pyext.pd and failed<br>tried C:\\Program Files\\pd\\patches\\looper\\pyext.pd and failed<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\scripts\\pyext.pd and failed
<br>tried C:\\Program Files\\pd\\extra\\pyext.pd and failed<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\examples\\pyext.pat and failed<br>tried C:\\Program Files\\pd\\patches\\pyext.pat and failed<br>tried C:\\Program Files\\pd\\patches\\library\\pyext.pat and failed
<br>tried C:\\Program Files\\pd\\patches\\granules\\pyext.pat and failed<br>tried C:\\Program Files\\pd\\patches\\bp-beats\\pyext.pat and failed<br>tried C:\\Program Files\\pd\\patches\\analog-synth\\pyext.pat and failed<br>
tried C:\\Program Files\\pd\\patches\\looper\\pyext.pat and failed<br>tried C:\\Program Files\\pd\\doc\\examples\\py\\scripts\\pyext.pat and failed<br>tried C:\\Program Files\\pd\\extra\\pyext.pat and failed<br> pyext simple ex3
<br>... couldn't create<br><br>By "couldn't create", it means the [pyext] object fails to start, and has a dashed border around it - pd doesn't recognize the name.<br><br>A search of my directory tree couldn't find any files called pyext.*, so not only are they not in the correct path, they don't exist at all on my machine. However, there is a
py.dll binary in pd/extra/, and pd sees it just fine. Could it be that pyext.dll failed to compile from the CVS sources?<br><br>As far as "doesn't work correctly," when I use an example patch with [py], changing the input to the [py] object doesn't have any effect on the output. Quite simply, it does nothing - it doesn't work.
<br><br>Thanks again for all your help!<br><br>David<br><br>ps Yes, I'm trying to get this set up on my WinXP partition - I've had too many Linux headaches for the past couple of weeks and am taking a break before plunging back in...
<br><br><div><span class="gmail_quote">On 2/17/06, <b class="gmail_sendername">Thomas Grill</b> <<a href="mailto:gr@grrrr.org">gr@grrrr.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi David,<br>i'm cc'ing this to the list - there might be others having the same<br>problem or people who can help you better than me.<br><br>> Hm, I tried adding the script directory to my PD paths, and it didn't<br>> work, then I restarted PD and it didn't work, then I tried copying all
<br>> the scripts to the "examples" directory (where the example patches I<br>> was trying are located) and it still didn't work.<br>It would be helpful to have more detailed information, like what exactly
<br>doesn't work under which circumstances. Try starting PD with the<br>-verbose flag and try to provide a walk-through so that i can reproduce<br>your situation.<br>> Again, [py] will load as an object but [pyext] will not, not even
<br>> typed in an object box by itself - it's like pd doesn't recognize the<br>> symbol I typed, like I just typed junk.<br>According to the error output you sent me, this doesn't seem to be the<br>case. The pyext object is created ok, only the Python scripts can't be
<br>found.<br>> The [py] object never complained about finding the scripts before, but<br>> they didn't seem to be working correctly either...<br>What exactly isn't working correctly?<br>><br>> I'm actually using
0.2.1 from the pd-extended dist, copied into the<br>> appropriate folders of my 0.39-2 release. But all of these things<br>> happen exactly this way using pd-extended as well.<br>><br>The console output says that you are using version
0.2.0. So, if you are<br>really having 0.2.1 in your PD package, then there's obviously another<br>py/pyext binary somewhere in the path which is loaded beforehand.<br><br>best greetings,<br>Thomas<br><br>><br>> On 2/16/06, *Thomas Grill* <
<a href="mailto:gr@grrrr.org">gr@grrrr.org</a> <mailto:<a href="mailto:gr@grrrr.org">gr@grrrr.org</a>>> wrote:<br>><br>> Hi David,<br>> pyext seems to run fine on your machine, only the Python scripts can't
<br>> be found.<br>> They have to be either in the same directory as the current patcher or<br>> in the PD load path (where also the externals are found) which can be<br>> set in the "Path..." menu dialog.
<br>><br>> What i find a bit strange is that according to your console printout<br>> [pym] wants to be loaded and gives an error. If i'm not mistaken this<br>> is only included in pyext >= 0.2.1
which is the cvs version, not the<br>> packaged one that you a using. Do you have a mixup of versions? Well,<br>> first try to fix the path and let's see if pym is ok, or not.<br>><br>> best greetings,
<br>> Thomas<br>><br>> Am 16.02.2006 um 06:52 schrieb david golightly:<br>><br>> > Hi Thomas,<br>> ><br>> > Hope I'm not bothering you here, just wanted to make sure I'm doing
<br>> > things correctly... are you still maintaining py/pyext? I got the<br>> > most recent WinXP binaries from your website as well as the<br>> > pd-extended distro & there doesn't seem to be any
pyext.dll or<br>> > pyext.py file - although the example patches use [pyext], this<br>> > module/object fails to load - same with [pym] (although [py]<br>> will at<br>> > least load, but doesn't work at all). Am I missing something here?
<br>> > Using PD 0.39-2 and Python 2.4.2, I get messages like this in the pd<br>> > console when I load the example patches:<br>> ><br>> > ------------------------------------------------
<br>> > py/pyext 0.2.0 - python script objects<br>> > (C)2002-2005 Thomas Grill - <a href="http://grrrr.org/ext">http://grrrr.org/ext</a><br>> ><br>> > using Python 2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC
v.1310 32 bit<br>> > (Intel)]<br>> > ------------------------------------------------<br>> ><br>> > ImportError: No module named simple<br>> > pyext simple ex1<br>> > ... couldn't create
<br>> > ImportError: No module named sendrecv<br>> > pyext sendrecv ex1 he hu<br>> > ... couldn't create<br>> > pym 2 *<br>> > ... couldn't create<br>> ><br>> >
<br>> > By the way, thanks for doing all this work! These patches are<br>> > brilliant. Once I get these externs running this'll be fantastic<br>> > addition to my pd arsenal. A pity more pd'ers don't bother to
<br>> learn a<br>> > bit of python - using these modules, externs are much easier &<br>> quicker<br>> > to write than either using C or native pd abstractions.<br>> ><br>> > Thanks,
<br>> ><br>> > David<br>> ><br>><br>><br><br>--<br>Thomas Grill<br><a href="http://grrrr.org">http://grrrr.org</a><br><br><br></blockquote></div><br>