Apologies in advance if this has already been well covered .
I did review the documentation, and search forums but can’t seem to come up with definitive answers.
My preconceived notion of how the transpose track would work in general, is that when a step were input, from that step on, any note steps for transpose enabled tracks would be transposed (Or maybe if applicable, have corresponding pitch data sent to the connected synth?)
What I am seeing instead, is that a step input on the transpose track will cause transpose enabled tracks to send a new MIDI note on/off message at that position (or as dictated by the pTRSP Sync setting)
Therefore in the case of a transpose step enabled in the middle of a sustained note of any transpose enabled track, a new note is retriggered.
This is great for creating some fun, unanticipated results, but not so great if the intention is to leave long sustained notes to do their thing.
Is the only solution here plan transpose steps more deliberately around all tracks content, or is there a setting I am missing that would simply allow for any notes triggered from the transpose step onwards to then become transposed, but leave any sustained notes from being retriggered?
Another slight niggle, is one would think that tracks would be returned to their original pitch when the transpose track had no steps enabled. It seems, either muting the transpose track or resetting the track is the only way back to the default pitch?
Thanks for the tip! However, note chasing does not seem to make a difference in this case?
What I have realized, is that steps on the transpose track are only retriggering where I have a sustained note trigger on a sequence track. If I have a short trigger, and sustain the sound via the connected synth release parameters, then there is no retriggering.
I am still very open to the fact that I might be missing something still…
However, if I am not, perhaps this might be worthy of a feature request? Possibly a secondary setting for the transpose track that determines if transpose is applied (triggered) immediately to sustained note steps. Or not, and instead waits for the next note on event, per track?
Another little quirk with the transpose track that I think might make sense to address, is that the steps input on transpose track are also sent out as MIDI (which has some usefulness), and there is no “off” setting in the output, and the output defaults to MIDI output A…
In my case I have been setting the output to a gate or CV out, which I am not otherwise using, to prevent unwanted triggering on MIDI outputs (or setting velocity to 0) but perhaps it would be sensible (and save potential confusion) to have the transpose track default to having no physical output routing?
the transpose only works on notes that happen at the same time as the transpose event, all following note-on after the transpose event, and notes currently sustaining (ie: there hasn’t been a note-off event yet). I think anything else is outside the scope of transpose. If you need a sound that has already received a note-off even to change, you’re going to need to do that manually since technically there’s no related midi note event to be transposed