tdat performance considerations
this week i have four final project presentations in a row, and “the data and tension” will comprise no less than three of them. mostly, this decision was arrived at for practical reasons: i want my performers to have a few chances to practice before the actual presentation on may 8th. it will also be nice to have the experience of trying to explain it a few times before the big date as well.
i have decided that in addition to my preamble where i problematize transiency and opacity in creative work with technology, just after i play the binaural recordings from the installation, i should engage two audience members in a demonstration of the tdat system. this way, in explaining the rules we can see them applied to a smaller system first, and the audience has the opportunity to experience the dilemma i’m trying to communicate.
this new ruleset is currently being located by a massive automated genetic search algorithm i wrote in supercollider. i’m searching for this new ruleset with a lot of improvements to the code that both automate the entire workflow and properly log each step of the process for future sonification / visualization work.
i am still uncertain if a duet version is viable, because it’s currently on its 140th generation of 32 and we’re still not getting reasonable results. i may can the duet idea and go for a trio instead, but i’m going to let this run for a few more hours and we’ll see if i eat my words. i hope i do, words are tasty.
April 20th, 2009 at 12:14
I’m at the 1268th generation and I’m giving up. There was a marked improvement but this algorithm is too slow. I could always pick it back up later, but for now I’m going to go for a three-person system.
April 22nd, 2009 at 07:23
I should really come up with a way to simulate tests outside of time… This scheduled-thread thing is only cute for so long.