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.
Loopy Pro Crashing inside Logic (won't load)
Hi guys, I just got the trial of loopy to use as a midi plugin in a host. But it's crashing in logic before even loading. And when attempting to reinsert Loopy after making a new logic project clicking it in the menu does absolutely nothing. I've tried other DAWs and it seems to load there but I need to use Logic for what I'm doing so other DAWs aren't an option.
I attached the an image of the popup message it shows when trying to load it.
Anyone else have this issue as well?
Comments
I haven’t heard any reports of this. Have you tried rebooting your device? (Try fully shutting the iPad down with slide to power off)
Is Loopy Pro standalone working fine?
You might see changing the sample rate or buffer makes a difference in logic.
Are you using an interface?
Does this happen loading as an effect or an instrument?
Hi. Thanks for the reply. It works just fine standalone and works in other DAWs. I'll try what you suggested and see if maybe Logic needs an update and report back. I'm loading it as a midi effect into the MIDI slot in Logic
Does it have the same problem in a regular effects or instrument slot?
Well I'll be danged. I added it as an instrument and it loaded and now it also loads as a MIDI plugin. No idea if it just resolved itself or if adding it as an instrument first solved the issue. In either case thanks for suggesting it! I'm so happy it works now
Now to test it as a midi surface and hopefully I can throw my money at the developer
So. It seems I spoke too soon. The moment I add an AuV3 instrument (or any native logic instrument for that matter) it crashes loopy (which is inserted as a midi effect) and I have to unload it
Does Logic allow midi from instruments or fx to be routed? If so, load loopy pro into one of those sorts of slots.
So it seems Logic wasn't updated and now everything works exactly as it should. Silly me.
Thanks for the help
Good to know
I've run into an issue again. The moment I try to midi learn the Loopy knob to synthmaster it forces me to unload Loopy again. The way I did it is set the knob up to send a midi cc, click midi learn in synthmaster, and then try to move the knob. The moment I move it, it crashes loopy. That's using Logic's virtual midi in. With send midi it's impossible to map the knob
Does it work from other MIDI AU? I.e. is this a Logic issue ?
Other MIDI AuV3 do work and map properly. (I tried with imaginando LK and it midi learns in logic)
So I just realized it's you I'm chatting with on the support discord. I posted a video there showing it happen
@DiscoBiscuitChef : I think I found someone that can help you out with this. Hopefully, he’ll be on I. The next day of two. As I understand it, part of his approach is loading Loopy Pro as an instrument and routing its MIDI output to other instruments rather than loading it as a MIDI Processor… though I am not 100% sure of that.
Hi. Thanks, I’ve finally got it to work so unless the person you speak of has an alternative method then no need to ask him. He only issue with how I’ve done it is that the instrument track needs to be armed to receive midi cc, which is not ideal, but I guess i can live with it, it would be better if I didn’t have to arm it so I don’t end up recording midi cc as automation whenever i press record.
I’m attaching pictures for how to do it for anyone who finds themselves struggling with this in Logic.
Also in loopy pro I made a midi track that sends to midi out to allow passthrough of midi notes.
So basically what this allows you to do is make performance macros in loopy for any synth or effect that has midi learn, I have yet to test out sending multiple cc from one loopy knob and to test if there is any significant latency (and hopefully mapping the macros to a midi controller goes without any problems).
Some cool use cases for this is making custom instruments kind of like ableton instrument racks. For example you can make a drum machine by making say a kickdrum preset in a synth and having restricted parameter ranges with the macros. Or of course have FX performance macros. Im really hoping the latency isn’t too bad, I’ll test it with a hardware sequencer when i get home
As far as using Loopy as a midi insert, I think the crashing is a bug and I really hope it can be fixed to avoid having to make complicated MIDI flow like this.
@DiscoBiscuitChef , I’m the person @espiegel123 spoke of. Seems you got it. That’s essentially how I had it working. Like I said before Logic is such pita when it comes to this, it’s what made switch to Loopy Standalone, much more logical! Though I hope to get an additional powerful iPad for Loopy standalone to just record into logic.
So many workflows…
Glad you figured it out.
Thanks, happy to hear I've done it right. Is arming the track receiving the midi basically the only way to have it actually receive midi CC? I can foresee this causing issues if i need to record something but don’t want to record to every single track I've armed. Seeing as I’m going to be using a hardware sequencer to sequence midi cc I don’t want to inadvertently record every single parameter lock on it into logic.
It seems like I have midi controlling knobs with just input monitoring on, you can customize track header to show input monitoring “I” and I have the I
On both Loopy track and korg auv3 track in my test setup. Hope that helps
Thanks! I'll give this a try