Event: Livecoding at the Shunt, London & a few lessons learned


Initially conceived as 'Voices Slowly Talk To Me,' this piece quickly took on a life of its own, demonstrating the unpredictable nature of livecoding. This recording is my second experiment with capturing an Impromptu performance, showcasing a soundscape that has moved beyond its original concept.

It was recently performed live at Shunt in London, where, thanks to the support of the toplap crew crew, I managed to navigate the various mistakes and unexpected delays to reach the finish line.

shunt-livecoding-1.png

shunt-livecoding-1.png

Livecoding practice: lessons learned

Somehow I'm becoming wiser with doing this type of stuff, you know, just trying to learn from past experiences. So here're a few tips I matured in the last weeks:

  • keep it simple. Especially when playing live. Long and convoluted functions are a giant source of errors especially when you're a bit tense
  • use 'paste' templates. Stuff like the pb:cb function that comes by default with Impromptu. At the beginning I thought it wouldn't look too good, cause you've gotta show that you're coding the whole thing from scratch. But actually, when you're livecoding time is very very precious and what you want to focus on is sound, primarily (well at least this is what I like to do). It's also important to remember that many other environments for live performance are much much higher level than Impromptu - meaning that it's quicker to emit sounds or musical structures and change their properties... so let's make sure we're not comparing apple and oranges here!
  • make variations often. Even if they look stupid to you, change something, add another melody, double the drumkit, stuff like that. The audience is more interested in new audio-visual things happening that in seeing you code a Bach's prelude.
  • exercise a lot. I initially felt weird about this, mainly because playing with Impromptu means coding, and when I code I usually take my time and think. But livecoding transforms the coding practice into a musical performance. Which means that you don't have time to think, things should just come out automatically and sound good. Only then you can take the freedom of 'jamming' without a plan. I play guitar, and that's exactly how it works there... I must have forgotten about it. When playing a song I can't lose time trying to remember how to lay out the fingers on the neck, that has to happen automatically.

That's it for now - I'll touch base again about this when the next live coding performance will happen! Rock on live-coders!

Cite this blog post:


Michele Pasin. Event: Livecoding at the Shunt, London & a few lessons learned. Blog post on www.michelepasin.org. Published on Oct. 7, 2009.

Comments via Github:


See also:

2017


paper  Fitting Personal Interpretation with the Semantic Web: lessons learned from Pliny

Digital Humanities Quarterly, Jan 2017. Volume 11 Number 1


2014


paper  Moving Early Modern Theatre Online: The Records of Early English Drama introduces the Early Modern London Theatres Website

New Technologies and Renaissance Studies II, ed. Tassie Gniady and others, Medieval and Renaissance Texts and Studies Series (Iter Academic Press), Dec 2014. Volume 4


2009





paper  Meaning and Structure in the London Theatres Bibliography

The Fifty-Fifth Annual Meeting of the Renaissance Society of America, Los Angeles, CA, USA, Mar 2009.