This example showcases a collection of useful temporal patterns and behaviours
that can be implemented with ossia score's temporal semantics
Without anything else, this doesn't
have any execution difference with the
event created before, the difference will
come after.
First, the various elements of score's timeline:
on their own they do nothing, they just specify
how time flows in your score.
3. An interval: the long blue
line.
An interval always connects
states.
This is what contains
processes, effects, curves,
etc.
Note that the interval
is the root element of the
score timeline.
1. A state: this little dot:
"},{"ObjectName":"CommentBlockModel","id":6,"Date":1436273536,"HeightPercentage":0.17,"HTMLContent":"\n\n2. An event: this connects
multiple states.
Two states on the same
event will always execute
together or not.
From any state you can
add another state on the same
event by selecting it,
and dragging the little
yellow cross that appears
on top-right
4. A time sync.
Time syncs connect
multiple events
(and thus multiple
states).
From any state you can
add another state on the same
time sync by selecting it, keeping
Alt / Option pressed,
and dragging the little
yellow cross that appears
on top-right.
5. A condition.
This can be applied to an event,
to implement if-then-else,
pattern-matching or
switch-case behaviours.
To create one on a state, select it
and press C or the button in the
inspector to the right.
6. Conditions span an event,
not a complete time sync:
in the following structure,
all the conditions will be evaluated
simultaneously.
The states without condition
will always execute.
The others will only execute
if their condition evaluates to true
at this point in time.
7. Triggers are used to
trigger elements of the
timeline interactively.
To create a state with
a trigger, simply double-click
in the background of the score.
Now, when you hit play it becomes
yellow : it indicates it can be triggered,
by clicking on the trigger button.
By default, floating trigger like this
one operate in an on-off manner:
- pressing the trigger triggers it
- pressing again cancels it
- pressing again re-triggers it
The auto-trigger mode in the inspector
instead re-arms the trigger as soon as
it executed, which works better for
instance for making drum machines, etc.
8. A trigger will start
all the events and states
of a time sync at the same
time, in a synchronous and
exact fashion - all event triggering
inside the score is sample-accurate
and synchronous in the
"synchronous programming"
sense, two states on the same
time sync will never execute
at a different frame.
9. Time syncs stop what's before
them when they execute
10. Intervals can have min and max
bounds.
Triggering messages before active
intervals are in their min bounds
are ignored
11. False conditions remove their
following branches from the execution
graph.
12. True conditions exist
as expected
13. Time syncs will always
wait for things before them
to have executed to move
forward
New Comment
"},{"ObjectName":"CommentBlockModel","id":21,"Date":1456121764,"HeightPercentage":0.5346666666666666,"HTMLContent":"\n\nWhen you hit play, things have to be connected
to the beginning of the document, in some way,
otherwise nothing will start automatically.