From ftm
| Line 2: | Line 2: | ||
== real-time object system for Max/MSP == | == real-time object system for Max/MSP == | ||
[[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. | [[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]] = | [[FTM]] = | ||
| Line 8: | Line 10: | ||
* file import/export (SDIF, MIDI, ...) | * file import/export (SDIF, MIDI, ...) | ||
* operators (expressions and externals) | * operators (expressions and externals) | ||
| − | |||
| − | |||
[[FTM]] is the basis of various specific libraries, such as the [[Suivi | suivi]] score-following objects and the object sets [[Gabor]] and [[MnM]]. | [[FTM]] is the basis of various specific libraries, such as the [[Suivi | suivi]] score-following objects and the object sets [[Gabor]] and [[MnM]]. | ||
| Line 15: | Line 15: | ||
== FTM object sets == | == FTM object sets == | ||
* [[FTM]] ... basic functionalities | * [[FTM]] ... basic functionalities | ||
| − | * [[Gabor]] ... multi-representation signal processing | + | * [[Gabor]] ... multi-representation overlap-add signal processing |
* [[MnM]] ... classification and recognition | * [[MnM]] ... classification and recognition | ||
| − | * [[Suivi]] ... HMM score following for audio and MIDI peformance input | + | |
| + | * [[Suivi]] ... HMM score following for audio and MIDI peformance input (not included to the free release) | ||
Revision as of 13:55, 26 November 2006
real-time object system for Max/MSP
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 =
- data structures
- visualization/editors
- file import/export (SDIF, MIDI, ...)
- operators (expressions and externals)
FTM is the basis of various specific libraries, such as the suivi score-following objects and the object sets Gabor and MnM.
FTM object sets
- FTM ... basic functionalities
- Gabor ... multi-representation overlap-add signal processing
- MnM ... classification and recognition
- Suivi ... HMM score following for audio and MIDI peformance input (not included to the free release)