Hi,
The short version: I fresh-installed Pd Extended into the default location (C:\Program Files\pd) and I get:
cyclone: can't load library zexy: can't load library creb: can't load library ....
and so on for EVERY library except Gem. The strange thing is that Gem does load, and it is located in pd/extra just like all other libraries. This is really crazy isn't it?
What can be wrong?
The long version:
I had already installed Pd Extended and it used to work fine. It was installed in an "unusual" location: "D:/programmi/pd_extended", where "programmi" is the italian word for "programs" but it is _not_ the default directory for programs in my computer (who speaks spanish, not italian). When I installed it, I had to manually modify the "pd-settings.reg" file that adds the libraries to startup, because it uses the wrong location for the registry keys (this has nothing to do with the path where Pd is installed). After that, I had Pd Extended working fine and loading all libraries.
Also, I have Pd Vanilla installed in another directory, "D:\programmi\pd". I run it using the "-noprefs" option, because otherwise, it would (try to) load the libraries from pd Extended.
Today, misteriously and without (apparently) touching anything, Pd Extended stopped working, that is it started giving me "cannot load library" messages. I tried uninstalling and reinstalling it to the same directory with no luck. So I uninstalled and reinstalled again, this time to the default location C:\Program Files\pd (note disk C which is where the OS is installed, and "Program Files" is the actual system Program Files directory, which is displayed as "Archivos de Programa").
However the result is the same: "cannot load library" for all libraries except Gem. The Gem it is loading is actually the one installed inside the C:\Program Files\pd\extra\Gem directory, which is the same path where all other libraries are located too. I know it because if I rename that gem.dll file, it won't load.
Please help!
thanks m.
Errata corrige: there is one other library that does load, it is "vbap".
And one thing it has in common with Gem is that its folder contains a dll file with the same name, namely "vbap.dll". Seems like all other libraries don't (though I haven't checked _all_ of them).
So I guess I should add the other directories to path rather than to startup? The very strange thing is that it used to work up to a few days ago however.......
Matteo Sisti Sette escribió:
Hi,
The short version: I fresh-installed Pd Extended into the default location (C:\Program Files\pd) and I get:
cyclone: can't load library zexy: can't load library creb: can't load library ....
and so on for EVERY library except Gem. The strange thing is that Gem does load, and it is located in pd/extra just like all other libraries. This is really crazy isn't it?
What can be wrong?
The long version:
I had already installed Pd Extended and it used to work fine. It was installed in an "unusual" location: "D:/programmi/pd_extended", where "programmi" is the italian word for "programs" but it is _not_ the default directory for programs in my computer (who speaks spanish, not italian). When I installed it, I had to manually modify the "pd-settings.reg" file that adds the libraries to startup, because it uses the wrong location for the registry keys (this has nothing to do with the path where Pd is installed). After that, I had Pd Extended working fine and loading all libraries.
Also, I have Pd Vanilla installed in another directory, "D:\programmi\pd". I run it using the "-noprefs" option, because otherwise, it would (try to) load the libraries from pd Extended.
Today, misteriously and without (apparently) touching anything, Pd Extended stopped working, that is it started giving me "cannot load library" messages. I tried uninstalling and reinstalling it to the same directory with no luck. So I uninstalled and reinstalled again, this time to the default location C:\Program Files\pd (note disk C which is where the OS is installed, and "Program Files" is the actual system Program Files directory, which is displayed as "Archivos de Programa").
However the result is the same: "cannot load library" for all libraries except Gem. The Gem it is loading is actually the one installed inside the C:\Program Files\pd\extra\Gem directory, which is the same path where all other libraries are located too. I know it because if I rename that gem.dll file, it won't load.
Please help!
thanks m.
Sounds like 'libdir' isn't being loaded first. Try reseting your
registry settings with the included pdsettings.reg file.
.hc
On Mar 7, 2010, at 1:07 PM, Matteo Sisti Sette wrote:
Errata corrige: there is one other library that does load, it is
"vbap".And one thing it has in common with Gem is that its folder contains
a dll file with the same name, namely "vbap.dll". Seems like all
other libraries don't (though I haven't checked _all_ of them).So I guess I should add the other directories to path rather than to
startup? The very strange thing is that it used to work up to a few days ago
however.......Matteo Sisti Sette escribió:
Hi, The short version: I fresh-installed Pd Extended into the default
location (C:\Program Files\pd) and I get: cyclone: can't load library zexy: can't load library creb: can't load library .... and so on for EVERY library except Gem. The strange thing is that
Gem does load, and it is located in pd/extra just like all other
libraries. This is really crazy isn't it? What can be wrong? The long version: I had already installed Pd Extended and it used to work fine. It
was installed in an "unusual" location: "D:/programmi/pd_extended",
where "programmi" is the italian word for "programs" but it is
_not_ the default directory for programs in my computer (who speaks
spanish, not italian). When I installed it, I had to manually modify the "pd-settings.reg"
file that adds the libraries to startup, because it uses the wrong
location for the registry keys (this has nothing to do with the
path where Pd is installed). After that, I had Pd Extended working
fine and loading all libraries. Also, I have Pd Vanilla installed in another directory, "D: \programmi\pd". I run it using the "-noprefs" option, because
otherwise, it would (try to) load the libraries from pd Extended. Today, misteriously and without (apparently) touching anything, Pd
Extended stopped working, that is it started giving me "cannot load
library" messages. I tried uninstalling and reinstalling it to the same directory with
no luck. So I uninstalled and reinstalled again, this time to the
default location C:\Program Files\pd (note disk C which is where
the OS is installed, and "Program Files" is the actual system
Program Files directory, which is displayed as "Archivos de
Programa"). However the result is the same: "cannot load library" for all
libraries except Gem. The Gem it is loading is actually the one installed inside the C: \Program Files\pd\extra\Gem directory, which is the same path where
all other libraries are located too. I know it because if I rename
that gem.dll file, it won't load. Please help! thanks m.-- Matteo Sisti Sette matteosistisette@gmail.com http://www.matteosistisette.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
¡El pueblo unido jamás será vencido!
Ok so I am trying to add all the paths to Pd Extended libraries. I would hate to have to add them as absolute path, such as "C:\Program Files\pd\extra\zexy", or even "%programfiles%\pd\extra\zexy", because then I can't move or the Pd folder without breaking it.
How can I add them as relative to Pd's paths? Is it possible at all? I tried with "..\extra\zexy" and "extra\zexy" but neither works.
(zexy is only an example obviously, the same holds for all other libraries)
thanks m.
Matteo Sisti Sette escribió:
Hi,
The short version: I fresh-installed Pd Extended into the default location (C:\Program Files\pd) and I get:
cyclone: can't load library zexy: can't load library creb: can't load library ....
and so on for EVERY library except Gem. The strange thing is that Gem does load, and it is located in pd/extra just like all other libraries. This is really crazy isn't it?
What can be wrong?
The long version:
I had already installed Pd Extended and it used to work fine. It was installed in an "unusual" location: "D:/programmi/pd_extended", where "programmi" is the italian word for "programs" but it is _not_ the default directory for programs in my computer (who speaks spanish, not italian). When I installed it, I had to manually modify the "pd-settings.reg" file that adds the libraries to startup, because it uses the wrong location for the registry keys (this has nothing to do with the path where Pd is installed). After that, I had Pd Extended working fine and loading all libraries.
Also, I have Pd Vanilla installed in another directory, "D:\programmi\pd". I run it using the "-noprefs" option, because otherwise, it would (try to) load the libraries from pd Extended.
Today, misteriously and without (apparently) touching anything, Pd Extended stopped working, that is it started giving me "cannot load library" messages. I tried uninstalling and reinstalling it to the same directory with no luck. So I uninstalled and reinstalled again, this time to the default location C:\Program Files\pd (note disk C which is where the OS is installed, and "Program Files" is the actual system Program Files directory, which is displayed as "Archivos de Programa").
However the result is the same: "cannot load library" for all libraries except Gem. The Gem it is loading is actually the one installed inside the C:\Program Files\pd\extra\Gem directory, which is the same path where all other libraries are located too. I know it because if I rename that gem.dll file, it won't load.
Please help!
thanks m.
On 2010-03-07 19:30, Matteo Sisti Sette wrote:
What can be wrong?
seems like you are missing the libdir loader. Pd-extended compiles libraries as libdirs, which cannot be loaded "as libraries" by Pd-vanilla (nor by Pd-extended i think): in order to load them as a library,l you have to use a special loader "libdir", which of course has to be loaded before trying to load any libdirized library.
libloadliblidirlib.
or you could us explicit namespaces, like [zexy/abs~]; but of course, then your patch won't work anymore with nonlibdirized libraries. (or libdirized libs layed out in other libdirectories)
fgamsrd IOhannes
IOhannes m zmoelnig escribió:
seems like you are missing the libdir loader. Pd-extended compiles libraries as libdirs, [...]
Oh yes! Libdir is indeed the first item in the "loadlib" list - i.e. it is "loadlib1"="libdir" in the registry, so the mistery is why libdir doesn't [didn't] load in the first place (I do, and did, have a libdir.dll file in the extra folder).
Now two strange things:
like it was before (I had replaced all "loadlib" with "path" as a workaround, to have all externals available though not pre-loaded), and surprise surprise, now everything works: libdir loads and all subsequent libs load
"loadlib" entries _and_ the "nloadlib" entry); however, when I run Pd, it still loads all libraries, and they appear in the "startup" list. If I modify the list from Pd and click "Apply", then all keys in the registry are created again.
So, how does Pd "remember" the startup list after I delete it from the registry? Seems like it saves it somewhere else. Where?? Or is it the registry itself that has some sort of "cache"?
Regarding mistrey (1), there is an error in the pd-settings.reg file (as it "ships" with Pd Extended), that the line just before "loadlib1"="libdir" reads "flags"=" where it should read "flags"=""
However I had fixed it already, so it doesn't quite explain the fact that libdir didn't load......
Which version of Pd-extended are you using?
.hc
On Mar 8, 2010, at 5:35 AM, Matteo Sisti Sette wrote:
IOhannes m zmoelnig escribió:
seems like you are missing the libdir loader. Pd-extended compiles libraries as libdirs, [...]
Oh yes! Libdir is indeed the first item in the "loadlib" list - i.e. it is
"loadlib1"="libdir" in the registry, so the mistery is why libdir
doesn't [didn't] load in the first place (I do, and did, have a
libdir.dll file in the extra folder).Now two strange things:
- I manually re-edited the .reg file, apparently reestablishing it
just like it was before (I had replaced all "loadlib" with "path" as
a workaround, to have all externals available though not pre- loaded), and surprise surprise, now everything works: libdir loads
and all subsequent libs load
- Now, just to try, I deleted all keys from the registry (all the
"loadlib" entries _and_ the "nloadlib" entry); however, when I run
Pd, it still loads all libraries, and they appear in the "startup"
list. If I modify the list from Pd and click "Apply", then all keys
in the registry are created again.So, how does Pd "remember" the startup list after I delete it from
the registry? Seems like it saves it somewhere else. Where?? Or is
it the registry itself that has some sort of "cache"?Regarding mistrey (1), there is an error in the pd-settings.reg file
(as it "ships" with Pd Extended), that the line just before
"loadlib1"="libdir" reads "flags"=" where it should read "flags"=""However I had fixed it already, so it doesn't quite explain the fact
that libdir didn't load......-- Matteo Sisti Sette matteosistisette@gmail.com http://www.matteosistisette.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity." -John Gilmore