How to install externals, libraries, gui plug-ins, etc.
Edit: This post was originally written with Pd-extended 0.43 in mind. These days there is a nice little plugin called Deken that you can use to easily download and install most of the popular libraries in Pd. It comes bundled with recent versions of Pd-vanilla. You can still use namespaces to load up the objects for most libraries, but for some libraries like zexy that have all the objects bundled into a single file, you will still need to use [declare] to load it up.
Installing libraries and plug-ins isn't so obvious. This guide will hopefully clear up the process, and may even explain more than you need to know.
Recent changes
This first section is mainly for those upgrading to Pd-0.43 from previous versions. If you're new to Pd and are starting on 0.43, you can just skip this section and get on with loading libraries.
It use to be that installing a library was done by putting it wherever you wanted on your system and adding its path to the preferences. While this wasn't particularly difficult, it did have some problems. Recent efforts have been made to standardize this a bit so those problems can be avoided.
In Pd-extended 0.43, you can't add paths from within Pd any more like you used to. You can open the preferences and add a path, but it won't save it. This means that non-default libraries won't load on start-up any more; you have to load them from within the patch. While this sounds like a hassle, it does have the advantage that patches are much easier to share. You don't have to worry about others having different start-up settings than you. It also forces the patch to document what libraries are being used, so if an object isn't loading, you don't have to go on some crazy hunt to find out where it came from or what it's supposed to do.
Putting them in the right folder
To make sure Pd can easily find the library, you need to put them in the right folder. This is OS dependent. The following folders are your options (taken from here). I personally recommend putting them in the user-specific folders since they are likely easier to migrate when updating your OS.
Linux:
User-specific:
~/pd-externals
Global:
/usr/local/lib/pd-externals
Mac OSX
User-specific:
~/Library/Pd
Global:
/Library/Pd
Windows
User-specific:
%AppData%/Pd
Global:
%CommonProgramFiles%/Pd
Linux and OSX are pretty straight-forward. "~" means your home folder.
Windows is a bit trickier. %AppData% and %CommonProgramFiles% are environment variables that contain specific directories. What the exact directory is depends on which version of Windows you are on. You can find out what it is by opening up the command line and typing this:
echo %AppData%
You might end up with something like C:\Users\username\AppData\Roaming or C:\Documentes and Settings\username\Application Data. Also, to see it in the file browser, you might need to show hidden files. At any rate, once you find the directory, create a Pd folder if there isn't one, and put your library, objects, or plug-ins there.
Loading whole libraries
To load a library you have a few options. The one that works on both vanilla and extended is to use [declare -stdpath libraryname]. The libraryname is the name of the folder that all the objects/abstractions are in.
[declare] doesn't always work as expected in abstractions, though. In Pd-extended, you can also use [import], which works well in abstractions. I have found that sometimes it doesn't work with libraries of abstractions that don't have a meta file, though. But that can be fixed by just making one. Simply create an empty Pd patch and save it as libraryname-meta.pd in the library's folder. That's all the meta patch is.
A third option (also Pd-extended only) is to use [path]. This is new to Pd-extended 0.43 and works similarly to [declare]. I haven't needed it, yet. But it's there.
Once the library is loaded, you should be able to load an object or abstraction just by creating it by name.
Loading objects or abstractions using namespaces
While this method means a little more typing, it is also the safest, and it makes it easier to find out what objects are from which library. The way you do it is add the library name (i.e. the namespace) to the beginning of the object when you call it, like this:
[zexy/multiplex~] <-- load the [multiplex~] object from zexy
[cyclone/comb~] <-- load [comb~] from cyclone
You don't have to load the library with [import] or [declare] for this to work. You just call the object that way.
Why is this safest? Because it's possible for different libraries to have objects with the same name. For example, both cyclone and zexy have an object called [mean]. But they don't work exactly the same. zexy's takes a list, while cyclone's takes in a continuous stream. If you have both libraries loaded (and in Pd-extended, these two libraries happen to be loaded by default), you can't be sure which one you're getting if you just type [mean]. However, if you type [cyclone/mean], you know exactly which one you are getting.
Lightest linux for pd-extended
Hello everybody:
As far as I know, all <~>buntus (meaning ~ a U, an L an X, whatever) and debian use the "aptitude" package installer. You should check if pd-extended or pure-data is among the tree of packages for your distribution.
To do so, open a terminal window and type:
$ aptitude search pd-extended
or
$ aptitude search pure-data
Then something like this should appear:
p pd-extended - Pure Data with patches and a large collection of externals
The 'p' means that is not installed yet. You should type then:
$ sudo aptitude install pd-extended
(Type your superuser -root- password when prompted)
Or
$ sudo su
(or just "su" in debian) Type your superuser password when prompted, then the $ changes to #, meaning you are superuser:
# aptitude install pd-extended
You may have to install some other packages on the fly, but you should be asked for it, to type Y or N. If you type "aptitude search" after installing, the 'p' letter at the left should have changed to 'i'.
If pd-extended is not available in your distribution package tree, then is recommended to install it from:
http://puredata.info/downloads/pd-extended
As always, I wish you success!
Sumidero
Pd extended on OS X 10.7 Lion
All that "build" stuff is referring to compiling the code from source. It's not the same thing as adding libraries to your Pd install. A library that needs to be built is one that is written in C (typically) and needs to be compiled into a binary to run on your system. A library that is already compiled, however, can simply be downloaded and added to your Pd installation.
In terms of the differences between Pd-extended and the standard Pd (often referred to as Pd-vanilla), one of the big advantages to Pd-extended is that it comes with many of the most common libraries already installed. So you may not have to add anything for a while, and you can share patches that have many externals that aren't included in the Pd-vanilla fairly easily, since other Pd-extended users will have those libraries as well. Pd-extended is basically Pd-vanilla plus more. If a patch works in vanilla, it will work in extended, but not the other way around.
The disadvantage to Pd-extended, however, is that those libraries are contributed from various users/developers under various licenses, so if you wanted to package your patch up and make an app out of it, you'll have to go through all the licenses and make sure you're not violating them. With Pd-vanilla, the license pretty much lets you do whatever you want.
In regards to my mmb library, they are all abstractions, so they don't need to be built. But many of them require objects that are included in Pd-extended, so you would need that to use them. Installing the library is the same as any other. You can put it in any folder on your system; you just have to make sure Pd can find it. So, let's say you put the mmb folder containing the abstractions in /Library/Pd. To make sure Pd can find it, open Pd, make a new patch (I don't know why, but you have to do that), and in the menubar click Pd-extended -> Preferences -> Path... In the dialog box, click "New..." and choose the path /Library/Pd/mmb. You should be able to use them then.
Pd-Extended for Debian
** EDIT ** I created an UPDATED version on this wiki page with steps to follow. Here:
http://puredata.info/docs/developer/DebianWheezyAmd64
Hi Nicola,
@bamboomusic said:
Hi, I've just installed Debian Wheezy amd64, but I can't be able to find a compiled Pd-Extended version for Debian 64-bit.
I checked in:
http://puredata.info/community/projects/software/pd-extended
http://autobuild.puredata.info/auto-build/and in the puredata repo, but I only found i386 versions.
Am I missing something?
I think simply there is no packaged version.
I actually managed to build the source partly following the instructions found here:
http://puredata.info/docs/developer/Debian and thanks to the script in the scripts directory in the source package - credit really goes to the authors of these
with some modifications and additions:
---- WARNING. Pretty much untested. Pd starts, no libraries complain, audio and a bunch of patches I have work with alsa and jack ----
-
Add the debian multimedia repository as explained directly on their page:
http://debian-multimedia.org/ -
Do the build-dep as explained but with a slight modification
apt-get build-dep puredata gem pd-pdp
(notice pd-pdp non not pdp)
-
Install the following packages not listed on that page:
apt-get install libmp3lame0 libmp3lame-dev ladspa-sdk dssi-dev libimlib2-dev libtheora-dev
-
Install libquicktime1 and libquicktime-dev from the official main packages *not* with apt. The links:
http://packages.debian.org/testing/libs/libquicktime1
http://packages.debian.org/wheezy/libquicktime-dev -
Get the source of Pd-extended, unpack anywere as explained in other places..
-
from the main source directory go to source dir for pidip:
cd externals/pidip/
-
configure and make pidip with the following switches:
./configure --with-pd=../../pd --with-pdp=../pdp
make -
chdir to scripts/auto-build/ from the source dir:
cd scripts/auto-build/
-
Start the ./pd-extended-auto-builder.sh script:
./pd-extended-auto-builder.sh
-
Wait...
-
Cross fingers...
-
Ignore some scary messages...
If everything went well there should be a message saying you have a deb in dir ./packages/linux_make/Pd-0.42.5-extended.deb (still from the source root): -
cd there:
cd ../../packages/linux_make/
-
Finally install:
dpkg -i Pd-0.42.5-extended.deb
By the way I got a nice .deb so maybe I could put it up somewhere, not sure about the dependencies though.
Hope this helps,
Lorenzo
Bad lib path? on Gentoo,cant run Androidome/MLR tutorial due to libs.
Hi all,
posted this to the list, but no answer -- no discussion! decided to repost here.
I added pd-overlay from layman, and have installed the following:
[ebuild R ] puredata-base/pd-extended-0.42.5 USE="adaptive alsa
bassemu boids bsaylor creb cxc cyclone earplug ekext ext13 flashserver
flatspace flib freeverb gem2pdp ggee hcs hid iem16 iem_adaptfilt
iem_ambi iem_bin_ambi iem_delay iem_matrix iem_roomsim iem_spec2
iem_tab iemgui iemlib iemmatrix iemxmlrpc jasch_lib loaders mapping
markex maxlib mjlib moocow moonlib motex mrpeach oscx pan pdcontainer
pddp pdogg pdp pdp_opengl pidip pmpd postlude sigpack smlib tof toxy
unauthorized vanilla vbap windowing zexy -debug -fftw -jack
-portaudio" 0 kB [1]
Why the article at gentoo wiki tells me to remove oscx&zexy flags from build? I didn't listened to it though.
With a few tricks, a working alsa/timidity++/puredata chain was set up
and running, to reference for other newcomers:
pdextended -alsa -alsamidi -stderr -verbose -d (config at pastebin:
http://pastebin.com/8p0rcd41 )
The following files were installed to my system: (filelist with paths:
http://pastebin.com/F9yymAPH )
Now, wanted to install Androidome's script,
http://androidome.googlecode.com/files/AndroidomeRouter.pd
Multiple errors came about missing functions (like mrpeach/udpsend),
and in the UI they were outlined in red.
Also the debug log shown that search under multiple paths (none
included /usr/lib/pdextended/extra/mrpeach)
was failed for that functions.
Looks like http://www.mail-archive.com/pd-dev@iem.at/msg04901.html,
but checks more paths.
udpreceive 8080
... couldn't create
tried /usr/local/lib/pd-externals/sprintf.l_ia64 and failed
tried /usr/lib/pd-extended/extra/sprintf.l_ia64 and failed
tried /usr/local/lib/pd-externals/sprintf.pd_linux and failed
tried /usr/lib/pd-extended/extra/sprintf.pd_linux and failed
tried /usr/local/lib/pd-externals/sprintf/sprintf.l_ia64 and failed
tried /usr/lib/pd-extended/extra/sprintf/sprintf.l_ia64 and failed
tried /usr/local/lib/pd-externals/sprintf/sprintf.pd_linux and failed
tried /usr/lib/pd-extended/extra/sprintf/sprintf.pd_linux and failed
tried /usr/local/lib/pd-externals/sprintf.pd and failed
tried /usr/lib/pd-extended/extra/sprintf.pd and failed
tried /usr/local/lib/pd-externals/sprintf.pat and failed
tried /usr/lib/pd-extended/extra/sprintf.pat and failed
sprintf connect %s 8080
... couldn't create
tried /usr/local/lib/pd-externals/mrpeach.l_ia64 and failed
tried /usr/lib/pd-extended/extra/mrpeach.l_ia64 and failed
tried /usr/local/lib/pd-externals/mrpeach.pd_linux and failed
tried /usr/lib/pd-extended/extra/mrpeach.pd_linux and failed
tried /usr/local/lib/pd-externals/mrpeach/mrpeach.l_ia64 and failed
tried /usr/lib/pd-extended/extra/mrpeach/mrpeach.l_ia64 and failed
tried /usr/local/lib/pd-externals/mrpeach/mrpeach.pd_linux and failed
tried /usr/lib/pd-extended/extra/mrpeach/mrpeach.pd_linux and failed
error: [import]: can't load library in 'mrpeach'
... you might be able to track this down from the Find menu.
Which declare's should be added to ~/.pdextended to allow search in
/usr/lib/pdextended/extra/mrpeach and other directories?
Also it seems that
http://docs.monome.org/doku.php?id=dev:pd:simple_mlr uses an old
version of OSC (guess I name the things correctly and dont call fish an aardvark api), function names in code are like dumpOSC instead of packOSC; how to run the script at the link above with 0.42.5, can anyone tell here? (will also bug monome's list).
http://www.pdpatchrepo.info/hurleur/2010-12-28-171813_473x410_scrot.png
Bad lib path? on Gentoo,cant run Androidome/MLR tutorial due to libs.
Hi all,
posted this to the list, but no answer -- no discussion! decided to repost here.
I added pd-overlay from layman, and have installed the following:
[ebuild R ] puredata-base/pd-extended-0.42.5 USE="adaptive alsa
bassemu boids bsaylor creb cxc cyclone earplug ekext ext13 flashserver
flatspace flib freeverb gem2pdp ggee hcs hid iem16 iem_adaptfilt
iem_ambi iem_bin_ambi iem_delay iem_matrix iem_roomsim iem_spec2
iem_tab iemgui iemlib iemmatrix iemxmlrpc jasch_lib loaders mapping
markex maxlib mjlib moocow moonlib motex mrpeach oscx pan pdcontainer
pddp pdogg pdp pdp_opengl pidip pmpd postlude sigpack smlib tof toxy
unauthorized vanilla vbap windowing zexy -debug -fftw -jack
-portaudio" 0 kB [1]
Why the article at gentoo wiki tells me to remove oscx&zexy flags from build? I didn't listened to it though.
With a few tricks, a working alsa/timidity++/puredata chain was set up
and running, to reference for other newcomers:
pdextended -alsa -alsamidi -stderr -verbose -d (config at pastebin:
http://pastebin.com/8p0rcd41 )
The following files were installed to my system: (filelist with paths:
http://pastebin.com/F9yymAPH )
Now, wanted to install Androidome's script,
http://androidome.googlecode.com/files/AndroidomeRouter.pd
Multiple errors came about missing functions (like mrpeach/udpsend),
and in the UI they were outlined in red.
Also the debug log shown that search under multiple paths (none
included /usr/lib/pdextended/extra/mrpeach)
was failed for that functions.
Looks like http://www.mail-archive.com/pd-dev@iem.at/msg04901.html,
but checks more paths.
udpreceive 8080
... couldn't create
tried /usr/local/lib/pd-externals/sprintf.l_ia64 and failed
tried /usr/lib/pd-extended/extra/sprintf.l_ia64 and failed
tried /usr/local/lib/pd-externals/sprintf.pd_linux and failed
tried /usr/lib/pd-extended/extra/sprintf.pd_linux and failed
tried /usr/local/lib/pd-externals/sprintf/sprintf.l_ia64 and failed
tried /usr/lib/pd-extended/extra/sprintf/sprintf.l_ia64 and failed
tried /usr/local/lib/pd-externals/sprintf/sprintf.pd_linux and failed
tried /usr/lib/pd-extended/extra/sprintf/sprintf.pd_linux and failed
tried /usr/local/lib/pd-externals/sprintf.pd and failed
tried /usr/lib/pd-extended/extra/sprintf.pd and failed
tried /usr/local/lib/pd-externals/sprintf.pat and failed
tried /usr/lib/pd-extended/extra/sprintf.pat and failed
sprintf connect %s 8080
... couldn't create
tried /usr/local/lib/pd-externals/mrpeach.l_ia64 and failed
tried /usr/lib/pd-extended/extra/mrpeach.l_ia64 and failed
tried /usr/local/lib/pd-externals/mrpeach.pd_linux and failed
tried /usr/lib/pd-extended/extra/mrpeach.pd_linux and failed
tried /usr/local/lib/pd-externals/mrpeach/mrpeach.l_ia64 and failed
tried /usr/lib/pd-extended/extra/mrpeach/mrpeach.l_ia64 and failed
tried /usr/local/lib/pd-externals/mrpeach/mrpeach.pd_linux and failed
tried /usr/lib/pd-extended/extra/mrpeach/mrpeach.pd_linux and failed
error: [import]: can't load library in 'mrpeach'
... you might be able to track this down from the Find menu.
Which declare's should be added to ~/.pdextended to allow search in
/usr/lib/pdextended/extra/mrpeach and other directories?
Also it seems that
http://docs.monome.org/doku.php?id=dev:pd:simple_mlr uses an old
version of OSC (guess I name the things correctly and dont call fish an aardvark api), function names in code are like dumpOSC instead of packOSC; how to run the script at the link above with 0.42.5, can anyone tell here? (will also bug monome's list).
http://www.pdpatchrepo.info/hurleur/2010-12-28-171813_473x410_scrot.png
What is the advantage to using pd-vanilla?
one noise~ object is not particularly cpu intensive, but if you have 20 or 30 of them in a patch (quite easy to do if you make an analogue style drum kit, for example), then of course a whole bunch of [r~] objects are going to be more efficient.
as far as i know, the pd engine and gui are pretty much the same in both vanilla and extended. as for the difference between the two, i can only speak from personal experience, but here are the reasons i stopped using extended and went back to vanilla: (1) there are annoying objects in extended like [spigot~] which will not work on certain operating systems. (2) some objects in extended have weird behaviour (bugs). for example, the matrix objects looked very useful, but for some reason, they wouldn't load for me unless i opened the help patch first. (3) the most important reason i stopped using extended was because i did a commercial project using pd as the sound engine. the licence for pd vanilla allows for this, but the externals in pd extended are all covered by different licences.
also, i don't think there is much runtime difference between vanilla and extended, but as extended has a larger default search path, it does take a fraction longer to create objects. nothing worth worrying about usually.
Compiling pdvjtools on Mac OS X 10.5.8
dear all,
is there a way to get the pdvjtools working on Mac OS X10.5.8?
I would be especially interested in the videogrid object (as I hope if I am able to compile this all the other pdvjtools can also be built).
What I did by now (besides having Xcode on the system):
1. install pd-extended binary from:
http://downloads.sourceforge.net/pure-data/Pd-0.41.4-extended-macosx104-i386.dmg
2. install ffmpeg via macports (a "ffmpeg -version" results in ffmpeg version 0.5)
3. get ffmpeg sources from: http://ffmpeg.org/releases/ffmpeg-0.5.tar.bz2
4. get the PD sources from:
http://downloads.sourceforge.net/pure-data/Pd-0.41.4-extended.tar.bz2
5. get the pdvjtools from:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/externals/pdvjtools/
6. modified the first line of the videogrid-makefile to fit my pd sources:
PD_SRC=/Daten/pdsrc/Pd-0.41.4-extended/pd/src
7. tried to modify the second line of the makefile to:
FFMPEG_HEADERS=-I/Daten/pdsrc/ffmpeg-0.5
This is the folder with the ffmpeg sources.
After make clean I start make - it fires up gcc with some correct path to the pd-sources - but the ffmpeg sources are the problem:
g++ -I/Daten/pdsrc/ffmpeg-0.5 -I/Daten/pdsrc/Pd-0.41.4-extended/pd/src -fPIC -c -O -o videogrid.o videogrid.cc
videogrid.cc:47:32: error: ffmpeg/avcodec.h: No such file or directory
...
Question 1: why this path? I never said "ffmpeg" is the path but "ffmpeg-0.5"?
Question 2: Ok - avcodec.h is really not in ffmpeg but in:
/Daten/pdsrc/ffmpeg-0.5/libavcodec/avcodec.h
(I also "opened up" the rights to not be trapped in a permission thingy)
make still does not work - same error;
So I tried:
FFMPEG_HEADERS=-I/ffmpeg-0.5
in the makefile - the result was the same.
So I changed the ffmpeg headers to:
FFMPEG_HEADERS=-I/Daten/pdsrc/ffmpeg-0.5/libavcodec/
Result:
g++ -I/Daten/pdsrc/ffmpeg-0.5/libavcodec/ -I/Daten/pdsrc/Pd-0.41.4-extended/pd/src -fPIC -c -O -o videogrid.o videogrid.cc
videogrid.cc:47:32: error: ffmpeg/avcodec.h: No such file or directory
So I started to mess around even more - i renamed the "libavcodec" dir to "ffmpeg" and restored the headers to FFMPEG_HEADERS=-I/Daten/pdsrc/ffmpeg-0.5
This results (as avcodec.h is now found) in:
g++ -I/Daten/pdsrc/ffmpeg-0.5 -I/Daten/pdsrc/Pd-0.41.4-extended/pd/src -fPIC -c -O -o videogrid.o videogrid.cc
videogrid.cc:48:33: error: ffmpeg/avformat.h: No such file or directory
This for me looks like a never-ending pain - hence the last question:
Does somebody have a working makefile for the pdvjtools for Mac OS X or at least some hint on how to get them working?
cheers
clouds11
Getting started with Gem???
This is what it shows when I first open Pd (without opening any patches):
libdir loader $Revision: 1.8 $
written by Hans-Christoph Steiner <hans@at.or.at>
compiled on Jul 29 2008 at 03:24:20
compiled against Pd version 0.40.3.extended
/Applications/Pd-extended.app/Contents/Resources/extra/Gem/Gem.pd_darwin: dlopen(/Applications/Pd-extended.app/Contents/Resources/extra/Gem/Gem.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libfreetype.6.dylib
Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/Gem/Gem.pd_darwin
Reason: image not found
Gem: can't load library
libdir_loader: added 'cyclone' to the global objectclass path
libdir_loader: added 'zexy' to the global objectclass path
libdir_loader: added 'creb' to the global objectclass path
libdir_loader: added 'cxc' to the global objectclass path
libdir_loader: added 'iemlib' to the global objectclass path
libdir_loader: added 'list-abs' to the global objectclass path
libdir_loader: added 'mapping' to the global objectclass path
libdir_loader: added 'markex' to the global objectclass path
libdir_loader: added 'maxlib' to the global objectclass path
libdir_loader: added 'memento' to the global objectclass path
libdir_loader: added 'mjlib' to the global objectclass path
libdir_loader: added 'motex' to the global objectclass path
libdir_loader: added 'oscx' to the global objectclass path
libdir_loader: added 'pddp' to the global objectclass path
libdir_loader: added 'pdogg' to the global objectclass path
libdir_loader: added 'pixeltango' to the global objectclass path
libdir_loader: added 'rradical' to the global objectclass path
libdir_loader: added 'sigpack' to the global objectclass path
libdir_loader: added 'smlib' to the global objectclass path
libdir_loader: added 'toxy' to the global objectclass path
libdir_loader: added 'unauthorized' to the global objectclass path
libdir_loader: added 'pan' to the global objectclass path
libdir_loader: added 'freeverb' to the global objectclass path
libdir_loader: added 'hcs' to the global objectclass path
libdir_loader: added 'jmmmp' to the global objectclass path
libdir_loader: added 'ext13' to the global objectclass path
libdir_loader: added 'ggee' to the global objectclass path
libdir_loader: added 'flib' to the global objectclass path
libdir_loader: added 'ekext' to the global objectclass path
libdir_loader: added 'flatspace' to the global objectclass path
/Applications/Pd-extended.app/Contents/Resources/extra/pdp.pd_darwin: dlopen(/Applications/Pd-extended.app/Contents/Resources/extra/pdp.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib
Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/pdp.pd_darwin
Reason: image not found
pdp: can't load library
/Applications/Pd-extended.app/Contents/Resources/extra/pidip.pd_darwin: dlopen(/Applications/Pd-extended.app/Contents/Resources/extra/pidip.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib
Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/pidip.pd_darwin
Reason: image not found
pidip: can't load library
I see that it is saying "Gem: can't load library" so that probably explains why it isn't working, but I didn't delete anything since I first installed it. I could probably try re-installing it. Do you think that would do me any good, or should I try something else first?
Lib pb on pd extended 0.40
hi
i was working on pd ext 0.39 without pb
and I recently I update to 0.40
and glaps! pd can't load any lib anymore (gem, zexy, etc.).
I'm working on mac osX 4 11...
anyone can help
thx
yeli
/Applications/Pd-extended.app/Contents/Resources/extra/Gem/Gem.pd_darwin: dlopen(/Applications/Pd-extended.app/Contents/Resources/extra/Gem/Gem.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libfreetype.6.dylib
Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/Gem/Gem.pd_darwin
Reason: image not found
Gem: can't load library
cyclone: can't load library
zexy: can't load library
cxc: can't load library
ext13: can't load library
FFTease - A set of Live Spectral Processors
Originally written by Eric Lyon and Christopher Penrose for MAX/MSP
flext port (version 0.0.0) provided by Thomas Grill, (C)2003-2004
iemabs: can't load library
iemmatrix: can't load library
liblist: can't load library
markex: can't load library
maxlib: can't load library
memento: can't load library
mjlib: can't load library
motex: can't load library
oscx: can't load library
pddp: can't load library
pdogg: can't load library
/Applications/Pd-extended.app/Contents/Resources/extra/pdp.pd_darwin: dlopen(/Applications/Pd-extended.app/Contents/Resources/extra/pdp.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib
Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/pdp.pd_darwin
Reason: image not found
pdp: can't load library
/Applications/Pd-extended.app/Contents/Resources/extra/pidip.pd_darwin: dlopen(/Applications/Pd-extended.app/Contents/Resources/extra/pidip.pd_darwin, 10): Library not loaded: /usr/X11R6/lib/libX11.6.dylib
Referenced from: /Applications/Pd-extended.app/Contents/Resources/extra/pidip.pd_darwin
Reason: image not found
pidip: can't load library
pixeltango: can't load library
pmpd: can't load library
rradical: can't load library
sigpack: can't load library
smlib: can't load library
toxy: can't load library
unauthorized: can't load library
VASP modular 0.1.4pre
vector assembling signal processor
(C)2002-2007 Thomas Grill
http://grrrr.org/ext
xsample objects, version 0.3.2pre
xrecord~, xplay~, xgroove~
(C)2001-2007 Thomas Grill
/Applications/Pd-extended.app/Contents/Resources/extra/zexy/z~.pd_darwin: can't load library