It's not discussed as much because you have to rebuild libpd with the externals for Java which is not so easy, especially if you haven't done it before. Your best bet is to use an abstraction library that works with pd vanilla. rjlib for instance, has both a resonant low pass filter and a ead~ replacement: [e_reslop] & [c_ead].

libpd is pd-vanilla, so IMO, it's best to approach it in that way unless you can add externals directly to your project. Even then, targeting vanilla means maximum portability. Libs like rjlib really help make that not so painful ...

On Aug 5, 2013, at 6:00 AM, pd-list-request@iem.at wrote:

From: Òscar Martínez Carmona xamps23@gmail.com Subject: [PD] libpd and Processing; handling externals Date: August 5, 2013 2:14:43 AM EDT To: "pd-list@iem.at" pd-list@iem.at

Hi list! I'm aware that libpd and Processing are not the subjects more related to this list but I've asked this were it's suposed to be; "Pd-everywhere" 's threat at Create Digital Noise without any reply by now, so I'm trying it here. Libpd and Processing work really fine together and embedding PD patchs in Processing apps (and even making them standalone) it's quite easy: cool! The thing is that externals don't seem to work when used in the patch. That happens also whith libpd on iOS or Android aswell, but the solution is well doccumented and nicely solved in the (awesome) "Making Musical Apps" book by Peter Brinkmann. I haven't found any solution to this in the Processing environment by now, does anybody know how to proceed? I'm using the lipbp5 Processing's version of libpd in OSX 10.7 and more preciselly using the [moog~] and [ead~] externals. Thanx!

-- Òscar Martínez Carmona

Dan Wilcox @danomatika danomatika.com robotcowboy.com