From ftm
m |
|||
| Line 57: | Line 57: | ||
[[Category:track Class]] | [[Category:track Class]] | ||
[[Category:sequence Class]] | [[Category:sequence Class]] | ||
| − | [[Category:fmat Class]] [[Category:expr Class]] [[Category:ftm.object]] | + | [[Category:fmat Class]] |
| + | [[Category:fvec Class]] | ||
| + | [[Category:mat Class]] | ||
| + | [[Category:expr Class]] | ||
| + | [[Category:ftm.object]] | ||
Revision as of 12:52, 22 October 2010
Contents
Class fmat
Floating point matrix.
Class fvec
Reference to a row or column vector of an fmat.
Class mat
Matrix or table of any value.
Class expr
A defition of an expression. See the expression help for more info
Class dict
Dictionary, or lookup-table, or hash-table, of any values.
Class track
A track represents a time-tagged sequence of events.
About tracks, sequences, markers, bars, metrics and tempo
Each scoob track consists of four sequences:
- the events sequence of scoobs (score objects). This one is iterated over by default.
- access
- any access method is by default to the event sequence. To get that, use: ($mytrack events)
- iteration
- [ftm.iter] or [ftm.iter @mode events]
- the tempo sequence contains float values with the current tempo in bpm.
- access
- ($mytrack tempo)
- iteration
- [ftm.iter @mode tempo]
- the metric sequence contains metric events for bars and metric signature changes
- access
- ($mytrack metric)
- iteration
- [ftm.iter @mode metric]
- properties
-
- num
- bar number
- meter
- metric signature as string, e.g. 4/4
- the marker sequence contains marker events that can bear any property, but above all cue, label (N.B.: there is also a separate cue property of the scoob score object)
- access
- ($mytrack markers)
- iteration
- [ftm.iter @mode markers]
- properties
-
- cue
- cue number
- label
- text
- <any>
- <any type>