Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Understanding Follow Actions
My name is Steve. I am not a looper. It's been 20 years since my last looping.
With that out of the way - I just started using LP last couple of days and cannot say how impressed I am with the work that has been done on this app. I will be a loyal customer for years to come.
I actually am not a looper - I will be using LP to trigger samples onstage as I am the guitar player in my band. I will be attempting to fill in accents and blips of sorts to make up for not having a keyboard player. Incorporating a mini keyboard is on the horizon as well. All will be done in the LP environment.
My question is-
I'm trying to trigger one 1 shot sample and select the next sample at the same time so as to use one footswitch to: play > select next > play etc.
Essentially I want to be able to to access any number of samples at will according to when I step on one of the footswitches. Think of 4 organ chords playing at the same time as guitar - a bit of tap dancing to do but have done it before in a less complicated sequence.
I believe this is possible from what I read in the manual about follow actions. Just not sure exactly how to implement it.
Thx for any help, cheers.
Comments
You can bind as many actions as you want to a MIDI message. So, you can easily have the first action play the one-shot sample followed by an action to select the next clip.
You could instead use an on-play follow action on each clip to select the next clip, but that could get confusing to keep track of. You'd have one MIDI bound action to trigger the clip but then you'd need to add the follow action to select the next clip on every clip. I don't recommend doing that unless you have a definite need to.
To refine the first method a little, it's usually a good idea to start with a widget that does what you want, then bind the midi action to that widget. Makes it easier to test, and easier to change messages or controllers.
For instance, you could have a button widget with the actions described in the first paragraph. Once that's working, you could bind a MIDI message to trigger the button widget.
More directly to the subject of the thread, Follow Actions are set to happen on Loop or One-Shot conditions such as Start Play, Stop Play, Record Start, etc. They're not directly controlled by your foot switch, but are triggered by the state of the clip.
Widget Actions fire when you trigger the widget either by an on-screen gesture or a midi message bound to the widget.
Direct Midi Bindings are possible without a widget and work the same way, but it's often better to start with a widget and trigger that by a midi message.
In all cases, you can have as many Actions as you need for a single event or binding. They can be delayed, quantized, faded in, etc. as well.
While you could do this with a follow action, it might be better to use a stepped dial that you nudge forward with a MIDI binding.
For example,
Step 1: select clip 1
Step 2: play selected clip then select next clip (or select a particular clip),
etc..
Set the dial's tap action to be Trigger Widget->Nudge Value
Set double-tap to scroll the dial to step 1 as a reset
Test the dial. If it does what you want, midi learn tapping the dial.
You could use a stop follow action or play follow action to select the next clip but then you lose the flexibility of being able to trigger the oneshot without changing the selected clip
Thx for the quick response.
Would your method allow this to be done with one stomp for each trigger?
Not sure exactly how to do this specifically:
You could use a stop follow action or play follow action to select the next clip but then you lose the flexibility of being able to trigger the oneshot without changing the selected clip.
Which part aren't you sure about? How to add a follow action that selects the next clip? Or how to select a clip with an action?
I'm not getting the logical process of how to string together all the steps to pull this off.
Do you know of any resource (video etc.) that could help me navigate the different connections with this widget?
A stepped dial for this seems more complicated than necessary to me. I would think a simple button with two actions would be enough for what you originally said you want to do. I'd have a next and previous button for moving forward and backward but that wouldn't be required.
If it were me though, I'd separate out the functions of moving and playing so that I could navigate without triggering anything in case I wanted to move to a different sample. Maybe single tap to move, double-tap to play, long-tap to move and play. With quantization the timing of those taps don't have to be exact.
Once the widget(s) work the way you want then mapping midi to trigger them is easy.
Ideally I was trying to do multiple actions with one stomp. Still unclear if that is feasible
Will take a crack at it - really appreciate the help.
You can do as many actions as you want. Put all the actions in a button and when that is working MIDI Learn the button. Editing buttons is less time-consuming than MID Bindings and can be tested without being connected to MIDI.
The screenshot I posted illustrates two actions on a single stomp. As already mentioned, you can have as many actions as you need on a single target. They can be configured in advanced ways too, such as with delays in between, ramps, etc. But those aren't needed for what you've said you want to do so far.
(Actually it's two actions on a single widget, which you can then trigger with a single stomp.)
Amazing, thx
I’m trying to set up a rig for live keys where I have a bunch of auv3s in loopy and can switch which one I’m playing with a cc button on a Korg nanokontrol. I’ve gotten it to work by soloing the input for each track, so I can switch which instruments I’m playing.
But I’ve run into a problem- if I bind a cc knob to the volume of multiple auv3s, they will all change volume at the same time. I really only want to change volume (or a host of other parameters) when that instrument input is soloed. And I don’t want to dedicate a knob for each instruments volume, as I’m not playing more than 1 at a time. Plus I’d want to use knobs and sliders to control different parameters depending on which instrument is soloed- like drawbars and fx on the organ, or synth filter and envelopes.
Any suggestions for doing this correctly?
Set up multiple project profiles, one for each AU you want to control and switch profiles when you solo an input.