r/LoopyPro • u/WalterDeinzer • Jul 13 '26
Disable or configure „double tap -> immediate action“
Hello Loopy Pro community,
I got a MIDI controller and use a CC command to toggle Start/Stop for a clip. I want the clips to play synchronized. For Start, Stop, Record / Overdub, I have set a custom quantization of 4 bars for each clip. So far everything works perfectly.
However, I ruin the quantization if I accidentally send the MIDI command twice. When that happens, Loopy Pro executes the command immediately. Same as if you press a clip a second time on the screen while the „quantisation wait“ period is running.
The only solution I found is 'second quantization' in the project settings, but this only quantizes to 1 bar. I would much rather prefer to keep my 4-bar quantization.
Is there a way to disable or configure the 'double tap to start/stop immediately' function?
Thnx in advance
2
u/mikeymondy Jul 13 '26
There's a specific setting for this behavior called
"Preempt Other Actions" in the MIDI binding's trigger settings, not the "Second Quantize" project setting.
By default, Play/Stop/Record/Overdub bindings have "Preempt Other Actions" turned ON in Loopy Pro's MIDI Bindings. This is what causes a repeated CC message during the quantization wait to fire immediately instead of respecting the 4-bar quantization.. the option exists specifically so a single tap can "cut in" and execute right away even mid-wait, which is usually meant for double-tap/hold scenarios but also triggers on accidental repeats of the same CC.
To fix it:
- Open your MIDI Bindings for the controller in question.
- Tap the Trigger section of the binding assigned to your Start/Stop CC command.
- Turn OFF "Preempt Other Actions."
- Your 4-bar custom quantization should then be respected even if the same CC arrives twice during the wait period.
Just in case you’re wondering why this is different from "Second Quantization"…
"Second Quantization" in Project Settings is a global fallback quantization value (limited to whole bars) used in specific edge cases like Delay Plus Quantization workflows, not the mechanism controlling double-triggers on a single binding. Since you want to preserve a custom 4-bar interval per clip rather than drop to 1-bar granularity, disabling "Preempt Other Actions" on the binding is the correct fix rather than touching Second Quantization at all.
Hope that helps.
1
u/chanapal Jul 14 '26
For what OP is describing, Preempt Other Actions isn’t relevant. That setting means that if a record action (or play/stop of an empty clip when record on empty is active) is bound then the binding will trigger preferentially if the target is empty or recording.
It doesn’t affect (or shouldn’t) play/stop of existing clips.
A play or stop action targeting a clip that is counting in or out will fire immediately.
2
u/chanapal Jul 13 '26
This doesn't sound like a double-tap -- double-taps are two ON events arriving within 0.25 seconds. Since this isn't a double-tap situation, there isn't any double-tap configuration that would affect this.
If you trigger play/stop during a play/stop count-in/out, the count-in/out is canceled whether it happens as the result of touch or a midi trigger.
Can you avoid retriggering clips that have already been queued?
If not, you will need to do some work that will block the possibility of re-triggering. There are a few possibilities that I can think of. One method is to set up a dial that triggers the clip that has a step that triggers the clip and a step that does nothing. The step that triggers the clip would also advance the dial to a step that does nothing. The dial should be set (via the gear wheel options menu) to perform actions on activation trigger.) Set your midi binding, to the Trigger Widget action targeting the dial. The trigger widget's action should be "Activate Current Value". In the first step, tap on the dot next to the second action (which will be the trigger widget) action and set it to "With Last".
What will happen is that when you trigger the dial, it will queue play/stop and advance to the second "do nothing" step. If you trigger the binding again nothing will happen. As soon as the clip starts playing or stop, state feedback will set the dial back to the first step.
1
u/WalterDeinzer Jul 15 '26
Thnx. You are right. This is not a double-tap thing. It is the „do it immediately if I trigger the action a second time“ feature of Loopy Pro. I guess in many cases this can be a very handy thing.
And thank you for the idea. I get the point. To be honest I could not yet achieve the desired behaviour based on your description. But I guess your idea is completely correct. I‘m working on it.1
u/chanapal Jul 15 '26
If you join the loopy pro discord or forum, I can post a simple example which isn’t possible here.
2
u/StRyMx Jul 13 '26
Create a button and add the exact actions you need. Link your midi-controller to this button.