> Great! Thanks Scott
> One other question. I recall there is a way to add a path from inside a patch (instead of having to open the path-dialog).
> Do you know how?
[declare -path path/to/library]
this only takes effect when opening the patch. This method has several advantages over the path preference of the application. For instance that you can redistribute a patch with a folder where the abstractions are in and you can declare that relative path in your patch.
> From: Scott R. Looney <
scottrlooney@gmail.com>
> To: Billy King <
billyking856@yahoo.ca>
> Sent: Tuesday, October 9, 2012 10:11:38 PM
> Subject: Re: [PD] soundhack
>
> it can be done by adding a path if needed to PD.
>
> #1: the more common way to install them is to take the folder with all the files and drop it in a specific path within the PD application.
>
> on a Mac the '.app' application files are actually bundles and can be opened. so find the PD-extended app, right click on it (or Ctrl click if you have no right mouse button option) and from the popup menu select 'Show Package Contents'.
>
> open the Contents folder and double click the 'Plugins' alias. this opens the 'extra' folder where most if not all of the externals are stored. copy or drop the soundhack folder with help files and 'pd_darwin' files in it and restart PD. the soundhack folder should be visible in the Help browser.
> #2. a pd_darwin file is a binary executable file created in C that runs in PD, that is ported to Darwin. Darwin is the BSD Unix subsystem of every Mac OS X system. PD refers to these types of files as 'externals'. these are not editable in PD, but they will execute in PD.
m.