ftm - User contributions [en]

How can I work with lists passed to an ftm.mess object?

2010-08-05T10:51:02Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3. Let's say we would like to only let lists of a certain length go through, you need to somehow get the list as a whole. This can be done with $*i, which gets the input list at that specific inlet rather than the corresponding element from that list.

($*1) will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial. The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the input variables ($1, $2...). So you can safely ask for the length of the input for use in the if statement and use the input again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)

with 4 5 6 as the input will give you 4, whereas

(if 0 $*1)

with the same input will give you 5. The 6 gets lost in this construction.

So, what if we need to get the list through? We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

* check the output tuples as list checkbox in the ftm.mess inspector
* (l (if ((llen $*1) == 3) {$*1}))

FAQ

2010-08-05T10:50:42Z

Laurens van der Wee: /* The FTM Message Box ftm.mess */

This FAQ aims to be an interactively built-up documentation of how to use FTM. It depends on your (the user's) input, be it only with questions. (Just insert a new page with your question, and mark it in the title as unanswered.)

* [[:Category:FAQ | FAQ Index]]
* [[Special:Categories | List of Documentation Categories]]

== General ==

* [[FTM, MnM, Gbr - What the hell does all this mean?]]
* [[How do I get help?]]

=== Installation ===

* [[Why no sound from some tuturialpatches?]]

=== Basic Concept ===

=== Expressions ===

* [[Expressions | What is the syntax in an FTM message box?]]

=== Interaction with Max/MSP ===

* [[Max objects having problems with FTM data objects | Why can't I route a singular FTM object?]]

* other [[Pitfalls for Maxers]]

=== Building Max Standalone with FTM inside ===
* [[How do I create Max standalones (collectives/applications) using FTM?]]

== FTM External Objects ==

=== The FTM Message Box [[ftm.mess]] ===

* [[Expressions | What is the syntax in an FTM message box?]]
* [[Message_Box | How do I get multiple inlets for an FTM message box?]]
* [[How to insert several init expressions in ftm.mess's inspector?]]
* [[Expression Class Arguments| How to pass an argument in a method involving an expression object?]]
* [[How can I work with lists passed to an ftm.mess object?]]

=== The FTM Object and Name Definition Box [[ftm.object]] ===

* [[I have a global fmat in an abstraction and the main patch, but get the error "cannot globalize 'xxx' (name stays local)"?]]

== FTM Data Classes ==

=== The fmat Class: Matrix Operations ===

* How to set and get values or vectors in an fmat?
* How do I import sound data into FTM?
* How does matrix import-export work in general?
* How to crop or access parts of an fmat?

=== The track Class: Sequence of Values ===

* How do I import markers into a track?
* [[How to retrieve the time index in a track]]?
* [[FTM_Classes#Class_track|How to access markers, bars, metrics and tempo in a track of type scoob]]

=== The dict Class: Dictionary/Lookup Table/Associative Array ===

* [[How do I access values stored on a dictionary?]]

=== The expr Class: An expression as a data object ===

* [[Expression Class Arguments| How do I pass arguments to an expression in an expr object?]]

[Other Data Classes...]

== Exchanging Data ==

* How can I convert FTM data to Max data?
* How can I convert FTM data to and from Jitter?

=== SDIF Integration ===

* [[How do I import and export SDIF data into FTM]]?
* How do I import markers into a track?
* [[How to record multiple data streams into a single SDIF-file using ftm.sdif.write?]]

[[Category:FAQ]]

Lists & Tuples

2010-08-05T10:48:54Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which gets the input list at that specific inlet rather than the corresponding element from that list.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the input variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use the input again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)

with 4 5 6 as the input will give you 4, whereas

(if 0 $*1)

with the same input will give you 5. The 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

* check the output tuples as list checkbox in the ftm.mess inspector
* (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:47:38Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which gets the input list at that specific inlet rather than the corresponding element from that list.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the input variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use the input again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

* check the output tuples as list checkbox in the ftm.mess inspector
* (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:47:24Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which gets the input list at that specific inlet rather than the corresponding element from that list.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the input variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use the input again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

* I check the output tuples as list checkbox in the ftm.mess inspector
* II (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:47:04Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which gets the input list at that specific inlet rather than the corresponding element from that list.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the input variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use the input again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

I check the output tuples as list checkbox in the ftm.mess inspector

II (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:46:40Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which gets the input list at that specific inlet rather than the corresponding element from that list.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the input variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use the input again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

I check the output tuples as list checkbox in the ftm.mess inspector
II (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:42:41Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which stops ftm.mess from 'spreading out' the elements of the incoming list over successive inlets.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the internal variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use it again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

I check the output tuples as list checkbox in the ftm.mess inspector
II (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:42:12Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analoguous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which stops ftm.mess from 'spreading out' the elements of the incoming list over successive inlets.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the internal variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use it again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

I check the output tuples as list checkbox in the ftm.mess inspector
II (l (if ((llen $*1) == 3) {$*1}))

Lists & Tuples

2010-08-05T10:41:56Z

Laurens van der Wee:

Working with inputs in the ftm.mess object is analogous to the standard Max message object: $1 refers to inlet 1 etc. Lists are also 'spread out', so

($1 + $2)

with '1 3' in the left inlet will give you the sum of 1 and 3.
Let's say we would like to only let lists of a certain length go through, you need to somehow get the list ''as a whole''. This can be done with $*i, which stops ftm.mess from 'spreading out' the elements of the incoming list over successive inlets.

($*1)
will output the input list.

Next, we check for the length and decide whether or not to output:

(if ((llen $*1) == 3) $*1) --> this will NOT work!

In this case, the order in which things get evaluated inside the ftm.mess object, is crucial.
The two $*1 statements are independent, in that there is, in this case, no operation that actually modifies the internal variables ($1, $2...).
So you can safely ask for the length of the input for use in the if statement and use it again to output if the statement is true. The problem in this case is that the list gets evaluated first and the first two elements are then used as the options for the if statement. So for example

(if 1 $*1)
with 4 5 6 as the input will give you 4, whereas
(if 0 $*1)
with the same input will give you 5

the 6 gets lost in this construction.

So, what if we need to get ''the list'' through?
We have to make it an object and pass it as a whole. This can be any ftm.object, let's say a tuple:

(if ((llen $*1) == 3) {$*1}) --> this will work, but you end up with a tuple. So finally there are two ways to handle this inside the same object:

I check the output tuples as list checkbox in the ftm.mess inspector
II (l (if ((llen $*1) == 3) {$*1}))

FAQ

2010-08-05T10:06:35Z

Laurens van der Wee: /* The FTM Message Box ftm.mess */

This FAQ aims to be an interactively built-up documentation of how to use FTM. It depends on your (the user's) input, be it only with questions. (Just insert a new page with your question, and mark it in the title as unanswered.)

* [[:Category:FAQ | FAQ Index]]
* [[Special:Categories | List of Documentation Categories]]

== General ==

* [[FTM, MnM, Gbr - What the hell does all this mean?]]
* [[How do I get help?]]

=== Installation ===

* [[Why no sound from some tuturialpatches?]]

=== Basic Concept ===

=== Expressions ===

* [[Expressions | What is the syntax in an FTM message box?]]

=== Interaction with Max/MSP ===

* [[Max objects having problems with FTM data objects | Why can't I route a singular FTM object?]]

* other [[Pitfalls for Maxers]]

=== Building Max Standalone with FTM inside ===
* [[How do I create Max standalones (collectives/applications) using FTM?]]

== FTM External Objects ==

=== The FTM Message Box [[ftm.mess]] ===

* [[Expressions | What is the syntax in an FTM message box?]]
* [[Message_Box | How do I get multiple inlets for an FTM message box?]]
* [[How to insert several init expressions in ftm.mess's inspector?]]
* [[Expression Class Arguments| How to pass an argument in a method involving an expression object?]]
* [[Lists & Tuples | How can I work with lists passed to an ftm.mess object?]]

=== The FTM Object and Name Definition Box [[ftm.object]] ===

* [[I have a global fmat in an abstraction and the main patch, but get the error "cannot globalize 'xxx' (name stays local)"?]]

== FTM Data Classes ==

=== The fmat Class: Matrix Operations ===

* How to set and get values or vectors in an fmat?
* How do I import sound data into FTM?
* How does matrix import-export work in general?
* How to crop or access parts of an fmat?

=== The track Class: Sequence of Values ===

* How do I import markers into a track?
* [[How to retrieve the time index in a track]]?
* [[FTM_Classes#Class_track|How to access markers, bars, metrics and tempo in a track of type scoob]]

=== The dict Class: Dictionary/Lookup Table/Associative Array ===

* [[How do I access values stored on a dictionary?]]

=== The expr Class: An expression as a data object ===

* [[Expression Class Arguments| How do I pass arguments to an expression in an expr object?]]

[Other Data Classes...]

== Exchanging Data ==

* How can I convert FTM data to Max data?
* How can I convert FTM data to and from Jitter?

=== SDIF Integration ===

* [[How do I import and export SDIF data into FTM]]?
* How do I import markers into a track?
* [[How to record multiple data streams into a single SDIF-file using ftm.sdif.write?]]

[[Category:FAQ]]

FAQ

2010-08-05T10:06:23Z

Laurens van der Wee: /* The FTM Message Box ftm.mess */

This FAQ aims to be an interactively built-up documentation of how to use FTM. It depends on your (the user's) input, be it only with questions. (Just insert a new page with your question, and mark it in the title as unanswered.)

* [[:Category:FAQ | FAQ Index]]
* [[Special:Categories | List of Documentation Categories]]

== General ==

* [[FTM, MnM, Gbr - What the hell does all this mean?]]
* [[How do I get help?]]

=== Installation ===

* [[Why no sound from some tuturialpatches?]]

=== Basic Concept ===

=== Expressions ===

* [[Expressions | What is the syntax in an FTM message box?]]

=== Interaction with Max/MSP ===

* [[Max objects having problems with FTM data objects | Why can't I route a singular FTM object?]]

* other [[Pitfalls for Maxers]]

=== Building Max Standalone with FTM inside ===
* [[How do I create Max standalones (collectives/applications) using FTM?]]

== FTM External Objects ==

=== The FTM Message Box [[ftm.mess]] ===

* [[Expressions | What is the syntax in an FTM message box?]]
* [[Message_Box | How do I get multiple inlets for an FTM message box?]]
* [[How to insert several init expressions in ftm.mess's inspector?]]
* [[Expression Class Arguments| How to pass an argument in a method involving an expression object?]]
* [[Lists & Tuples | How can I work with lists passed to an fmt.mess object?]]

=== The FTM Object and Name Definition Box [[ftm.object]] ===

* [[I have a global fmat in an abstraction and the main patch, but get the error "cannot globalize 'xxx' (name stays local)"?]]

== FTM Data Classes ==

=== The fmat Class: Matrix Operations ===

* How to set and get values or vectors in an fmat?
* How do I import sound data into FTM?
* How does matrix import-export work in general?
* How to crop or access parts of an fmat?

=== The track Class: Sequence of Values ===

* How do I import markers into a track?
* [[How to retrieve the time index in a track]]?
* [[FTM_Classes#Class_track|How to access markers, bars, metrics and tempo in a track of type scoob]]

=== The dict Class: Dictionary/Lookup Table/Associative Array ===

* [[How do I access values stored on a dictionary?]]

=== The expr Class: An expression as a data object ===

* [[Expression Class Arguments| How do I pass arguments to an expression in an expr object?]]

[Other Data Classes...]

== Exchanging Data ==

* How can I convert FTM data to Max data?
* How can I convert FTM data to and from Jitter?

=== SDIF Integration ===

* [[How do I import and export SDIF data into FTM]]?
* How do I import markers into a track?
* [[How to record multiple data streams into a single SDIF-file using ftm.sdif.write?]]

[[Category:FAQ]]

FAQ

2010-08-05T09:22:03Z

Laurens van der Wee: /* The FTM Message Box ftm.mess */

This FAQ aims to be an interactively built-up documentation of how to use FTM. It depends on your (the user's) input, be it only with questions. (Just insert a new page with your question, and mark it in the title as unanswered.)

* [[:Category:FAQ | FAQ Index]]
* [[Special:Categories | List of Documentation Categories]]

== General ==

* [[FTM, MnM, Gbr - What the hell does all this mean?]]
* [[How do I get help?]]

=== Installation ===

* [[Why no sound from some tuturialpatches?]]

=== Basic Concept ===

=== Expressions ===

* [[Expressions | What is the syntax in an FTM message box?]]

=== Interaction with Max/MSP ===

* [[Max objects having problems with FTM data objects | Why can't I route a singular FTM object?]]

* other [[Pitfalls for Maxers]]

=== Building Max Standalone with FTM inside ===
* [[How do I create Max standalones (collectives/applications) using FTM?]]

== FTM External Objects ==

=== The FTM Message Box [[ftm.mess]] ===

* [[Expressions | What is the syntax in an FTM message box?]]
* [[Message_Box | How do I get multiple inlets for an FTM message box?]]
* [[How to insert several init expressions in ftm.mess's inspector?]]
* [[Expression Class Arguments| How to pass an argument in a method involving an expression object?]]
* [[Lists & Tuples | How can I work with lists passed to a fmt.mess object?]]

=== The FTM Object and Name Definition Box [[ftm.object]] ===

* [[I have a global fmat in an abstraction and the main patch, but get the error "cannot globalize 'xxx' (name stays local)"?]]

== FTM Data Classes ==

=== The fmat Class: Matrix Operations ===

* How to set and get values or vectors in an fmat?
* How do I import sound data into FTM?
* How does matrix import-export work in general?
* How to crop or access parts of an fmat?

=== The track Class: Sequence of Values ===

* How do I import markers into a track?
* [[How to retrieve the time index in a track]]?
* [[FTM_Classes#Class_track|How to access markers, bars, metrics and tempo in a track of type scoob]]

=== The dict Class: Dictionary/Lookup Table/Associative Array ===

* [[How do I access values stored on a dictionary?]]

=== The expr Class: An expression as a data object ===

* [[Expression Class Arguments| How do I pass arguments to an expression in an expr object?]]

[Other Data Classes...]

== Exchanging Data ==

* How can I convert FTM data to Max data?
* How can I convert FTM data to and from Jitter?

=== SDIF Integration ===

* [[How do I import and export SDIF data into FTM]]?
* How do I import markers into a track?
* [[How to record multiple data streams into a single SDIF-file using ftm.sdif.write?]]

[[Category:FAQ]]