From ftm
Jump to: navigation, search
(Current Version)
(Older Versions)
Line 30: Line 30:
 
== Older Versions ==
 
== Older Versions ==
 
Max 5 on Mac OS X
 
Max 5 on Mac OS X
 +
* [http://ftm.ircam.fr/downloads/FTM.2.5.0.BETA.0-Max5.dmg FTM 2.5 beta release (BETA 0) for Max 5]
 
* [http://ftm.ircam.fr/downloads/FTM.2.5.0.ALPHA.5-Max5.dmg FTM 2.5 alpha release (ALPHA 5) for Max 5]
 
* [http://ftm.ircam.fr/downloads/FTM.2.5.0.ALPHA.5-Max5.dmg FTM 2.5 alpha release (ALPHA 5) for Max 5]
 
* [http://ftm.ircam.fr/downloads/FTM.2.5.0.ALPHA.4-Max5.dmg FTM 2.5 alpha release (ALPHA 4) for Max 5]
 
* [http://ftm.ircam.fr/downloads/FTM.2.5.0.ALPHA.4-Max5.dmg FTM 2.5 alpha release (ALPHA 4) for Max 5]

Revision as of 13:52, 7 May 2009

Current Version

FTM & Co

Max 5 on Mac OS X

Max 5 on Windows

Max 4.6 on Mac OS X

Max 4.6 on Windows

FTM and Max/MSP Multi-Threading (Warning)

FTM is still not entirely thread-safe. Messages or expressions that are executed in different threads (alarm, GUI/main, UDP input, etc) and simultaneously modify FTM data structures (e.g. fmat ou mat) can cause crashes. The easiest way to avoid this is to reschedule congruent accesses to FTM data structures into the same thread. The externals "pipe" or "ftm.schedule" (that now is thread-safe) with a 0 delay time would always output in the alarm ("high priority") thread while "defer" and "deferlow" can be used to reschedule messages in the Max main application (GUI) thread.

Experimental Versions

Max 5 on Mac OS X

FTM & Co 2.5.0 (for Max 5) is 100% compatible with patches created and saved with FTM & Co 2.3 and 2.4.

Older Versions

Max 5 on Mac OS X

Max 4.6 on Mac OS X

Max 4.5 on Mac OS X

Max 4.6 on Windows

Max 4.5 on Windows