Channel number randomization/LFO for Note On/Off types of messages is a simple specific example
Sorry, I don’t get this.
partial guess
Channel number randomization for Note On/Off.
I have a vague memory of Giedrius responding to a request for enhancements to Dispatcher.
This is where this would fit IMO.
We’ll have to wait/see whether he’s tackled this in eagerly awaited 1.14
LFO
don’t get this bit.
like a cycle through note channel remap according to what value an LFO has just produced?
If so like below but easier.
LFO trigger that runs a cycle only IF two other LFO’s on other CC parameters hit >100 value.
That’s interesting to think about how to achieve with current firmware†…
…but I take your point about wanting it to be easier to achieve via a logical AND pipe.
Have you given any thinking as to how such a pipe would look – in terms of what it’s property panel would look like?
Off the top of my head I’m picturing
- an “Input1” set of properties, a similar “Input2” set
- then an “Output” set of properties (same).
- Obviously a
Operation
property (AND|OR|XOR etc) would make the pipe more flexible
I ask cos I’ve not seen G pick up much on this sort of idea but, as a fellow enthusiast, it’s the kind of abstraction I’d like to ‘sell’ him on!
Maybe you can provide an [obvious] solution
† If you really wanna do this now, my hunch would be :
- Transform (using
Value.. Low|High
) to create a “LFO1 > 100” condition - Rescale it via the 2nd LFO (emulates a multiply operation)
- similar Transform to create a “both LFOs > 100” outcome
- use result mapped to Trigger of One-Shot LFO3
This currently needs physical-loopback but I’m pretty confident G is going to make this easier
(you’ve seen that post )