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.
Comments
You probably already know this? But Loopy has save slots, so I’ve got buttons that let me save and restore the current values of all the other controls.
I really love Loopy in this regard. I do wish I had more control over some aspects of layout design, but overall it provides an amazing facility for this kind of thing.
I don’t really understand why you can load it into a Midi AUM track. It loads with the full feature set, as far as I can tell, but since it’s not a Midi looper (yet), a lot of it doesn’t make sense in this context. Well… I guess when it finally does become a midi looper, it will.
Yes, those are amazing. What I was thinking of though was a Loopy Pro running as a control surface on one device, controlling Loopy Pro on another. If you load a new project on the 2nd one, it's not going to dump its control positions to the controller one without some doing. But I expect you've found a comfortable way around that. There are several ways to go about it.
My comment was more for other readers of the thread so as to not have expectations that there would be automatic two way feedback between two devices.
As far as I can tell, incoming MIDI to a Surface object like a knob only sets the value of the object… not the value of its output. In short, there’s no MIDI thru. What, then, is the point? It means that the only way for a MIDI source to both move the Surface knob and control whatever the actual target is (like a VCF cutoff), you have to split the path… one branch to Surface, the other to the target.
I don’t get it.
Yes, that is a baffling omission.
@4pockets_paul can usually be reached at support @ 4pockets.com. I've found him responsive most times I've contacted him.
Hi guys. Can the control knobs in surface builder be mapped to a midi controller? As in is there midi learn? And if there is does it work smoothly in logic?
Some synths and effect units can dump their complete parameter set as MIDI CC upon receiving the respective dump request message - in that case the above would be exactly what I want.
No MIDI feedback and no value jumps when I move the knobs to edit the current preset.
Or did I misunderstand anything here?
So I've just run into this issue trying to control surface builder with Digitakt, if we're thinking about the same thing. The moment I midi learn a knob on a midi controller to surface builder, that knob stops sending CC to the synth further in the signal chain. Also midi notes don't pass through. Did you ever figure out a fix?
@DiscoBiscuitChef I think what I’ve observed is slightly different. As I recall (it’s been a little while since I did this), I twist my external controller to make SB learn. Now that it’s learned, I can twiddle in SB to control an AU (I’ve never tried to control another external piece of gear with it). But if, after the learning, I twist the external controller, it will move the knobs in SB but not transmit the control to the target AU.
@rs2000 Does that help clarify my use case? I want control to flow through and merge. Which would seem pretty straightforward. LP does it. And I’d just go ahead and use LP, but for some limitations in its UI.
I sent the developer an email about it but have never received any response, even though they’ve released new apps and updates since.
Yup. That's exactly what's happening to me, seems crazy it would behave that way as it entirely defeats the purpose of using an external midi controller
I was surprised that there was no MIDI being passed from the external MIDI controller to the Surface Builder objects, and then out (i.e MIDI through), so I tried testing all sorts of different configurations in AUM using MIDI input and MIDI learn from MIDI sources within AUM and also using an external hardware controller knob. One example - I thought maybe that it would be necessary to set a different AUM output port on the knob object in SB, so that input and output was not being caught in some sort of feedback loop, but that didn't work either. I tried loading SB as an Audio object as well as a MIDI object in AUM - they behaved the same. The way I see it, either (1) there's some sort of special configuration required to allow MIDI data to both control and pass through the SB objects or (2) it's not supported. I'm leaning toward (2) at this point.
Regarding the response from Paul, the developer, I would say please try again. I can't speak for Paul, but I have communicated with him over email on some current app related things during the last couple weeks and he told me that he would get back to me after he took care of some other priorities and he did, but it took a little while.
Indeed. I believe Paul tries hard to be responsive but gets buried from time to time.
I'm of the opinion that midi through isn't the best alternative here. I think what is really needed is simply for controls to work the same way if they're moved by a controller or moved by an on-screen gesture.
I say this because often it makes sense to re-map controller output. You might want to have a controller that's sending CC 11 move a knob that's sending CC 20 or something. It makes a lot more sense that way in my opinion.
I feel like this just has to be something overlooked by @4pockets_paul rather than a conscious design decision. Hopefully it'll be addressed at some point because it's kind of a big deal.