Marko Timlin wrote:
Hi everybody, I recently installed the newer Pd version 0.39.3-extended on a Windows XP
machine.
Now I opened a patch that was working perfectly fine with the previous Pd
version, but I got:
sendOSC ... couldn't create dumpOSC 9997 ... couldn't create range 0 0.22 300 0 0 ... couldn't create
That's a bit scary, as I worked a couple of months on that patch and now it
doesn't work.
So does anybody know why with the newer PD version there seem to be no
sendOSC, dumpOSC and range objects any more?
Any suggestions how to solve that?
load OSCx apart from that, why not use mrpeach's [packOSC], [unpackOSC],...
i think your problem might be, that some externals have left the "flatspace" and are now available "on their own", so you need to add more paths (or libdirs) to your preferences.
fgasdmr, IOhannes
Hi Iohannes, hi list members, as I worked on that patch for more than half a year I wouldn't like to change it now. It has a lot of subpatches etc. So how could I add the C:\Programme\pd\extra\oscx patch so that Pd autoloads it every time? The PD Patch menu seems to be full. And: How can I make sure that PD loads all the available patchs????
Thanks, M.T.
Marko Timlin wrote:
Hi Iohannes, hi list members, as I worked on that patch for more than half a year I wouldn't like to change it now. It has a lot of subpatches etc.
valid argument.
So how could I add the C:\Programme\pd\extra\oscx patch so that Pd autoloads it every time? The PD Patch menu seems to be full.
might be able to add it in one of the existing lines by using the colon: "/existing/path:/path/to/oscx"
in Pd-extended you might also add it to the libraries.
i am no expert in this fields (neither pd-extended nor xp), so you probably want to save your pdsettings (in the registry) before doing that.
And: How can I make sure that PD loads all the available patchs????
i am sure that you don't want to do that.
if you just want to check whether all the objects have been found correctly, you should have a look at the pdconsole output after loading and look out for "could not create" lines.
fgmadsr IOhannes
oscx should be loaded by default in Pd-0.39.3-extended as long as you
have the default preferences that were installed by the installer.
Otherwise, you can add an [import oscx] to your patch, or prefix
those objects with "oscx/" like this:
[oscx/sendOSC] [oscx/dumpOSC]
[range] is most likely the old link to maxlib scale, so you can
replace [range] with [maxlib/scale].
.hc
On Jan 17, 2008, at 8:03 AM, IOhannes m zmoelnig wrote:
Marko Timlin wrote:
Hi Iohannes, hi list members, as I worked on that patch for more than half a year I wouldn't
like to change it now. It has a lot of subpatches etc.valid argument.
So how could I add the C:\Programme\pd\extra\oscx patch so that Pd
autoloads it every time? The PD Patch menu seems to be full.might be able to add it in one of the existing lines by using the
colon: "/existing/path:/path/to/oscx"in Pd-extended you might also add it to the libraries.
i am no expert in this fields (neither pd-extended nor xp), so you probably want to save your pdsettings (in the registry) before
doing that.And: How can I make sure that PD loads all the available patchs????
i am sure that you don't want to do that.
if you just want to check whether all the objects have been found correctly, you should have a look at the pdconsole output after
loading and look out for "could not create" lines.fgmadsr IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
¡El pueblo unido jamás será vencido!
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Marko Timlin