Option to only execute stepped dial actions when dial is triggered, not when selecting step
under review
S
Sawyer Lawson
When adding an action to a step on the dial, you currently have three choices for what will initiate that action: “Select”, “Deselect”, and “Select/Deselect”. There should be a fourth option: “Only when triggered”.
This way, each step of the dial can act as a “state” that arms the dial to perform certain actions but, importantly, doesn’t automatically execute those actions simply by selecting that step. Once the dial is set to the desire state, the associated action(s) can be triggered by a widget or a MIDI binding.
AJ Kerezy
there are, I believe, several requests like this.....to allow what I call "scroll through" - that is functionality to scroll through or nudge through steps in a step dial WITHOUT executing any of the actions (select, deselect, etc.) - UNTIL you get to the specific step you want, and THEN you indicate to LP (the software), now I am on the step I actually want to execute - so execute the action on this step
Some user described this functionality as similar to a drop down menu on a web site, you scroll through the list of items in the drop down menu, and nothing happens UNTIL - you select (stop scrolling) an item from the list, and now as you actually select an item in the drop down list then (and only then) something executes
this is SORELY needed...... PLEASE.... if you're a guitar player we need this for presets at the entire project level. As stated in the request - we need the functionality to scroll through or move through the steps in a step dial and NOTHING executes.... UNTIL..... we tell LP we've reached the specific step we need
S
Sawyer Lawson
AJ Kerezy agreed, it would be very useful to only have the action(s) of the step that you end up on execute.
With my idea, that would be possible, but also you’d be able to scroll without any actions executing, not even those of the step where you end up. (Until the widget gets triggered later)
Use case example:
A step dial could be used to determine what will happen when clips finish recording. The clips could have a follow action to trigger the step dial widget (the actions of whatever step it’s set to) when a clip finishes recording. The steps could be:
Play
Overdub
Stop
Record next clip
So you can set the dial to whichever mode you want without anything happening but once you record a clip, the dial determines what happens next.
AJ Kerezy
Sawyer Lawson In your example here, you would have to turn or 'preset' the step dial to the intended action you want executed once the clip finished playing, correct? The clip would not somehow inherently know what your intended action is once it finishes, correct?
S
Sawyer Lawson
AJ Kerezy correct, the step dial would essentially just tell loopy what to do when clips finish recording, but it would only do so if the clips have a follow actions to trigger the dial after they finish recording. Whatever the dial is set to when it gets triggered determines what happens next.
AJ Kerezy
Sawyer Lawson YES, we need this. There are some other similar feature requests on this that have been out there for over a year. Still Waiting......
S
Sawyer Lawson
AJ Kerezy sounds like it’s coming soon 🙂 Hopefully this means selecting a step without yet activating will be possible in 2.0, not just turning the dial past steps without activating
ultracello
under review
Anthony Westbrook
It can even default to release to trigger itself, but this doesn't happen if it's turned.
S
Sawyer Lawson
Anthony Westbrook Are you talking about being able to manually scroll the dial without triggering any actions until you take your finger off it, and then it only triggers the step you ended on? This seems like one of many very useful workflows that would be enabled with this option. And it would be really easy- you could just set all the actions to “only when triggered”, and then set a release action on the dial to “trigger current value”.
Currently, simply scrolling the dial manually to get to the setting you want isn’t viable without triggering a bunch of other actions on the way there. So instead we have to create all sorts of actions that scroll multiple steps at a time or jump to a specific step; it’s unnecessarily cumbersome.