Back to reality, back to the arranger and the clip launcher. Today it´s about clip lengths, note sub-divisions, combining note clips and the clip launcher.
Luca inquired on Instagram, "How can I alter the length of a trigger pattern without modifying the subdivisions or tempo?" Here's my solution to this issue in @bitwig , which includes an explanation of the difference between polyrhythms and polymeters.
Since when can Bitwig snap to other notes? Am i stupid? I also created a jazzy loop along the way, combining some things i showed in the recent videos.
Euclidean rhythms the easy way and with voice stacking inside of Bitwig. Simple start and getting slowly complex, with lots of options to extend the ideas.
I'm implementing crate for reading (and later on writing) #polyend#tracker projects :-) Not proactively developed until I get my serial tool in shape tho. After I have that I might write a playback engine for the projects and a command-line player. For reverse engineering reverb and delay algorithms I'm going to use Bitwig Grid and then just compare sampled output until I get it right.
The utility would be e.g. to convert Polyend project to #Bitwig or #Ableton project and stuff like that but to do proper conversion you first need to have a playback engine for comparative testing even though those tools do no need to play anything.
@polarity I just started trying to wrap my head around the Clip Launcher in #Bitwig and how I can use it in my workflow.
Do you know whether it's possible to launch Scenes by incoming MIDI Program Change (PC) messages?
I can get it to work via the Mappings Panel and tying Scenes to note values, but it seems like the "mapping listener" (or whatever it's called) doesn't react to PC. And I'd rather use PC values, as it's easier to understand and translate (i.e. PC1->Scene1, PC2->Scene2, etc.)