I found this reading particularly interesting because of the mathematical part of it (information theory) but at the same time a little difficult to follow because of the music technicality. What I really found eye-opening was the difference between random corruption versus random generation. For my second assignment, I was initially struggling a lot to create something that sounded nice or meaningful because I do not have any musical background and I do not know which notes to hit, what sounds to use together, etc. Because of this lack of music technicality, I was just trying to generate random patterns I could think of that sounded monotonous after a point. As the author writes, even my music was, “Informative, unpredictable, not conforming to something heard before, but it [fell] short of being a musical composition.”

This reading made me realize how we could create a better, more meaningful musical composition that conveys emotions of anticipation, prediction, surprise, disappointment, reassurance, or return through the usage of noise (random corruption of carefully selected notes/sounds). I now understand what Prof. Aaron meant when he said, “Put in some question marks here and there, use random range, degradeBy, sometimesBy, etc.” I earlier wondered how this could lead to music that would be more pleasurable to hear because it will be so off-pattern, out of sync, uncertain, and not have a clear rhythm but I now understand why this is important and a better move than random generation. This reading has enlightened me to a different approach to composing music. From really struggling to create live computational music, I believe I now have a direction I want to explore – replace defined information with random data at random times, degrading otherwise fully intelligible signals.

I do not know if this will make me a better composer or the next assignment a bit easier but the idea of using information theory in computational music is quite fascinating and I think I will definitely look more into it later 🙂

After this reading, I am a little confused about what Live Coding is. It is definitely coding live in front of the audience – but my question is more about the approach regarding that. Do you practice your code thoroughly, memorize what each step is, remember what to do next, account for possible mishaps – just like one prepares for music, dance, or theatre performance? Practice and practice until you you can’t get it wrong? Or you practice different code combinations, try out your hands at different things, but then live code all of that improv? No set sequence, no idea of what you’ll do next but improvise based on the audience’s reactions.

 

The latter is more risk-taking and the former is risk-aversing. In the former approach, you practice and perfect everything and leave minimal things for chance. In this, the live-coding idea is a performance in front of an audience where you code ‘live’ (in real-time) and show them whatever you are coding. However, it is a rehearsed performance. In the second approach, you think about ideas there and then, make a sequence at the moment, you are unsure of the output and also have to think about how to reverse it if it doesn’t look as good. It is like a theatre improv performance. 

 

The former approach was my interpretation of live coding and mostly what I presented for my first assignment. But, this reading makes me wonder otherwise. In multiple instances, I get a feeling that artists love to engage in live coding because they see spontaneity as a result of improvisation as a challenge. One of the subjects said that “[Live coding] allows for improvisation and spontaneity and discourages over-thinking.” And another one said, “The higher pace of live coding leads to more impulsive choices which keep things more interesting to create.” So is live coding supposed to be a spontaneous challenge, an improv? Can it not be a rehearsed performance? Does that take away from the creativity of the artist performing live?

 

In the article, the author uses this spontaneity and impulsiveness in live coding as a reason to justify how it allows creative minds to express their music. The author says, “Such riskier ways of making music are more likely to produce aberrant output, providing the opportunity to adjust your style through transformational creativity.” But my question is, is improvising live the only way to define creativity? Creativity is a broader topic. Sampling sequences of audio/music or video in a way to a tell story is also creativity. This creative piece can then be rehearsed and perfected to perform live in front of the audience. That does not make it less creative. 

 

I then believe that both approaches are correct, or say, neither of them are incorrect. It depends on where you are at and how comfortable you are with live coding. If you are just starting out, you may want to rehearse everything beforehand, and that is absolutely alright. If you are experienced, you may want to improvise live and that challenge could be your performance. Whatever your approach may be, one should not be defined as more creative than the other or justified in that way.