Code module POC #2
(Sorry if all my posts are getting spammy, I just have a bunch of projects going right now.)
This is drum pattern data taken from the patternarium, parsed and put into a code module to send triggers out. It is a little janky, but it works. I may or may not build an actual shareable patch with this, but I wanted to share some kind of out side the box usage for these modules. My build process is actually running a python script that converts the .mtpreset into a .drmodule, which I run in bulk. The idea being that if you have a whole bunch of data that needs to get into your rack, you don’t need to do it by hand. I have racks for three presets built, but the video below is only one of them:
What does everybody think, would it be fun to have access to the patternarium outside of microtonic? (Obviously, it wouldn’t be the same without the drum synth presets as well.)
oh, just in case whoever is reading this doesn’t”t know what the patternarium is, check it, it”s so bad ass:
Comments
If I do continue with this project, I think I’m not going to use the code modules.
Pretty cool. I tried something similar (a not quite random but somehow random drum pattern generator) by randomizing 8 Euclidean sequencers and giving some control over the parameters. It's on patchstorage and called beatmap navigator.
How does your patch and patternarium make sure, the results sound like useful drum patterns?
This is better: