The offset of the collection time relative to the loop start, see above.
| key | value |
|---|---|
| default | 0 |
| range | full |
The color index of the region. The meaning of this value is determined by the UI.
| key | value |
|---|---|
| default | 0 |
| range | [0, 41] |
A user-assigned name for the region.
The duration of the region on the timeline, see above.
| key | value |
|---|---|
| default | 15360 |
| range | full |
If is_enabled=false, the audio engine won't produce audio as a result of this region.
| key | value |
|---|---|
| default | true |
The duration of the loop in the region, see above.
| key | value |
|---|---|
| default | 15360 |
| range | full |
The offset of the loop start in the region relative to region start, see above.
| key | value |
|---|---|
| default | 0 |
| range | full |
The position of the region on the timeline, see above.
| key | value |
|---|---|
| default | 0 |
| range | full |
Regions arrange content on the timeline, such as audio, midi melodies, automation events, and others. They're not an entity themselves but a submessage of the different region entities.
A region can be considered a "view" of a collection of notes, automation points, or an audio sample. Collections position "events" (notes, automation points, an audio samples) in collection-local time, on a timeline that's neither looped nor capped in any way.
The parameters of the region below then add information on:
For a simple looped region, set parameters as follows:
For more complex setups, here's an extremely intuitive diagram of the relationship between the different parameters:
In the diagram above, this would result in the following collection start ticks:
Because the collection start tick can be determined by:
The raison d'être of the collection_offset_ticks is that multiple regions can point to the same collection, and there needs to be a way to position the collection relative to the region start without re-positioning the events inside the collection.