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? Thanks again B
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.
#3 you should generally put it where i stated before, but i believe you can optionally create a path for PD to look for externals.
@ List - was there another way that changed recently how externals were loaded that was different than adding a path in the preferences? i seem to remember something changing about that between 0.42 and 0.43.
hope this helps! anyone else want to elaborate?
scott
On Tue, Oct 9, 2012 at 6:48 PM, Billy King billyking856@yahoo.ca wrote:
Hello all,
3 related questions:
How does one install soundhack externals for PD - simply by pointing a path to the folder?
Also, what's the deal exactly with the pd_darwin files? I assume they cannot be edited / viewed inside PD (they are not written in PD, right?)
last, is it a good idea to throw it into the pd-extended package content?
ThanksB
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
scott, you may want to read the netiquette http://puredata.info/community/lists/Netiquette/ sections “Reply-To” and “HTML vs plain-text”
Am 10.10.2012 um 04:26 schrieb Billy King billyking856@yahoo.ca:
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.
this is NOT the preferred way to install libraries. If you do it like this you will loose the library when you update the application. Refer to http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files on how to install externals and help files. as HCS has already mentioned.
#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.
huh? i'm just using gmail same as i always have. i realize i steered Billy the wrong way on his installation situation but i always reply to all in my emails to the list and i don't format my type beyond what gmail does by default.
scott
On Wed, Oct 10, 2012 at 3:21 AM, Max abonnements@revolwear.com wrote:
scott, you may want to read the netiquette http://puredata.info/community/lists/Netiquette/ sections “Reply-To” and “HTML vs plain-text”
Am 10.10.2012 um 04:26 schrieb Billy King billyking856@yahoo.ca:
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.
this is NOT the preferred way to install libraries. If you do it like this you will loose the library when you update the application. Refer to http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files on how to install externals and help files. as HCS has already mentioned.
#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. _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[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.
Yes, you can do that.
Or alternatively...I am working with a percussionist who has to run his patches on a Mac. I have a version of the external I am using for a Mac inside a folder ext/ which is inside the directory that contains the patch.
Instead of typing the name of the object into the object box when it is created [gemnotes_counter] I type... [ext/gemnotes_counter] and the external is always the right version, since I make sure the extern is distributed with the patch. I also have versions for Windows and Linux in the same folder, so in theory I could run it on any machine... But if you see my previous post on "Too many objects" you'll find it doesn't work on Windows. Ah well, it doesn't have to, yet ;-)
Ed
-
Billy King -
Ed Kelly -
Max -
Scott R. Looney