From ftm
| Line 1: | Line 1: | ||
== Class ''fmat'' == | == 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 ''dict'' == | ||
| + | |||
| + | Dictionary, or lookup-table, or hash-table, of any values. | ||
| + | |||
== Class ''track'' == | == Class ''track'' == | ||
Revision as of 19:12, 13 March 2008
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 dict
Dictionary, or lookup-table, or hash-table, of any values.
Class track
A track contains 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
- 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>