Flow: concept & technical details
Flow was a collaboration between staff and students from QUT’s music program. Final year production students were tasked with running the project on the day, as I was occupied downstairs performing on the Garden of Minuscule Delights show. The concept behind this project was the idea of making the flow of music and sound analogous to the flow of water.
From the outset I wanted to see if Ableton’s Link technology could be used on a large scale event. Link is amazing. Whoever came up with the concept was having a really good day in the office. Unlike previous iterations of sync, wireless or otherwise, there is no master/slave arrangement. Instead all devices lock to a single clock. If one device changes this clock, all others change with it. This meant we could have:
Two large control rooms with large format analogue consoles recording microphone captured material from four live rooms. We also captured performances from Indian group Filter Coffee via a skype connection in one of these control rooms.
Four iPad apps running Patterning, Fugue Machine, TriqTraq and Borderlands, with the first three apps wirelessly synced to Link. Patterning and TriqTraqs provided rhythmic material, with Fugue Machine responsible for all the sequenced synthesised sound. We sampled various water sounds, and then placed them in Borderlands, a granular sampler, for textural atmospheric sounds.
A Make Noise Shared system. We clocked this modular synth system off a metronome output fed from an iPhone connected to the Link network and running Maschine Jam. Not perfect, but it worked and kept the Rene sequencer in time with the rest of the building.
These eight elements (2 x mono feeds from each control room capturing live material and 4 x mono iPad feeds) then fed into our SSL AWS desk on the other side of the studio complex. We took direct outs from each of the channels and daisy-chained a series of small format desks in the large live space. Audience members could then put on a pair of headphones and individually re-balance and create their own unique mix of the current state of Flow.
We used a hidden, password protected network that used the existing QUT network infrastructure to run Link. This prevented any member of the public from joining the session and being able to change the tempo. Early tests with ad-hoc networks demonstrated the difficulty in running wireless sync over a large distance and through concrete walls, but the custom network in place worked flawlessly throughout the day.
Each of the two main recording rooms had an Ableton template set up. This allowed students to capture long recordings on one track, and then edit, trim and warp them into time, process them with effects (e.g. reverbs, delays, EQs, pitch shifting, etc.) and create a series of clips that could then be sent downstream to the final workstation room.
A student in each of the two control rooms was responsible for capturing performances, communicating with the performer or conductor and ultimately deciding which recordings were then processed and looped before being sent downstream. Each performance group was able to play through a few times or, if they were improvising, spend a little time working on ideas. It was the job of the production student to maintain communication and let them know when they were being recorded, and how long they were going to be recorded for. The performances hinged on people feeling comfortable, and knowing when they’re being recorded. Groups were giving headphones with rhythmic loops to perform to; we felt this would work better than a simple click track.
Once a loop had been captured, this process repeated. This maintained variety throughout the day; if you were to visit the room three times during the eight hours it ran, you were likely to hear quite different material each time. Students could send a captured loop downstream, while then working on additional loops. I call them loops, but this meant any piece of musical material that was captured so that it could be repeated. It may have been two simple guitar chords, a reversed piano note, a full choir droning for two minutes, whatever. The operator needed to be making musical decisions based on the material they were being provided with. This also meant that the output being sent to the final workstations could change even when the audience group were in the final room, with each room’s operator moving between different Ableton clips, made up of these newly recorded loops. This created more movement in, what was otherwise, quite a static overall piece.
The video below is a walk-through of the event, demonstrating the live rooms, iPad room and final workstation room. There’s also a video demonstrating tempo changes on an iPhone that would change the tempo on all Link-enabled devices (3 x Ableton workstations and 3 x iPads) across the entire floor.