Having some issues getting some external abstractions/externals to compile with the "make app" function in Pd-extended. It seems to compile foreign externals like sigmund~ but not the [ambilib] by Dave Malham. Any ideas? I have the externals listed in path but they are not showing up on the "run-time" compile. Should they be included somewhere specifically on HD, maybe in Pd-extended contents?

Any help much appreciated,

Ricky

Hi Ricky,

It's a while ago that I made a 'app' from Pd that way. Probably, you can pick all the binaries and abstractions you need from within the Pd-extended folder if they didn't come with the 'app'.

I also made an 'app' from Vanilla Pd, and it does not even have the 'make app' option. It's a matter of copying all the stuff you need into the 'extra' folder, setting startup items and flags, setting the new name in Info.plist etcetera. And coolest of all, you can make a new icon for your app with Icon Composer...

With Vanilla Pd, the app is quite a bit more compact. Ah, there's one complication with the so called standalones: it must have it's own preferences file. Do not set preferences from the app's menu - or they will be written into the shared preferences file for all Pd-extended installations on your computer. Make a preference file by hand instead, using X-code's Property List Editor and store it in the app's Contents folder.

Katja

Hi Katja,

Is there an example of the preferences file on my HD? This is a new problem to me.

Thanks for the direction,

Ricky

Also, is there a text-type file on my HD that contains the Pd paths for start-up?

Ricky

Ricky,

Preferences stuff is explained in Pd flossmanual, section 'advanced configuration':

http://en.flossmanuals.net/pure-data/ch011_advanced-configuration/

If you change or make a plist for OSX 'by hand', with Property List Editor, there is one trick to keep in mind: the numbers for key 'nloadlib' and 'npath' must reflect the actual numbers of libs and paths which you want to include. For example, a lot of loadlibs can be defined, but if nloadlib is zero, no lib will be loaded.

Katja

Understood. Thank you.

One more thing; I have been trying to establish a few paths and I have been receiving some strange error messages:

"error: plications/Pd-0.43.0-extended-20110207.app/Contents/Resources/Scripts/../extra/rradical: no such object"

The odd thing is that the pathway mentioned is not what I had point at. Any ideas?

What is 'plications'?

I presume it is pointing at my applications folder on HD. I read the FLOSS manuals and I don't seem to have the org.puredata.pdextended.plist on my machine? I think this may be causing the issues.

edit: I should add that the strange 'plications results after navigating to the Pd application folder.

Ricky,

You can't find such config files with Finder's search functionality. In every Pd-extended's Contents folder is a org.puredata.pdextended.default.plist. You are using a 0.43 build, maybe the info from floss is not relevant anymore.

Katja

I guess not?

Platform-Specific Configuration Tools

Since Pd-extended and the vanilla version of Pure Data really function as separate apps, they each of their own separate files for saving configuration settings. Also, this settings file is saved with a format, name, and location that is appropriate for the operating system you are using. The locations for the Pd settings files are:

Pd-extended

OS X: ~/Library/Preferences/org.puredata.pd.plist (~ means your home folder)

Every object that I require to be compiled is configured correctly through the path and startup menus, but it still does not work. I had planned on formatting my machine (time for a spring clean?) and perhaps it may work after that.

And I am using a 0.42.5 build.

Are you sure you're looking in your home folder and not the HD? If I'm not mistaken, when you make any changes to the preferences from Pd-extended, it will make an updated prefs file and put it in that directory. Otherwise, it will stick to the default one in the .app. Either way, Spotlight won't find it. You still have to navigate to it.

Also, the error you posted above shows it looking into the 0.43.0 build. My guess is you gave that build a try, messed with the setting, and it overwrote you 0.42.5 prefs. So you should either trash the old prefs and rebuild your paths or edit the file by hand.

Yep. That's exactly what I have done. I tested 0.43 and messed up the preferences somewhere along the way. Thanks for your help Katja and .mmb. I will try again tomorrow.

Good news. I have a fully compiled standalone. Just a note, for this to function correctly (on OSX), you have to edit the "org.puredata.pdextended.default.plist," not "org.puredata.pd.plist," which is located in the Pure Data package contents folder.

No wonder so many people on the Pd-list have said they have trouble with the Make App function while Hans says it always works for him. I think he only uses the defaults. Are you on the list? If so, it might be worth mentioning there. If not, I'll be happy to bring it up.

Pd-extended 0.43 is no longer supporting editing the preferences (so it might get shrugged off as "not technically a bug"), but that doesn't mean it isn't doable. And I've never seen this solution brought up.

By the way, this is now the official way to add libraries:

http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files

I am registered but rarely post. Please do bring it up if you think the information is of benefit to anyone