I think you really picked up what I was trying to do with the score, glad it came through.
I had some feedback from a art curator about a previous piece of work that I was going to show (this one in fact https://www.vitling.xyz/welcome-to-tech-talk/ ), and she didn't really understand what was going on. After explaining what was happening and how it all works she told me "I love it now; but you're hiding all the interesting parts from the audience".
One of the interesting parts about generative art is that the "work" I do is really the ruleset/algorithm, rather than the audio or visuals that come out of it, so I always want to find a way to show what's happening 'inside the box' so to speak. Source code can be nice, but only for those who can read it, and the core idea often gets lost in boilerplate and technical weirdness. That's where I got to the idea of writing a score for it instead, which just lays out the basic premise of what's going on - enough to understand that what's being played is generative but not so much as to get lost in the detail.
Thanks - it’s really just a magical choice of word you made. You could have posted the same explanation under the heading of ‘How it Works’ and it wouldn’t have had any of the same connotation for me. Calling it a ‘Score’ made something click.
I love how you've done this. It really is a musical score. Reminds me of Terry Riley's similarly "algorithmic" approach to describing how a piece of music is played.
Comments
I think you really picked up what I was trying to do with the score, glad it came through.
I had some feedback from a art curator about a previous piece of work that I was going to show (this one in fact https://www.vitling.xyz/welcome-to-tech-talk/ ), and she didn't really understand what was going on. After explaining what was happening and how it all works she told me "I love it now; but you're hiding all the interesting parts from the audience".
One of the interesting parts about generative art is that the "work" I do is really the ruleset/algorithm, rather than the audio or visuals that come out of it, so I always want to find a way to show what's happening 'inside the box' so to speak. Source code can be nice, but only for those who can read it, and the core idea often gets lost in boilerplate and technical weirdness. That's where I got to the idea of writing a score for it instead, which just lays out the basic premise of what's going on - enough to understand that what's being played is generative but not so much as to get lost in the detail.
Thanks - it’s really just a magical choice of word you made. You could have posted the same explanation under the heading of ‘How it Works’ and it wouldn’t have had any of the same connotation for me. Calling it a ‘Score’ made something click.
I love how you've done this. It really is a musical score. Reminds me of Terry Riley's similarly "algorithmic" approach to describing how a piece of music is played.