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.
Invalidated..... Maybe it crashed
What in the world! I've been getting this message from AUM frequently today for the first time ever..... Any ideas 
Comments
I've had a few of those too.
Have you powered all the way down and then back up? Sometimes "soft-booting" doesn't do the trick.
Yes, have been getting this with Atom, k7D, limiter and a few others. If you have a simple project which replicates this please send to Jonatan
I haven't done a full reboot but I'm gonna after work! And I'll send a basic project to him
I am having the exact same issue. Reboot fixed it initially, but now I’ve noticed that if I leave AUM open for a while and use other apps, it happens again.
Yes this looks like the exact same issue that has been occuring with Atom for a few users, and it’s been ridiculously difficult to track down the actual underlying issue.
I have this problem regularly, generating no crash logs of any use ☹️
Never seen this before. What device, OS version are you experiencing it?
Air2 12.02 (latest). Happens regulrly, randomly, both in use in the foreground, and idle in the background.
Beta testing AB3, but no generated crash logs for @Michael
IPad pro 2018 10incher
No generated crash logs for Atom either when it happens.
iOS12.3 should be out soonish and we can only hope it fixes a thing or two...
Has anyone seen this happen in AB3, apeMatrix or other hosts?
I've not been able to test much recently.
I haven't been able to reproduce it either. If someone can find a way to reliably reproduce it, please tell me! (Just "playing around with a few apps for some time" won't help)
With previous version of StepBud in AUM I was able to repeatably reproduce this issue (ie. make the plug-in get 'invalidated') when used together with SquareSynth 2(ie. SquareSynth 2 got 'invalidated').
The issue turned out to be the way StepBud behaved when using transport stop...
It overloaded the plug-in with Note Off's causing it to bail but there were no crashlogs for either of the apps.
Curiously enough I was able to get the Plug-In to 'crash' in AUM and ApeMatrix but it didn't crash in AB3?!
I don't have the offending apps in this case (Factory and Velocity KB) available to test with.
But it could be 'leaking midi data'. Factory is to my knowledge not MPE capable and if Velocity KB sends rogue MPE midi to it it could cause problems. That's just a thought...
I have just had this and atom unloaded all instances, this was my first idea with atom and like a fool i didnt save and lost everything :-(
Yeah that sucks...Are you on ios 13? Just wondering whether the new AU memory allowance stops this.
Nope, ipad pro 12.9 1st 12.4.1