As for static vs dynamic, it's a mix of both. Some tracks are more static than others, and I have learned it actually seems better to try and use randomness sparingly. Almost all tracks will use probabilities of loops firing, and some watch for the status of other loops to create sections (e.g, always fire A if not firing B). Note / Chord selection also often contains randomness, such as a probability to pick each note from a list, then a probability that note itself to fire.
Hope that makes sense!
(Are "tracks" simple MIDI files or some combination of JSON/JS?)
Anyway, nice work! ;-)
I have a synesthesia-themed project (https://testfixture.presteign.com) where I currently make all the audio with generative synthesis in a DAW and the visuals by hand in a design package, but I'd love to branch out into fully-procedural at some point.
I make algorithmic (infinite) music in a DAW (Reaper) and have been thinking about porting some of it to the browser, but didn't actually do anything about it :-(
Can you describe the architecture a little? Are you using the Web Audio API for the instruments (and timing)? Are tracks static/looping, or dynamic (created on the fly based on random parameters)?