From ftm
Line 4: | Line 4: | ||
The basic idea of FTM is to extend the data types exchanged between the objects in a Max/MSP patch by complex data structures such as sequences, matrices, dictionaries, break point functions, tuples and whatever might seem helpful for the processing of music, sound and motion capture data. | The basic idea of FTM is to extend the data types exchanged between the objects in a Max/MSP patch by complex data structures such as sequences, matrices, dictionaries, break point functions, tuples and whatever might seem helpful for the processing of music, sound and motion capture data. | ||
− | [[About | | + | * [[About | Read more about FTM ]] |
− | + | * [http://listes.ircam.fr/wws/info/ftm join the FTM mailing-list] | |
− | [http://listes.ircam.fr/wws/info/ftm join the FTM mailing-list] | ||
Revision as of 18:42, 1 December 2006
FTM is a shared library for Max/MSP providing a small and simple real-time object system and optimized services to be used within Max/MSP externals.
The basic idea of FTM is to extend the data types exchanged between the objects in a Max/MSP patch by complex data structures such as sequences, matrices, dictionaries, break point functions, tuples and whatever might seem helpful for the processing of music, sound and motion capture data.
FTM standard packages
(included in the free releases)
- FTM ... set of basic functionalities
- Gabor ... multi-representation overlap-add signal processing
- MnM ... matrix processing and recognition
Additional packages
(available via the IRCAM Forum)
- Suivi ... score following for audio and MIDI peformance input
Publications
- ICMC 2005 paper on FTM (PDF)
- Longer 2005 paper on FTM (PDF)