in my limited knowled it seems much more logical to have the midi-note translating module at the start of the signal chain - most signal paths in synths goes midi-in -> midi interpreter that converts the midi data into values synth can use (ie a notepitch controlle) -> oscs -> amp -> filters right?
Also - while we can use the step modulator to make semi-tb303 stuff, we can only really use it to modulate the volume/pitch etc, not actually to trigger the attack phase of notes - it doesnt act like a midi sequencer - its more like a highly editable LFO....it would be nice to have a module like the step module, but that didnt just output a CV, rather actual note-on/off data+pitch or something...
A Trigger module propably wont make it into the upcomming version 0.95, but definetly next version, incl. simple arpeggiator features.
About the notepitch, a general setup is:
ie. last in signal chain but before effects.
I've made a big effort to explain this in the manual, since it
kind of hides the keyboard control signal.
So things affected by envelopes, for example, you will in most cases want before the notepitch controller (so each voice gets its own ADSR or cutoff modulation etc. and is distinguishable from the others). FX are something that you usually want equally applied to all voices, and so go after the notepitch (saving a lot of CPU too).karmafx once said wrote:The first thing you have to be aware of is that modules before the controller are polyphonic, while modules after are monophonic.
Like in Kasper's example above, the filter and amp are before the notepitch - the two most common modulations of cutoff and amplitude wouldm be per-voice.