From ftm
Jump to: navigation, search
Line 14: Line 14:
  
 
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.
 
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 ==
 +
 +
* [http://ftm.ircam.fr/downloads/FTM.2.5.ALPHA.0-Max5.dmg FTM 2.5 alpha version (ALPHA 0) for Max 5 on Mac OS X]
  
 
== Older versions ==
 
== Older versions ==
Line 59: Line 63:
  
 
* [http://ftm.ircam.fr/downloads/ftm.release.txt FTM 1.7 Release Notes]
 
* [http://ftm.ircam.fr/downloads/ftm.release.txt FTM 1.7 Release Notes]
 
== Experimental versions ==
 
Max 2.5 alpha version 0 for Max 5
 

Revision as of 10:33, 3 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

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