Diego de la Fuente Curaqueo

I was wondering if anyone have tried to use Lyon's FFTease library on Max7... I downloaded it from 

http://disis.music.vt.edu/eric/LyonSoftware/MaxMSP/FFTease/

 and when i tried to use residency~, max console showed me this:

residency~: unable to load object bundle executable

2015-06-05 15:15:31.941 Max[1601:707] Error loading /Applications/Max.app/Contents/Resources/C74/externals/FFTease2.52-MaxMSP-OSX/FFTease Externals/residency~.mxo/Contents/MacOS/residency~: dlopen(/Applications/Max.app/Contents/Resources/C74/externals/FF

Tease2.52-MaxMSP-OSX/FFTease Externals/residency~.mxo/Contents/MacOS/residency~, 262): no suitable image found. Did find:

/Applications/Max.app/Contents/Resources/C74/externals/FFTease2.52-MaxMSP-OSX/FFTease Externals/residency~.mxo/Contents/MacOS/residency~: no matching architecture in universal wrapper

the same thing happened with all the other objects of the mentioned library... :(

Hi everyone,
I was wondering if anyone have tried to use Lyon's FFTease library on Max7... I downloaded it from http://disis.music.vt.edu/eric/LyonSoftware/MaxMSP/FFTease/ and when i tried to use residency~, max console showed me this: 

residency~: unable to load object bundle executable
 2015-06-05 15:15:31.941 Max[1601:707] Error loading /Applications/Max.app/Contents/Resources/C74/externals/FFTease2.52-MaxMSP-OSX/FFTease Externals/residency~.mxo/Contents/MacOS/residency~:  dlopen(/Applications/Max.app/Contents/Resources/C74/externals/FF
 Tease2.52-MaxMSP-OSX/FFTease Externals/residency~.mxo/Contents/MacOS/residency~, 262): no suitable image found.  Did find:
 /Applications/Max.app/Contents/Resources/C74/externals/FFTease2.52-MaxMSP-OSX/FFTease Externals/residency~.mxo/Contents/MacOS/residency~: no matching architecture in universal wrapper

the same thing happened with all the other objects of the mentioned library... :(


fftease-max7-osx

"no matching architecture" is a key phrase. Are these 64 or 32 bit externals?

You may have to run Max 7 in 32 bit mode (can be accessed if you get info on the Max app).

"no matching architecture" is a key phrase. Are these 64 or 32 bit externals?
You may have to run Max 7 in 32 bit mode (can be accessed  if you get info on the Max app).


Im not sure if they're 64 o 32 bit externals (and there's no info about that in the website). I've tried to use FFTease objects running Max both in 32 and 64 bits and nothing changed.

Hi Evan,
Im not sure if they're 64 o 32 bit externals (and there's no info about that in the website). I've tried to use FFTease objects running Max both in 32 and 64 bits and nothing changed.


It should have. I just ran all the externals in Max 7 in 32 bit mode.

https://github.com/ericlyon/FFTease3.0-MaxMSP

In my little spare time i'm compiling the sources for Win 32 and 64 bit.

I did some test and everything seems to work!

In a week or so i'll share the results ;-)

For OSX should be easy beacause in the github repository there is an xcode project...

Eric has open the sources.
In my little spare time  i'm compiling the sources for Win 32 and 64 bit.
I did some test and everything seems to work!
In a week or so i'll share the results ;-)
For OSX should be easy beacause in the github repository there is an xcode project...

I wrote an email to Eric in order to brief him about this issue and he'd shared with me the same version for OSX (beta).

Thanks a lot Alfonso...
I wrote an email to Eric in order to brief him about this issue and he'd shared with me the same version for OSX (beta).

Is the x64 version available to download anywhere?

I read the conversation you had here with Eric Lyon :

https://github.com/ericlyon/FFTease3.0-MaxMSP/issues/1

and downloaded the FFTease 3.0 package, Unfortunatly when I try to load any object it doesn't work and it appears in red, all I get in the console is this message :

I'm on Windows 7, Max 7.2.3, same issue on 32bit and 64bit.

I read the conversation you had here with Eric Lyon :
https://github.com/ericlyon/FFTease3.0-MaxMSP/issues/1 

and downloaded the FFTease 3.0 package,  Unfortunatly when I try to load any object it doesn't work and it appears in red, all I get in the console is this message :  

I'm on Windows 7, Max 7.2.3, same issue on 32bit and 64bit.


Exactly the same problem as DJLBE. I think the fftease 3.0 package is mac only, which is really, really disappointing.

Exactly the same problem as DJLBE.  I think the fftease 3.0 package is mac only, which is really, really disappointing.


I know that this is an old post, but I was having the same issue that DJLBE, ERIC, and GEOSCLE was having and have found a solution.

After downloading the FFTease 3.0 package and typing any of the object names into a new max object, the object is red and the max window repeats the name of the object 4 times.

For example: I type [pvoc~] and the object loads as red and the max window shows: 

However, if I then type [fftz.pvoc~], as the objects are typed in the help files, it works like a charm. If is START by typing [fftz.pvoc~], that is, before typing [pvoc~], it does NOT work. It isn't the end of the world to load them with the two step process, but after saving and re opening a file that uses the externals, none of them load, which is a deal breaker when using more than a few of the FFTease externals. 

I added "fftz."before all of the external names and it works just fine. To be clear: in Windows file explore, go to the directory where all of the externals are located. Go one by one, or use a bulk renamer, to add "fftz." at the beginning of each file name. For example, "bthresher~.mxe64" should be changed to "fftz.bthresher~.mxe64". Do this for all of them and they open in max when you type them into a new object box as [fftz.bthresher~].

I know that this is an old post, but I was having the same issue that DJLBE, ERIC, and GEOSCLE was having and have found a solution. 

PROBLEM: 
After downloading the FFTease 3.0 package and typing any of the object names into a new max object, the object is red and the max window repeats the name of the object 4 times. 

However, if I then type [fftz.pvoc~], as the objects are typed in the help files, it works like a charm. If is START by typing  [fftz.pvoc~], that is, before typing [pvoc~], it does NOT work. It isn't the end of the world to load them with the two step process, but after saving and re opening a file that uses the externals, none of them load, which is a deal breaker when using more than a few of the FFTease externals. 

SOLUTION: 
I added "fftz."before all of the external names and it works just fine. To be clear: in Windows file explore, go to the directory where all of the externals are located. Go one by one, or use a bulk renamer, to add "fftz." at the beginning of each file name. For example, "bthresher~.mxe64" should be changed to  "fftz.bthresher~.mxe64". Do this for all of them and they open in max when you type them into a new object box as [fftz.bthresher~].

Is there a place to download a package compiled for Win-64?

Yes. Here's the link: https://disis.music.vt.edu/eric/main/fftease/

FFTease 3.0 has both 32 and 64 bit externals

Yes. Here's the link: https://disis.music.vt.edu/eric/main/fftease/
FFTease 3.0 has both 32 and 64 bit externals

@ David Landon I couldn't get those to work on Windows 10, 64bit, Ableton Suite 11. The link

downloads the FFTease-3.0-10282015 zip file which has a FFTease 3.0 10282015 folder (and a folder called _MACOSX)

I jammed the FFTease 3.0 10282015 folder into my Packages folder. But the whole thing is full of *.mxo 

, which are for Macs. Max could load up the Help and Reference pages for the objects, but the actual objects aren't there.

For example, The package has a directory called

"FFTease 3.0 Package\externals\fftz.bthresher~.mxo\Contents"

which contains a MacOS directory and a info.plist and pkginfo file. The MacOS directory only contains a file called fftz.bthresher~ which has file type "BTHRESHER~ file"

Soooo, I went and looked in the _MACOSX directory of the zip file. Inside, there is a FFTease3.0 folder, followed by a Package and a Code directory. For some mystical reason, the Package directory has an externals folder with .mxe and .mxe64 files. For example, there is a file called

So, I renamed it to fftz.bthresher~.mxe64. No Luck. It finds the renamed object and gives an

error 193 loading external fftz.bthresher~

I even tried renaming the *.mxe file, same result. I went ahead and tried with a different file and renamed it to

All with the same error. It finds the file, can't load it.

@ David Landon  I couldn't get those to work on Windows 10, 64bit, Ableton Suite 11.  The link

downloads the FFTease-3.0-10282015 zip file which has a  FFTease 3.0 10282015 folder (and a folder called _MACOSX) 

I jammed the FFTease 3.0 10282015  folder  into my Packages folder. But the whole thing is full of *.mxo folders, which are for Macs.  Max could load up the Help and Reference pages for the objects, but the actual objects aren't there.  

For example, The package has a directory called  

which contains a MacOS directory and a info.plist and pkginfo file. The MacOS directory only contains a file called fftz.bthresher~  which has file type "BTHRESHER~ file"


Soooo, I went and looked in the _MACOSX directory of the zip file.  Inside, there is a FFTease3.0 folder, followed by a Package and a Code directory.  For some mystical reason, the Package directory has an externals folder with .mxe and .mxe64 files.  For example, there is a file called

._bthresher~.mxe64

So, I renamed it to fftz.bthresher~.mxe64.  No Luck. It finds the renamed object and gives an 

error 193 loading  external fftz.bthresher~

I even tried renaming the *.mxe file, same result.  I went ahead and tried with a different file and renamed it to 

All with the same error.  It finds the file, can't load it.

That _MACOSX folder are mac resources, which you can safely delete.

The package probably has not been compressed carefully,

the windows externals are in the package, exactly in the exernals folder.

but if you still have problems, here is compressed package

FFTease3.0PackageWIN.zip

That _MACOSX folder are mac resources, which you can safely delete.
And all other mac files.
The package probably has not been compressed carefully,
one has to exclude mac resources...

the windows externals are in the package, exactly in the exernals folder.
but if you still have problems, here is compressed package
with all traces of mac files removed.


I haven't been able to use any of these in over 5 years. Back then I was planning on publishing a whole bunch of Max4Live devices, made the switch to 64bit and had to give up.

OMGOMGOMGOMG TYTYTYTYTYTYTY!!!!!!!!!!
I haven't been able to use any of these in over 5 years.  Back then I was planning on publishing a whole bunch of Max4Live devices, made the switch to 64bit and had to give up.

FFTease on Max7 (OSX)