i-score is specifically designed for interactive scenarios, whether it is for live performance or for interactive art installation, for instance. Thus it provides a number of way to interactively use your timeline and control its execution live.
Global control of execution
By default, i-score execution works in a similar way to most digital audio or video workstations: automation boxes are played as the playhead run across the timeline. In the screenshot below, you can see that each automation box has its own progress bar displaying where the playhead is in the automation.
Global speed of execution can be changed while i-score play your scenario. This can be done by using the slider in i-score’s top-bar to modulate the unity speed of execution. A speed factor of 0.5 will play your scenario twice as slow, whereas a speed factor of 2 will play your scenario twice as fast. For instance, in a live performance context, you might want to slow down a bit the execution of your scenario to synchronise manually to some actions happening on stage.
Interactive triggering of automation
So far we saw that the triggering is done according to the position of the automation boxes in the timeline: the automation start as the global playhead crosses its start point. Simple.
However, when writing your interactive scenario, there are some cases where you want a specific automation to run at some point but cannot know when. For example, when writing the scenario of an interactive art installation, you know that an automation will start playing whenever a visitor enters the exhibition space or passes by a sensor, but you can not know when he will do so. To help with that, i-score let you set that an automation box will be triggered interactively. We can add a « trigger point » to a box by clicking one of the handle at the box’s top corners as illustrated below.
When done, the automation box display a flag at its corner (start point, in our case). Now when playing our scenario, the automation will not start as the global playhead crosses its start point and will have to be triggered dynamically.
As illustrated in the video below, when playing our scenario, the interactive automation box flag turns green when it is ready to be triggered until it is started by a mouse click or when receiving the OSC message displayed above the box (
/'box name'/start. When playing, the interactive automation box’s flag turns red until it is done.