I’ve been testing the new expression maps and the new update is awesome. So far I’m just finding one flaw in the design, specifically Length. It is in percentage but I think it should be milliseconds because the Attack Compensation is in ms.
As you can see, at 125% the note is nowhere near the next note in order to trigger the legato. If the note is sufficiently longer then it will be enough.
Extension should not be dependent on note length because note lengths will always vary. 125% on a long note may end up being way too long if the next note is really short.
So, if length was in ms, I could set it to exactly the same amount as the Attack Compensation so that every single time it will be extended by the same amount it was offset, and the end will always reach where I need it to reach.
That’s right! The length of the event must be extended by exactly the amount of the negative delay in ms. The percentage has no meaning, so it is useless in this form. Shame
Thanks all for your feedback. We’ll consider how we can provide a tool that allows for the Note Off to be unaffected (or counter-compensated) by the Attack Compensation. We’re not just going to change the unit of the existing Length modifier, because we don’t want to change playback behaviour of existing projects.
A simple toggle so that attack compensation only affects the Note On but not the Note Off would be great (I personally can’t think of a reason or situation where you’d want the Note Off to be shifted back as well, I’d personally always want the note to end right where you see and position it on the grid).
Indeed, and I think veenu understood it that way. We may have to provide this via way of a toggle though (no promises, just initial thoughts so far), because we must ensure existing projects don’t change playback behaviour. Also, there will inevitably be someone who would rather shift the Note Off as well.
)