Dear ladies and gentlemen, i'm proud to announce the new versions of
- flext (which used to be max-pd 0.2), the C++ layer for pd and max/msp
externals
Along with the name a lot has changed - programming C++ externals has become a cinch. Version 0.1.1 features abstractions for DSP handling, more robustness, better readability of code, and more documentation. See idelay or xsample sources for further reference.
- xsample, a collection of sample objects
quite a few bugs have been fixed
xgroove~ is a varispeed sample player/looper (much like Max/MSP groove~) xplay~ acts like tabread4~ with more options xrecord~ records message- or signal-triggered into a buffer (with mix-in capability)
under Max/MSP these objects are multi-channel capable
- idelay, a simple interpolating delay (in one object) - mainly a
demonstration how to use flext
For these packages find sources, project files, builds and help patches for Windows (MS VC++ 6, BorlandC++ 5.5), Linux (gcc i686) and MacOS (CodeWarrior) under
http://www.parasitaere-kapazitaeten.net/Pd/ext/
have fun, Thomas
Thomas Grill hat gesagt: // Thomas Grill wrote:
i'm proud to announce the new versions of
- flext (which used to be max-pd 0.2), the C++ layer for pd and max/msp
externals
What would be the preferred location to install the flext header and library files in linux? I know, that I can give the FLEXTPATH in my Makefiles, but maybe it would be a good idea, to agree upon a common location, as everyone will have the flext source files somewhere else.
Personally I would just put the header in /usr/include and flext.a in /usr/lib or somewhere under /usr/lib/pd. I'm not sure, where you wanted it to land, maybe $(PDEXTRA), but that one is not defined in the flext makefile. It is in xsample, though.
Ciao,
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ / / __ \ ___\
/ / / ____/ / / / // ____// /\ \ ___\____ \
/_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\
You should probably put things in /usr/local/include (or atleast /usr/local/something) because on a lot of distributions, everything except the ../local directories is considered the exclusive domain of offical-distribution business..
or atleast, that's what i tend to believe :)
(and, i haven't had a look at flext yet, so maybe you should listen to users instead)
pix.
On Mon, 25 Feb 2002 11:54:52 +0100 Frank Barknecht barknech@ph-cip.uni-koeln.de wrote:
Thomas Grill hat gesagt: // Thomas Grill wrote:
i'm proud to announce the new versions of
- flext (which used to be max-pd 0.2), the C++ layer for pd and
max/msp externals
What would be the preferred location to install the flext header and library files in linux? I know, that I can give the FLEXTPATH in my Makefiles, but maybe it would be a good idea, to agree upon a common location, as everyone will have the flext source files somewhere else.
Personally I would just put the header in /usr/include and flext.a in /usr/lib or somewhere under /usr/lib/pd. I'm not sure, where you wanted it to land, maybe $(PDEXTRA), but that one is not defined in the flext makefile. It is in xsample, though.
Ciao,
__ __Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______ / __// __ /__/ __// // __ \ / / __ \ ___\ / / / ____/ / / / // ____// /\ \ ___\____ \ /_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\
What would be the preferred location to install the flext header and library files in linux? I know, that I can give the FLEXTPATH in my Makefiles, but maybe it would be a good idea, to agree upon a common location, as everyone will have the flext source files somewhere else.
Personally I would just put the header in /usr/include and flext.a in /usr/lib or somewhere under /usr/lib/pd. I'm not sure, where you wanted it to land, maybe $(PDEXTRA), but that one is not defined in the flext makefile. It is in xsample, though.
Hmmm, i didn't spend brain-time on that. I simply put the flext source where i develop my externals (i.e. /home/thomas/prog/pd/flext), and the lib in some subfolder of that .....this is surely no portable behavior.... /usr/local/include and /usr/local/lib is just fine. Be aware that the flext.a may not be upwards compatible for the next few "releases". I'll fix the path stuff for the upcoming next release (featuring list/anything for all inlets)
greetings, Thomas
Thomas Grill hat gesagt: // Thomas Grill wrote:
What would be the preferred location to install the flext header and library files in linux? I know, that I can give the FLEXTPATH in my Makefiles, but maybe it would be a good idea, to agree upon a common location, as everyone will have the flext source files somewhere else.
Personally I would just put the header in /usr/include and flext.a in /usr/lib or somewhere under /usr/lib/pd. I'm not sure, where you wanted it to land, maybe $(PDEXTRA), but that one is not defined in the flext makefile. It is in xsample, though.
Hmmm, i didn't spend brain-time on that. I simply put the flext source where i develop my externals (i.e. /home/thomas/prog/pd/flext), and the lib in some subfolder of that .....this is surely no portable behavior....
yes, that's what I'm doing also, normally.
/usr/local/include and /usr/local/lib is just fine.
It's not, that I don't want to mess in /usr, because that would be distribution land. I don't want to install to /usr/local, because I build Debian packages for my distribution on my own. That way, upgrades are handled by the Debian package system, and they become really painless. So I do in fact want to install somewhere in /usr, an not in /usr/local, but I'm not sure if e.g. flext.h should go to /usr/include or somewhere under /usr/lib/pd or even in a yet nonexisting include directory "/usr/include/pd"
This might be a question for PD in general. I have m_pd.h etc. in /usr/include, I think that's okay, but it could clash with other headers sometime, couldn't it?
Be aware that the flext.a may not be upwards compatible for the next few "releases". I'll fix the path stuff for the upcoming next release (featuring list/anything for all inlets)
In fact, I can't rebuild flext or xsample at the moment, because I always get an "Internal compiler error", using gcc in version 2.95.4. Your binaries work fine, though...
But so I can't build my own debian packages at the moment, and I copied everything in $(PD-DIR)/extra now.
Ciao,
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ / / __ \ ___\
/ / / ____/ / / / // ____// /\ \ ___\____ \
/_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\
In fact, I can't rebuild flext or xsample at the moment, because I always get an "Internal compiler error", using gcc in version 2.95.4. Your binaries work fine, though...
I did the build with gcc 2.95.2 which works fine for flext.
I'm generally surprised by the bad quality of most C++ compilers, though. GCC and MSVC 6 ("internal compiler error") and CodeWarrior for MacOS ("C++ feature not implemented") fail when using more "exotic" (but standard) C++ features, like template <int,int> for functions or class member pointers.
For Windows i can recommend the free BorlandC++ 5.5 compiler with which i have never experienced any problems. What concerns Linux I would like to hear if anyone has made experiences with the gcc 3.0 series (before i try it out...). Anybody using it?
greetings, Thomas
flext, xsample, etc. http://www.parasitaere-kapazitaeten.net/Pd/ext
Thomas Grill wrote:
In fact, I can't rebuild flext or xsample at the moment, because I always get an "Internal compiler error", using gcc in version 2.95.4. Your binaries work fine, though...
I did the build with gcc 2.95.2 which works fine for flext.
gcc 2.95.2 compiled flext for me, as well. it does give me "internal compiler error" for xsample, however.
What concerns Linux I would like to hear if anyone has made experiences with the gcc 3.0 series (before i try it out...). Anybody using it?
gcc 3.0.3 compiles both flext and xsample for me -- i can't seem to get xsample loaded into pd though ("shared library not present" or somesuch) -- but i compiled pd with gcc 2.95.2, so perhaps that has something to do with it...
marmosets, Bryan
-
Bryan Jurish -
Frank Barknecht -
pix -
Thomas Grill