Discontinuity in negatively nudged steps Standalone <-> Control Mode
Posted: Tue Oct 15, 2024 12:06 pm
So there's a couple of schools of thought on this one and I appreciate the Move designers may have a different idea of how it should/needs to work than I. I'm coming from FXpansion Geist's graph lanes and how that program deals with micro shifted notes. In any case there is a discontinuity from Move in Standalone to Move in Control Live mode.
So in Standalone if you negatively nudge a step by any percentage (even -1%) it then gets represented as residing on the previous step. This is technically accurate I suppose as a 16th step encompasses everything up to the very start of the next step. However, in Control Live mode if you negatively nudge a note in Live it only gets represented as residing on the previous step on the Move when nudged past (at most coarse) a 1/64T note. That would equate to one tick at 24ppqn.
I actually prefer how it works in Control Live mode. Why? Because there are occasions where one might want to align notes early for flam type effects but to the ear and rhythmically they still actually belong to the subsequent step.
As I say there's a couple of different ways of approaching this representation and in e.g. FXpansion Geist you can microshift anywhere up to -50% and still be on the same step. I think that anywhere < one tick at 24ppqn is probably a good call because it allows for negative offsets that still don't really function as late 16ths/triplet semiquavers.
I can foresee a difficulty when selecting portions of a bar i.e. lets say you had a negatively nudged note just before halfway in the bar, if you wanted to select the first 8 steps for copying or group editing well do you you include that early nudged note? Perhaps the answer would simply be no, unless it landed over a 1/64T earlier than the halfway point.
I shan't digress into how I believe quantifying nudges (or groove) in integer percentages is not rhythmically valid, can save that for another day. Although I'm curious how Move is actually mapping those 100 values, I would've imagined it'd be done according to a number divisible by both 2 and 3 like 96 but perhaps it is strictly by 100. I intend to analyse an exported Move pattern at some point to see what it's actually doing.
So in Standalone if you negatively nudge a step by any percentage (even -1%) it then gets represented as residing on the previous step. This is technically accurate I suppose as a 16th step encompasses everything up to the very start of the next step. However, in Control Live mode if you negatively nudge a note in Live it only gets represented as residing on the previous step on the Move when nudged past (at most coarse) a 1/64T note. That would equate to one tick at 24ppqn.
I actually prefer how it works in Control Live mode. Why? Because there are occasions where one might want to align notes early for flam type effects but to the ear and rhythmically they still actually belong to the subsequent step.
As I say there's a couple of different ways of approaching this representation and in e.g. FXpansion Geist you can microshift anywhere up to -50% and still be on the same step. I think that anywhere < one tick at 24ppqn is probably a good call because it allows for negative offsets that still don't really function as late 16ths/triplet semiquavers.
I can foresee a difficulty when selecting portions of a bar i.e. lets say you had a negatively nudged note just before halfway in the bar, if you wanted to select the first 8 steps for copying or group editing well do you you include that early nudged note? Perhaps the answer would simply be no, unless it landed over a 1/64T earlier than the halfway point.
I shan't digress into how I believe quantifying nudges (or groove) in integer percentages is not rhythmically valid, can save that for another day. Although I'm curious how Move is actually mapping those 100 values, I would've imagined it'd be done according to a number divisible by both 2 and 3 like 96 but perhaps it is strictly by 100. I intend to analyse an exported Move pattern at some point to see what it's actually doing.