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
Tested Quantiloop, works perfectly. It does seem to work intermittently at times. I tried to open AUM and LP at the same time, worked once but then its not.
My iPad is a 2017 2nd Gen, iPad Pro 12.9. so it is a little older but still runs strong with most stuff. What is it when you reset your iPad without loosing all the information?
Please see my previous comment. Can you try what I suggested above. It is possible that launching AUM may be waking things up. Please try what I suggested above (tldr: launch AUM first with your pedalboard router into an auv3 midi monitor before you launch loopy pro. That way if things stop working in loopy, you can switch to AUM and see if AUM saw the midi…and it eliminates the possibility that AUM launching is having an impact)
It also will give a little audit trail in case there is something interesting that the pedalboard is sending
@espiegel123 I was messing around with doing that. Nothing was actually working in either app. I pulled up quantiloop and things were working.
I loaded up AUM and things were working. Streambyter was picking up midi. I loaded LP and nothing was responding in LP. I switch back to AUM and it had stopped working as well.
I am about ready to do a factory reset on my iPad.
Are you saying you launched AUM and Loopy at about the same time and that when Loopy stopped working, it also wasn’t working in AUM?
And that rebooting AUM fixed it?
About how long do things run before this happens?
I had AUM working, for about 1 minute, then opened LP and it wasn't working.
Further development, as I was contemplating reseting my iPad, I was looking at my Minecraft worlds to see if I could back them up. I closed out Minecraft and opened up LP, MIDI worked for about 5-10 seconds. I closed out LP, opened up minecraft closed it out and Opened up LP, same situation, worked for about 5-10 seconds. I then closed out LP, and opened it back up and nothing.
So it seems that there is some sort of cache issue or my iPad is loosing the midi connection.
Fingers cross, I did a simple reset all settings option first and so far it is working. I will slowly put it through the paces.
When you say "closed out", do you mean "force-quit" (swipe off the App Switcher screen), or just switched to another app?
How many other apps are loaded when you experience these problems? Could you try with nothing else loaded?
Also, do you have any other MIDI devices you could connect? This would help establish whether Core MIDI overall is failing, or whether it's just this specific device.
@uncledave I have plenty of midi devices and I tried several. Closed out means force-quit. I usually only run LP at church unless I have to pull up SongKit or guitar tabs.
It must have been something with CoreMIDI and LP because as soon as I reset my iPad, everything seems to be working.
Mitch does this happen even after a fresh reboot if Loopy is the only app launched and remains the front app without ever switching out?
How long does Loopy run before you start having problems?
Open AUM and route midi to MidiSpy (or other midi monitoring app)
Don't close AUM, launch LP and then switch to AUM to see if there is any midi feedback
@espiegel123 yes it happened after a fresh reboot and LP was the only app opened. Sometimes it would work for a few minutes until I started adding bindings and other times it would only work for about 5-10 seconds.
@Korakios I tried that. There was no feedback that I could see.
Its been running off and on for a couple hours now after the soft reset. I am thinking something glitched on iOS. We had several power outages over the past few days while my setup was powered on. Hopefully doing that soft reset fixed the issue and I won't have to do a full reset, although I was almost looking forward to restarting my iPad and getting rid of the clutter.
It is still mysterious that it only failed for you when Loopy Pro or Audiobus was running… and sometimes failing after only minutes which rules out some sort of timeout.
@Michael : is it possible that Loopy is sometimes sending feedback even if feedback is turned off?
I suppose it's possible, but I'd be very surprised. At the end of the day, Core MIDI has always been buggy, for all of us; Jonatan and I are still dealing with weirdness on an ongoing basis. I think if it's working now after a soft reset, I'm happy to just leave it there. I don't think it's worth my time delving deeper unless it's an ongoing issue.
@Michael No joy. I just got time to test it this morning and it stopped working again. doing the same stuff as it was before. Is there some diagnostic information or application logs I could pull from the iPad to help give you an indication as to what is going on? I am restarting my iPad to see if that helps.
@Michael So I figured out that WIFI is killing the midi. I can turn off the WIFI restart LP and it seems to work. I can then turn on wifi while LP is still on and it kills the midi. I turn off wifi, restart LP and boom it works.
Interesting. Do you use any MIDI connections to "Network Session"?
Is all midi into Loopy not working when this happens for just midi from that device?
@wim Not on my iPad. Maybe I have enabled something on my MacBook that is causing issues with midi via wifi. But my MacBook pro is hardwired. My Akai force is currently turned off. I shouldn't have any other wifi enabled deices that work with midi.
@espiegel123 all midi stops working.
Has all your troubleshooting been with the same Loopy Pro document?
Given how quickly things stop working for you, I wonder if it would be possible to try something methodical -- as what is happening to you seems quite unusual.
For the sake of troubleshooting, can you try something like this:
Figured out that it was the UCNET midi drivers that was causing the issues. I turned off my MacBook pro and everything worked as expected. When I booted my MacBook back up things started acting funny again. I slowly deleted midi devices until I figured out that UCNET was causing the issue.
Thanks everyone for the help. @Michael Not sure if there is anything that could be done via code but be aware that when I removed the UCNET midi from HD/Library/Audio/Midi Drivers deleted it from the MIDI studio and restarted my MacBook pro, everything is working as normal.I think it is part of the Universal Control from Presonus. It must have gotten installed since I have studio one 5 and a presonus Studio 24c audio interface.
How was the Mac MIDI making it to the ipad?
Was there a Network Session active?
@espiegel123 not that I could see. Where would I have gone on my iPad to check network session for midi? global? or per app? AUM must handle midi different than LP since it only seem to effect LP and Audiobus.
For something on the Mac to be affecting the iPad, the iPad must be listening to it. I wonder if a network session gets started when that driver is present and loopy listens to it but AUM doesn’t.
That's a good thought!
Hey @TheAudioDabbler - when you check the network icon in AUM's midi routing window, is Network Session ON or OFF?
It seems that Loopy connects to the Network Session automatically whereas AUM has an option to turn it on and off. I don't remember what the AUM default is.
So, quit all apps and opened Audio/MIDI Setup on the Mac. No connected devices were listed.
That leads me to conclude that Loopy Pro always initiates a Network Session on startup whereas AUM respects the ON/OFF option.
This is amazing diagnostic work, everyone, @TheAudioDabbler – thank you so much for getting to the bottom of this! I've added a "Enable Network MIDI" switch to LP's system settings, so it can be disabled. The question now is whether to disable it by default – it may avoid some bad experiences if network MIDI is this flaky.
Cool!
Yeh, I thought about that. I tend to think it should default to off. But then you're going to get people freaking out over broken setups that use it. I'm always surprised how many people try to use Network Session when they have no need to communicate to another device.
I'd say off by default.