{POZ, 181114}

Currently, Jonathan is developing a SuperCollider class called SynthLibrary. This class basically tries to fill the gap between live coding and (out of time) composition. The idea is to have a tool that allows to collect and catalogue synths played during live performances, turning live coding a bit more into a compositional tool and leaving traces of a performance that's very ephemeral. Instead of disappearing jsut after the show, synths are collected in a library and thus can be later reworked and reutilized. The class makes use of metadata to create categories that can be sorted by, like a tagging system - a bit like the dosctring syntax in Java. Then you can search by text, but you can also filter by categories in a non hierarchical fashion. Once a synth is selected you can play its default sounds, examples and view the source code in a separate TextView window.

{function: report}


SynthLibrary Class

{kind: title}

Signale Soirée, 26_11_18    {JR}


I've been live coding for a while, but I always feel a bit limited by the way it works for me. I mean, one thing is that a lot of things get lost. Maybe I create some really interesting synthesis process at some point, and then I change it during the performance. Then that really interesting synthesis process is lost. Or I create a whole composition over time through the performance, but then it gets lost somehow. So, one thing I was thinking about was "ok well, how can I create ways of maintaining some of the things that I create while I'm live coding?"

Experimentalstudio meeting, 05_11_2018

Jonathan Reus, David Pirrò, Hanns Holger Rutz, Daniele Pozzi

meta: true
persons: [HHR, DP, JR, POZ]
kind: conversation
origin: presentation
place: CUBE

date: 181105
keywords: [synthesis, coding, performance, live coding, SynthLibrary]