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.
BM 3.0.5 - out now!
update 2 - still problems with crashing, suggest to wait for 3.0.5. (which may or may not also fix a new AU crash bug that was also introduced on old projects)
update - seems to work fine now, and if not, put the ipad in airplane mode
Updated and now the app won’t launch ![]()
Ipad pro 2027 12.9”, tried memory rest, system hard reset etc. Anyone else?
Specifically, the app gets to the file open screen for a couple of seconds then crashes every time.
Comments
Intua just tweeted not to update. A fix is underway.
Damn! Missed that
Lifesavers thanks for the heads up.
It’s a wifi problem
This actions working for me
and now it’s working
I wonder if the 'update to AudioBus sdk 3’ means AB midi. Soon!
Anyone else having issues with the app immediately crashing when trying to switch to keyboard view when on an auv3 pad? Also when trying to show the auv3 itself. This happens with isem and model 15 in my limited testing so far
Model 15 and Zeeon crashes here when I try to show the plugin window - Poison works.
This update is screwed
Twitter says it should work without the airplane mode trick now, but tis not true... Works fine after. Another good reason to keep autoupdate off!
I had to unload the auv3’s and reload them, then the project worked fine without crashing. But it seems the main crash is back where you need to switch wifi off to get it working. Something with the music app store Intua says...
Imagine there is feverish update noodling and someone in QA is on the naughty step. Been there many times.
All hail the new security measure from Apple. Since iOS 11, Isee you guys posting about updates all the time, yet they are not available without going to the particular app in the store. In the Updates section, they don’t show straight away (this may be the U.K. or even just myself only lol)
The above can be annoying, but it’s stopped me updating before many people have done some testing!
Hmm, after more testing it seems that any previously loaded auv3 in a project will crash the app if you attempt to show the UI. Hope a fix is coming soon, because a lot of those auv3 instances weren’t using presets
What bugs me is that there are some new bugs that were not present in 3.0.3.
Like a 'new' somewhat laggy behaviour of the mini-keys in the sample editor(s) when trigger mode is set to 'hold'...
(This 'appeared' in the later beta builds). I know it will get fixed sooner or later...
Why after all these updates can’t I simply replace a sample without losing all the settings, such as tuning, filter and modulation mappings. The only way still is to load it into a new layer and then move it.
Feel sorry for the guys. It's a pretty bigly update.
OMG
sonofabiatch! I'd just hit the update button only seconds before reading not too. Dang it.
Oh well, I'm sure they're frantically trying to correct it as quickly as possible. And, it's not like I had an immediate important use for it right this very minute anyway.
These guys are like the Manic Street Preachers of app developers. Totally devoted, but...
LMAO just worked out I have already updated to this one and I’ve not had any issues as yet
Beats me. I've reported a load of issues and I don't know what criteria an issues has to meet to get 'top priority'.
(There are few things that bug me like mad, like no option to disable note-end quantise which is especially annoying when using 'hold' as a trigger mode as shortest note that can be recorded with quantise on is the currently set 'quantise value'). And well, there's a ton of other 'things' that are still missing but in due time they will come.
Their bass player also disappeared?
Or maybe someone is late on delivery
(Ie. transient detection).
Sounds like it was an Intua Sound Store problem....update loads and runs fine now...
The update works fine here...
I usually keep WiFi enabled so I don't bump into issues caused by lack of network connection...
Need to swipe downwards while on the update screen
So conflicted now... ...i await official word from.... I don't know...
No difference, as I tried that when some where available a while back.
Found out update available by comment on here.
Went to app and swiped until the update icon came up, but no new updates.
Checked app on the store and my list of apps and it showed update available.
Went back and checked on app and still no update.
The update list did change later that day.
This has happened a few times of late where I’ve only known about updates via this website and the updates have arrived on the app up to 12 hours later than they show on My app list or under the store.
Yah Model 15 did not show up as an update for me for a few hours after a bunch of people here said it was available. Seems like it was put on hold when a bunch of people did it and there were issues. Sounds like another fix will likely hit soonish.
I thought maybe it was just loading previous sessions with AUv3s... but I don't have anything I really need to save, so I just deleted my handful of sessions and started a fresh one. Still kinda messed up. I couldn't even close the app. Had to force quit by holding down power button to get the shut down slider, then holding the home button. (The forced memory clear) just to get the app to finally close. Some AUv3s worked, but weren't showing the interface.
I'm just going to wait for another update at this point. This one seems mangled... at least for me.