hello,
for those who are interested in to use fluid~ with soundfont
instruments under OSX, here it is the before -flext compiled
fluid~.pd_darwin file. It works fine in my machine under OSX 10.4.8
and Pd-0.39.2-extended-test7, but I never tried with any other machine.
http://www.puredata.org/Members/korayt/pdfiles/fluid~pd_darwin.tgz/
Koray.
M.Koray Tahiroglu Media Lab,UIAH http://mlab.uiah.fi/~korayt/ tel: +358 50 939 02 33 ( in Finland only) tel: +90 533 712 8245
On Feb 3, 2007, at 1:00 PM, pd-list-request@iem.at wrote:
Message: 8 Date: Sat, 3 Feb 2007 10:32:44 +0100 From: Frank Barknecht fbar@footils.org Subject: Re: [PD] flext, fluid~, readanysf~, and FLEXT_USE_CMEM (or don't) To: pd-list@iem.at Message-ID: 20070203093244.GD24769@fliwatut.scifi Content-Type: text/plain; charset=us-ascii
Hallo, Bryan Jurish hat gesagt: // Bryan Jurish wrote:
First, make sure you're not really delete()ing a NULL pointer ;-)
That said, I do think we've stumbled onto the same bug, and that there's something going horribly wrong (possibly because of mis-use and/or misunderstanding of flext's conventions) particularly when flext
objects are not self-contained, and call functions from 3rd-party shared libraries (e.g. fluid~ --> libfluid; readanysf~ --> libogg,
libvorbis, libmad, libflac, etc.; your resoncomb~ --> libSndObj).Hm, maybe fluid~ should go back to being a pure C/Pd external like it was in its prevous life as iiwu~? Max-users didn't seem interested in it (or just not willing to compile) anyways, one even wrote a new, pure C Max external for fluidsynth instead of compiling the flext-fluid~. So the cross-platformness I was hoping to achieve didn't work out in practice.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__