A brief introduction to FTM - Revision history

Norbert: /* Editors and file formats */

2010-01-29T10:58:32Z

‎Editors and file formats

2010-01-29T10:56:58Z

‎Data structures

2008-09-12T09:25:27Z

‎Jitter & JavaScript support

2007-06-18T12:55:03Z

2007-06-18T12:15:21Z

2007-06-18T12:15:14Z

2007-06-18T12:14:49Z

2007-06-18T12:14:26Z

2007-05-07T10:13:51Z

2007-05-07T08:13:58Z

@@ Line 87: / Line 87: @@
 == Editors and file formats ==
-The editors for FTM objects are implemented in Java and integrated into Max/MSP using mxj. Simple double-clicking on an FTM object in a patcher opens its editor.
+The editors for FTM objects are implemented in Juce and integrated into Max/MSP using mxj. Simple double-clicking on an FTM object in a patcher opens its editor.
 [[Image:About.ftm.trackeditor.gif|none|frame|
 screen shot of the track editor for score objects]]
-FTM currently supports simple text files and standard MIDI files. Import and export of SDIF files is currently being finalized and a score interchange format such as MusicXML will be supported in the near future.
+FTM currently supports simple text files, SDIF and standard MIDI files.
-Most of these import and export methods are implemented for the FTM track class as it provides a generic container for temporal sequences.
+Most of these import and export methods are implemented for the FTM ''sequence'' class as it provides a generic container for temporal sequences.
 == Jitter & JavaScript support ==

@@ Line 33: / Line 33: @@
 | dictionary of arbitrary key/value pairs
 |-
-| align="right" | '''''track'''''
+| align="right" | '''''sequence'''''
 | width="24" align="center" | ...
 | sequence of time-tagged values

← Older revision		Revision as of 09:25, 12 September 2008
Line 99:		Line 99:

	== Jitter & JavaScript support ==		== Jitter & JavaScript support ==
−	~~(from FTM 2.0)~~

	From a certain point of view one can look at FTM as something like Jitter. Like Jitter, it is a shared library installed next to the Max/MSP application. Like Jitter, it extends the set of things one can send through the connections and process by Max/MSP externals.		From a certain point of view one can look at FTM as something like Jitter. Like Jitter, it is a shared library installed next to the Max/MSP application. Like Jitter, it extends the set of things one can send through the connections and process by Max/MSP externals.

@@ Line 70: / Line 70: @@
 While basic operations of FTM objects are implemented as methods of the FTM classes, more complex interactions with FTM objects use operators in form of Max/MSP externals.
 == Operators ==
@@ Line 85: / Line 84: @@
 Operators specific to a certain field of applications are assembled to separate object sets such as Gabor for sound analysis/resynthesis and MnM for mapping and recognition techniques.
 == Editors and file formats ==
@@ Line 99: / Line 97: @@
 Most of these import and export methods are implemented for the FTM track class as it provides a generic container for temporal sequences.
 == Jitter & JavaScript support ==

← Older revision		Revision as of 12:15, 18 June 2007
Line 1:		Line 1:
−	~~__NOTOC__~~
−	~~__TOC__~~
	FTM is a shared library for Max/MSP providing a small and simple real-time object system and a set of 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 a set of optimized services to be used within Max/MSP externals.

← Older revision		Revision as of 12:14, 18 June 2007
Line 1:		Line 1:
		+	__NOTOC__
	__TOC__		__TOC__
	FTM is a shared library for Max/MSP providing a small and simple real-time object system and a set of 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 a set of optimized services to be used within Max/MSP externals.

← Older revision		Revision as of 10:13, 7 May 2007
Line 19:		Line 19:
	The FTM library and its Java editors are based on the jMax project and distributed under the Lesser GNU Public License (LGPL). The sources of FTM are available via [http://sourceforge.net/projects/ftm/ CVS at SourceForge.net]		The FTM library and its Java editors are based on the jMax project and distributed under the Lesser GNU Public License (LGPL). The sources of FTM are available via [http://sourceforge.net/projects/ftm/ CVS at SourceForge.net]

		+	__TOC__

	== Data structures ==		== Data structures ==

@@ Line 63: / Line 63: @@
 [[Image:About.ftm.object.gif|frame|none|
-<font size="-2">example of a static FTM object in a Max/MSP patcher</font>]]
+example of a static FTM object in a Max/MSP patcher]]
 They can be named within a local or global scope and marked persistent to be saved within the patcher. FTM provides a serialization mechanism to recursively save the content of objects and the contained objects.
@@ Line 82: / Line 82: @@
 [[Image:About.ftm.operators.gif|frame|none|
-<font size="-2">example of FTM externals operating on FTM objects (the MIDI parsing objects convert a MIDI byte stream into a stream of FTM MIDI events)</font>]]
+example of FTM externals operating on FTM objects (the MIDI parsing objects convert a MIDI byte stream into a stream of FTM MIDI events)]]
 Operators specific to a certain field of applications are assembled to separate object sets such as Gabor for sound analysis/resynthesis and MnM for mapping and recognition techniques.
@@ Line 94: / Line 94: @@
 [[Image:About.ftm.trackeditor.gif|none|frame|
-<font size="-2">screen shot of the track editor for score objects</font>]]
+screen shot of the track editor for score objects]]
 FTM currently supports simple text files and standard MIDI files. Import and export of SDIF files is currently being finalized and a score interchange format such as MusicXML will be supported in the near future.