From ftm
Jump to: navigation, search
(Experimental versions)
(Experimental versions)
Line 20: Line 20:
 
* [http://ftm.ircam.fr/downloads/FTM.2.5.ALPHA.1-Max5ub.dmg FTM 2.5 alpha release (ALPHA 1) for Max 5]
 
* [http://ftm.ircam.fr/downloads/FTM.2.5.ALPHA.1-Max5ub.dmg FTM 2.5 alpha release (ALPHA 1) for Max 5]
  
With this version one can load and run FTM & Co patches in Max 5 without editing nor saving in the new Max 5 file format. The graphical objects such as ''ftm.vecdisplay'' appear empty.
+
With this version one can load and run FTM & Co patches in Max 5 without editing the the FTM message box (''ftm.mess'') and definitions (''ftm.object'') nor saving in the new Max 5 file format. The graphical objects such as ''ftm.vecdisplay''and ''ftm.editor'' are loaded but don't display anything yet.
  
 
== Older versions ==
 
== Older versions ==

Revision as of 11:10, 20 November 2008

Current version

FTM & Co 2.3

Max 4.6 on Mac OS X

Max 4.6 on Windows


Known issue:

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

With this version one can load and run FTM & Co patches in Max 5 without editing the the FTM message box (ftm.mess) and definitions (ftm.object) nor saving in the new Max 5 file format. The graphical objects such as ftm.vecdisplayand ftm.editor are loaded but don't display anything yet.

Older versions

Max 4.6 on Mac OS X

Max 4.5 on Mac OS X

Max 4.6 on Windows

Max 4.5 on Windows