09-08-2021, 02:31 PM
(This post was last modified: 09-08-2021, 02:37 PM by Paranormal Patroler.)
(09-08-2021, 01:24 PM)mgd Wrote: I think the problem is about words. [...]
I honestly hope it's not the case.
Let me start by saying that I see your point, but in the context of a modular system, and in particular a sequencer, a gate is a pulse with a large duration, whereas a trigger is a short pulse. Context and use case is important when setting definitions and UX copy (which is what we're discussing about essentially). In that sense, if 'Auto Fill-In Trigger' automatically adds short pulses when a Note is added, whereas 'Auto Gate on Note' automatically adds gates when a Note is added until the next Note is reached (with the Gate Off setting being independent) then the stages vs events dichotomy isn't really applicable or at least as important, your standard use-case is very similar (as both are mainly aimed as solutions to the necessity of having something being output from the Gate of the track to hear a note), and from a UX-copy perspective these two can be easily "grouped" together by having very similar copy. This was my suggestion earlier with the reasoning that it is less mental clutter for the user (it's easy to distinguish between Gate and Trigger, and you get that generally what these two do is add pulses automatically).
It is suggested that the function is different though. If the differentiation is between Gate and Trigger, then that is already apparent by using that particular term in the title of the function (Auto Fill-In Gate vs Auto Fill-In Trigger, or maybe we should go for Auto Gate on Note and Auto Trigger on Note ?).
My assumption is that we're missing some major difference in the functionality, but I need to check to make sure as the doc doesn't indicate something additional to what we're discussing.