Indra

Introduction

Indra is a virtual score platform for real-time music composition with live performers. A conductor at a central interface controls musical parameters such as density, pitch and volume, which are translated into notation for an ensemble reading from laptops or tablet screens. Indra is a new way of performing music that integrates traditional, improvisatory and aleatoric performance practices.

The first performance using Indra took place in 2014. The premiere composition was called Spring Flow, a chamber concerto for viola and ensemble by Drake Andersen. The soloist was Kallie Ciechomski, and the ensemble was Ensemble sans Maitre. The video above is a 2016 live performance featuring Kallie Ciechomski, viola; Mike Perdue and Jude Traxler, percussion; and live electronics performed by the composer.

In Spring Flow, the violist plays from a traditionally-notated score, while the ensemble performs using Indra. The notation for the ensemble is transcribed from the solo, resulting in an improvisatory, nonlinear accompaniment to the soloist. In the 2016 performance, the soloist's gestures were also captured, processed, and played back electronically.

Selected Performances Using Indra

August 9, 2019  • drift • Robert McClure • 4(19) Festival, Toledo Museum of Art • Toledo, OH
October 17, 2016  • Spring Flow • Drake Andersen • The Graduate Center, CUNY • New York, NY
January 28-30, 2016  • drift • Robert McClure • The Asia Society • Houston, TX
May 31, 2014 • Spring Flow • Drake Andersen • Tenri Cultural Institute • New York, NY

Development and Release Information

Version 1.1
September 18, 2014
Adds reference pitch subpatcher to receiver for vocalists to get their pitch

Version 1.0
July 7, 2014
Resolves “known issues” from Ver 0.9

Version 0.9
May 31, 2014
First performance with Indra
“Spring Flow” with Kallie Ciechomski and Ensemble Sans Maitre
Tenri Cultural Institute, New York

Used patcher dated 05 15 2014 (and receiver patch dated 05 19 2014)

Known issues:
-Sustain mode does not work
-UDP is triggered unintentionally (i.e. data was sent from master computer when updated without composer hitting “send”)
-No way to deal with stack overflow error (when filters exclude all possible gestures there’s no way to know or deal with it)
-No mode status monitors for local computers
-No global instrument labels
-Nicer interface (including subpatcher for all IP/port input by musicians)