ChromoRhythm: Mediocre Results
Though I haven't fully fleshed out the ChromoRhythm data structure, I'm already getting the unfortunate feeling that the drum module simply isn't going to be able to stand up to GGrewve. It's too unstructured to bring any coherence to a drum channel without extensive use of a complicated fitness function and a large population of randomly mutated DNA strands, which results in unnecessarily high run times.
In short, Chromo's genetic algorithm engine isn't looking like a good choice for drum beats. The engine, even in early stages, consumes too much time and produces mediocre results.
I'm not yet ready to give up on finding a superior alternative to GGrewve. I may abandon this particular genetic algorithm approach for the moment and focus on a flexible stochastic system implemented on top of a grammar foundation.
As I like to remind myself, one of the greatest benefits of my style of research lies in my ability to immediately turn around when I sense a dead end. Without a concrete aim or hypothesis, other than the overall goal of creating an infinite music system, I am completely free to try whatever methods I choose, creating and abandoning modules as necessary for maximum productivity. Killing a module within two days of creating it isn't a bad thing. It means more experience, more knowledge of what doesn't work, and more opportunity to find out what does work.