The cultural differences between Live Coding and Algorave

Hey all. I’ve been spending some time on chat.toplap.org recently and I saw an interesting discussion take place in which someone was pointed in the direction of an algorave room and said, in essence, that they did not really want to get involved in algorave, but rather wanted to involve themselves in live coding generally. This got me thinking about the Live Coding and Algorave. Are they the same movement, or just closely linked? If they are different movements, how are they culturally similar/different? If any of you could clear this up I’d be super thankful.

I guess live coding is a set of techniques, and a loose community/group of communities around them, a lot of them under the TOPLAP umbrella. Algorave is a kind of event, and again the community around those events. There’s a lot of overlap, but algorave is a) more specific, in that it’s around dance music+visuals and related activities, and b) more general, as it’s not just about live coding but also other ways of making algorithmic music.
In practice there’s a lot of overlap. Algoraves can have a wide spectrum of styles and intensities, sometimes chill-out rooms… But if e.g. repetitive dance music isn’t your thing, or you want to focus on ‘slow coding’ rather than higher pressure intensive performances, then there are alternatives!

1 Like

It’s funny because from where I am, when algoraves came about there wasn’t a lot of opportunity to experience algorithmic dance music outside of a warp records party… Computer music events were mostly about electroacoustic/acousmatic/noise music. Now to some extent it’s hard to make people realise that live coding isn’t all about techno…

This has made me realise I kind of have no idea if there are live coding events that aren’t algoraves. The two types of event I play have either been billed as algoraves (and I’m on in the chillout/weird stuff room) or they’re indiepop shows. Are there others?

1 Like

Not that I know of, apart from algorumba in South America… We need more names for these things!

2 Likes

I use this diagram when I’m teaching workshops

4 Likes

The folk at Netherlands Coding Live run lots of non-algorave live coding events - I was lucky enough to play one with TYPE earlier this year and they have a super community - https://netherlands-coding-live.github.io/

1 Like

But I also wonder really why we keep asking this question (and I’m including myself in that).

Live coding is like a technique or instrument rather than a genre I guess. So it’s like asking about guitar shows rather than punk shows (for example). Algorave is a bit more like a genre but almost more akin to something like ‘an open mic night’ in that it is about the format rather than the style or technique…

Maybe easiest not to think about it :stuck_out_tongue:

I also disagree with Alex in that I don’t think we need more names for things that can be misconstrued as the new future of something or other :stuck_out_tongue:

Yes, the Algo~Rhythms event in Rotterdam organized by @JoChicau is a great example of a livecoding event that is not focussed on Algoraves. I also hosted a few Coding Jamsessions that focussed on short (10min) improvised coding, which resulted more in sounddesign/ambient/noise, but the results were really just all over the place.

5 Likes

@heavy-lifting you are awesome hope we get to play someday in the future. Indeed as @Timo mentioned we are trying to make explore all possible approaches to live-coding and Algo-Rhythms is a very good example of this.
I think one of the most beautiful things about Toplap and live-coding in general is the lack of preconceptions and rules on how to express your art with these tools and a generally very opened and receptive community.

The reason I raised Netherlands Live Coding is I think we can learn a lot in the UK from how they organise. I can only hope to emulate the super positive and welcoming energy of @Timo, @JoChicau, @eerieear & pals <3

Algorave has an amazing profile here (in the UK) due to a lot of hard work from people like @yaxu et al - which unfortunately goes along with a lot of misconception about algorave (e.g. we are djs, we want to replace djs, we are dj’s from the future etc :smiley:) - so I think that can cause us to suffer a bit from algorave=live coding.

^^^ Yes very much so!!!

4 Likes

In the beginning, when my coding was still slower, I leaned heavily towards the ambient/drone side in my live coding practice (nowadays it’s more eclectic). I was a bit annoyed that the whole Live Coding thing was so heavily leaning towards (or identified with) Algorave, because there’s much more possibilities in Live Coding

