Notes go in (buzz notes, midi notes, all the same.) Other machine's patterns get triggered as a result.
download (updated Dec. 30, 2014)
http://007ee821dfb24ea1133d-f5304285da5 ... st_1.3.zip
http://007ee821dfb24ea1133d-f5304285da5 ... ce_1.3.zip
- List of assignments lets you choose which notes trigger which patterns of which machines
- Optionally make note release stop the pattern
- Optionally loop the triggered pattern
- Quick access to associated patterns and machines by double-clicking in the list
- And more... It can be thought of as a note-triggered version of Jeskola Live.
- The song must be playing
- The patterns don't start immediately. They start on the next "bar". (the bar length is just a parameter, like in Jeskola Live)
- Any target machine must have a sequence (Now I will elaborate on this point because the naming might not be obvious. Each track in the Buzz sequence view is called a sequence (internally). Patterns are played on sequences, and if you want to trigger a machine's patterns, that machine *must* have at least one sequence created in the sequence view. Patterns triggered by patternist will interrupt any patterns currently playing on the target sequence.)
Chaotic suggests using this feature for ADSR patterns (so the notes of a synth would be accompanied by a pattern) but that's not doable with the current Buzz API, ie. you cannot trigger a pattern immediately when receiving a note on the same tick. I'm not sure if it would really fit into the way Buzz works: when a note is processed, it is assumed that patterns have already been decided for the current tick... maybe.Autopattern is instrument-bound pattern, triggered with every note of its instrument.
So instead of triggering patterns immediately it uses a "bar" system, which can be used in other interesting ways. It's ideal for controlling patterns with a keyboard or other controller. One could also use the pattern editor as sequence editor, but why would one do that? One is weird.