(→Download) |
|||
| (42 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | __NOTOC__ | |
| + | The FTM external SDK (Mac OS X only) consist of an Xcode project and the sources of three example externals that demonstrate the most important features of the FTM external API. | ||
| − | * | + | * '''fff.coucou''' ... an external storing four different items using messages and/or four dedicated inlets |
| + | * '''fff.pack''' ... a full FTM compatible pack | ||
| + | * '''fff.pingpong~''' ... a non-sense DSP external toggeling an input signal between two outputs | ||
| − | + | == Download == | |
| + | |||
| + | * [http://recherche.ircam.fr/equipes/temps-reel/distrib/FTMEXT-SDK-2-6-MacOSX.zip FTM External SDK 2.6] Max 5 et 6 on Mac OS X | ||
| + | |||
| + | Older versions: | ||
| + | * [http://listes.ircam.fr/wws/arc/ftm/2011-04/msg00024/FTM-SDK-2.5.0-BETA-20.zip FTM External SDK 2.5] for Max 5 on Mac OS X | ||
| + | * [http://recherche.ircam.fr/equipes/temps-reel/distrib/FTMEXT-SDK-230-OSX.zip FTM External SDK 2.3] for Max 4.6 on Mac OS X | ||
| + | |||
| + | == Instructions (version 2.6) == | ||
| + | |||
| + | === Max 5 SDK === | ||
| + | |||
| + | The FTM external SDK depends of the Max 5 SDK available from [http://cycling74.com/products/sdk/ Cycling '74]. | ||
| + | |||
| + | The variable '''C74_SUPPORT_DIR''' in the Xcode build project has to be set to the folder of the Max 5 SDK (usually "c74support"). | ||
| + | |||
| + | By default, the project looks for the Max 5 SDK in "/Applications/Max5/c74support". | ||
| + | |||
| + | === FTM Library === | ||
| + | |||
| + | An FTM external always has to be next to the FTM library external ''ftm.mxo''. | ||
| + | The bundle of ''ftm.mxo'' also contains the FTM header files needed to compile the externals. | ||
| + | |||
| + | The directory "externals" in the SDK distribution contains a copy of the ''ftm.mxo'' and by default, the compiled example externals are copied into this directory to work right away. | ||
| + | |||
| + | Nevertheless, you should set the variable '''EXTERNALS_DIR''' of the Xcode build project to the externals directory of your current FTM & Co distribution. | ||
| + | |||
| + | This way the compilation uses the header files of the FTM release you actually use and the compiled externals are directly copied next to the ''ftm.mxo'' library external and the other externals of this release. | ||
| + | |||
| + | == Support == | ||
| + | |||
| + | For questions and suggestions, please consider subscribing and contributing to the [https://lists.sourceforge.net/lists/listinfo/ftm-devel ftm-devel] mailing-list. | ||
Latest revision as of 14:38, 3 October 2012
The FTM external SDK (Mac OS X only) consist of an Xcode project and the sources of three example externals that demonstrate the most important features of the FTM external API.
- fff.coucou ... an external storing four different items using messages and/or four dedicated inlets
- fff.pack ... a full FTM compatible pack
- fff.pingpong~ ... a non-sense DSP external toggeling an input signal between two outputs
Download
- FTM External SDK 2.6 Max 5 et 6 on Mac OS X
Older versions:
- FTM External SDK 2.5 for Max 5 on Mac OS X
- FTM External SDK 2.3 for Max 4.6 on Mac OS X
Instructions (version 2.6)
Max 5 SDK
The FTM external SDK depends of the Max 5 SDK available from Cycling '74.
The variable C74_SUPPORT_DIR in the Xcode build project has to be set to the folder of the Max 5 SDK (usually "c74support").
By default, the project looks for the Max 5 SDK in "/Applications/Max5/c74support".
FTM Library
An FTM external always has to be next to the FTM library external ftm.mxo. The bundle of ftm.mxo also contains the FTM header files needed to compile the externals.
The directory "externals" in the SDK distribution contains a copy of the ftm.mxo and by default, the compiled example externals are copied into this directory to work right away.
Nevertheless, you should set the variable EXTERNALS_DIR of the Xcode build project to the externals directory of your current FTM & Co distribution.
This way the compilation uses the header files of the FTM release you actually use and the compiled externals are directly copied next to the ftm.mxo library external and the other externals of this release.
Support
For questions and suggestions, please consider subscribing and contributing to the ftm-devel mailing-list.