The ICLC (at least the ones i participated in) usually showed a good spectrum, I think … from Algorave over mechanical pianos, live coding on humans, to one-handed live coding. I really like that.

I guess the reason that Algorave became somewhat predominant is that it’s one of the most accessible types of algorithmic music … people like to dance.

Last year I organized an ambient concert on 8 channels and named it Algobiente … works nice in Spanish (algo bien → something good)

2 Likes

Interesting topic really.

How would you guys call music made in the studio with live-coding tools ? Algorithmic music ? Something else ?

Not that it matters much, I’m genuinely curious though.

From what I gather, the incredible values if such tools « in the studio » to write music seems to be often overlooked in favor of what they offer in a live context.

1 Like

I call it algorithmic music, coded music…
I’m not in love with the “algorave” definition, it reminds me of high people dancing on a straightforward kick drum in the sunday morning :smiley:
Not my cup of tea

The word RAVE in Algo-rave I don’t think refers to a specific musical genre rather to the spirit of the open party where the events happens. If we track back to the origins, live coding has roots in academia with researchers like Pietro Grossi (for sure there are a lot more).
The term Algorave for obvious reason doesn’t come from there since academic dislike club music and want to distance themselves from it (at least most of them in my experience).

I think live coding is a mindset to approach technology, a paradigm shift of our vision of software, from a tool, to a concept that continuously evolves (both individually and collectively, both during performance and during development sessions).
Algorave is the context where this becomes a collective ritual and a form of entertainment which brings a set of idealistic principles.

What I think we miss in this equation is exactly… how does this sounds?
I think is cool that this is a open question, because brings really a lot of diversity. But ultimately is not about how you do things, but what you are communicating. A test I havebeen trying to do lately is to do live coding without any projection or explanation, if the audience feels and understands that is a real-time improvisation process then I think you are on a good path.

Live coding is a lot of things and it appeals to very different types of people including: 1) algorithmic musicians, 2) modern musicians interested by system-based, cybernetic-based, rule-based composition 3) music improvisers with jazz / free music influences 4) rave / techno / club people seeking new tools 5) open-source / open-hardware people 6) musicians willing to use their computer as an instrument, 7) musicians embracing experimentation on the sonic level (DSP) or the software level, etc… This is just a subset, but enough to get an idea.

IMO live coding is sitting perfectly at the edge and building connexions between very different people that would have stayed in their own niche if no common tool or framework were pushing them to be aware of their resemblances. I see the technique of live coding as a common ground between almost all of the experimental branches of music that sprung out of the rich history of XXth century music. One of the most distinctive features of the scene is that there is almost no boundary between technicians and artists, which is not that common if you think about it.

The technique itself is all about confronting the very notion of software and algorithm. It looks a bit like a crowd of people having a strong and sudden emotional reaction to the way software is being designed since the 90s because they see so much more in software than just creating nicely packaged applications with limited interaction, good looking but constrained GUIs, etc… They propose an alternative where we design computing devices around a rich and profound interaction with the human operator, using language as a medium. Live coding tools without humans are not playing any music, and the technique doesn’t make sense without strong interaction and human involvement. It doesn’t say anything about the music being played, it could be live coding an orchestra, a group of singing mices or a huge techno system.

In comparison, Algoraves are social. It uses clubs / bars / concert halls as a way to reach out to the world, to include other musicians and listeners in the algorithmic process. It is more than often club-inspired music because this type of music is built for dancing bodies, social interactions in the crowd, head-nodding, beer drinking, etc… Algoraves are music performances but they are also so much more, because you can chat with everyone else around you and share something about the way you think about music, computing, art-making, etc…

I’m not a fan of the rave in algorave as well because the so called rave parties can be really different from country to country and people always expect something different concerning the rave aspect of algoraves.

I think you are missing the point by only discussing musicians. I live coded choreography for years before I tried working with sound. I collaborate with a visual artist who also has never live coded sound.

Live coding does not have to be music. It is about process not medium. I think this is the hill I will die on.

2 Likes