Fantastic work, @JamO — thanks a lot for all the hard work on this.
Would it be possible (@JamO or anyone on the forum) to explain the changes in the new legato module, specifically things like the value “extend notes UP to 13 ms” compared to what we used to set manually (e.g. ~8 ms)?
Previously, I found the 8ms values to work really well in combination with bends (e.g. 12st) when using certain string VSTi like fretless basses. That setting gave me more control over hammer-ons vs legato/slides. With the new legato module, I’m still experimenting but not fully confident yet about the proposed values.
Would it also be possible to include the old legato module alongside the new one in a future MG3 version, so I can compare behaviors directly without having to reinstall a different MG3 plugin version?
So, for legato runs we (usually) want to extend note durations a bit, so that they don’t turn off until the next note is played. Previously you could set it down to 1ms resolution but I got the feeling that 13ms was a sweet spot, which we should set as default and remove most other options as steps of 1ms is not really noticeable. But let me add 8ms as well in next update (later today or tomorrow). It should still load your 8ms patches.
All I know is that 7ms vs 8ms makes a difference in my case. I can’t explain why it is, but at 8ms, I’m optimal. As you make the value past 8ms, it increasingly make my legato/slides not sounding as natural. This might be dependent on the VSTi used, but I use a good bunch and they all seem to be happy with 8ms. I found it tricky to achieve the right balance between legato, bend value and get proper VSTi response for hammer on and slides. But the end results are quite convincing. Thanks for your software that makes it possible.
