ANTESCOFO Case Study
2.1.1.1. ANTESCOFO
ANTESCOFO is a score-following system that enables to code interactions between the instrumental parts and the computer-generated parts by providing a proprietary programming language [Giavitto, Cont and Echeveste, 2015]. ANTESCOFO is an event based customizable score-following. Accordingly, its most important programming entities are events and actions [Giavitto, Cont, and Echeveste, 2015]. Figure 2.10 shows a sample code in ANTESCOFO language with events and actions; Events are symbolic elements in the score to be identified by the score-following core, and actions are triggered commands associated with events (example taken from the Antescofo v 0.8l official download) [Giavitto, Cont and Echeveste, 2015].
Figure 2.10. ANTESCOFO Sample Code.
In Figure 2.10, the NOTE label identifies the event of a note with pitch C4 and symbolic duration one-beat. The inside labels are actions triggered when an event is detected by the score-following core engine. This short example shows clearly the similarity between ANTESCOFO and Music-N Language where sequential-symbolic time events are mapped to commands. In summary, ANTESCOFO programming-language design is event-driven and reactive.
One consequence of this event-driven (atomic) approach is that horizontal logic flow in the score became a secondary role in the logic representation, …show more content…
Therefore, it’s the author itself and not the tool who should define the creative path, so tools should be designed
ANTESCOFO is a score-following system that enables to code interactions between the instrumental parts and the computer-generated parts by providing a proprietary programming language [Giavitto, Cont and Echeveste, 2015]. ANTESCOFO is an event based customizable score-following. Accordingly, its most important programming entities are events and actions [Giavitto, Cont, and Echeveste, 2015]. Figure 2.10 shows a sample code in ANTESCOFO language with events and actions; Events are symbolic elements in the score to be identified by the score-following core, and actions are triggered commands associated with events (example taken from the Antescofo v 0.8l official download) [Giavitto, Cont and Echeveste, 2015].
Figure 2.10. ANTESCOFO Sample Code.
In Figure 2.10, the NOTE label identifies the event of a note with pitch C4 and symbolic duration one-beat. The inside labels are actions triggered when an event is detected by the score-following core engine. This short example shows clearly the similarity between ANTESCOFO and Music-N Language where sequential-symbolic time events are mapped to commands. In summary, ANTESCOFO programming-language design is event-driven and reactive.
One consequence of this event-driven (atomic) approach is that horizontal logic flow in the score became a secondary role in the logic representation, …show more content…
Therefore, it’s the author itself and not the tool who should define the creative path, so tools should be designed