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
Get this in AUM> @uncledave said:
Get this in AUM on 14.2 after reloading a session. Also, get it in other hosts, AB3, etc. Sometimes I’ll walk away for half hour, come back and “there aren’t AU extensions installed.” A restart fixes it, but this isn’t ideal at all.
Yep same here in NanoStudio2 and Cubasis3.
I really believe that this is a problem with the OS rather than the individual apps.
There are a lot of variables in this equation, but generally...
Audio production being a real time process is always a balancing act. And since progress never stops, finding this balance is getting more difficult every year... battery life vs cpu limiting, latency vs stability etc.
I think the current state (AU list, preset handling) is just a little teaser. When they will start making real tweaks I expect more severe problems... and those tweaks will have to come to bring iPad closer to desktop.
@god have you mentioned anything to Apple? I was on the phone for an hour the other day talking to through four levels of mostly worthless tech support. Basically, they said we’d have to get someone like @Michael or Jonatan of AUM, etc to submit if they can see what’s going on in their hosts. Someone close to me is on the iOS team and is going to look for an internal radar about it.
Exactly why I don’t report. Not worth the hassle. This is a very specific problem and needs the attention of someone who actually understands this area .
That’s right. I’ll ping you if I hear anything anytime soon.
My guess is that this is happening this time because of the delayed releases of the various hardware platforms and the upcoming Arm based machines.
For the presets issue, Apple made a change to a couple of methods that both hosts and AU's use to get and save state. I'm guessing that these changes have something to do with expanding support for using Swift in the AU's.
These are massive systems with tons of code. Things go wrong. I can envision how this problem didn't get caught in Apple's internal testing. The problem is that it was reported during developer beta testing early enough that it should have been fixed before release.
There are several answers to that. Any one, or combination of them, can cause issues.
Those are just a few off the top of my head.
I guess it’s over my head since I don’t really know anything about programming. I’ve made websites in the early 2000’s and that’s about my extent of coding.
It just seems like adding a new feature to a operating system shouldn’t effect every single thing in all the apps. But I guess it’s all the little intricacies I don’t understand.
Thanks! I understand a little better now. Seems like there should be a basic language or foundation, if you will, to build upon without messing up everything all the time. Lol I guess that would be too easy to hack or something I don’t know. Gives me a headache thinking about it really.
It would be cool to have a way to sandbox or really backup iOS, that way if something gets messed up with an update, you could revert back to your backup.
IMO, that is one of the most annoying things about iOS that you cannot fully restore your iPad to a previously backed up state that crosses OS version boundaries.
Apple is shockingly careless about their iOS updates when it comes to their music related developer API's! I know they're not dumb, so it can only be that they just don't care enough. Their documentation (particularly related to AUv3 apps) is abominable.
This! I still can't get over that a "backup" doesn't mean you can revert to where you were before the "backup". This is why I cringe when people jump on the latest major update on day one. There simply has never been a major version update that hasn't broken stuff, even when things have seemed to be reasonably OK in the betas. It just takes several weeks for all the issues to come out. I do eventually upgrade, but not until things settle down several weeks or sometimes a few months later. If you could revert to the previous version, I'd update if for no other reason than to help flush out bugs.
Exactly. I think you mean "you cannot restore...". And I hate that you cannot return to a last known good OS. At most, you can go one release back, but that release may have the same bugs as the current one. I just jumped from 13.7 to 14.2, and I know I can never go back there again. Leap of faith.
Yes. It was a typo. “Cannot”
Nope, you understand perfectly, and it's perfectly reasonable to expect apps not breaking after OS updates. After all, Microsoft has managed to do that for decades with Windows, where you can totally run an application from the 90s on an operating system "update" released in 2020. No problems!
Essentially though, Apple, with macOS, has managed to combine all the disadvantages of Linux with all the disadvantages of Windows 3.11
(I know we're talking about iOS, but it's comparable).
Seems to be more marked in relation to music apps. I don't recall many non music apps breaking with OS updates. Maybe that's just because I have so many other music apps. But still, I don't ever get broken games, which arguably are many times more complex with iOS updates.
Or maybe it's just because I'm fantastically frustrated with the lack of quality documentation from Apple for developing AUv3 apps. Also, when they break their own Example Projects and don't bother to update them or even note the changes. For such a brilliant company in other respects, it's just mind-boggling.
I can only attribute it to "follow the money". Music apps are such a tiny fraction of their business (and resistant to their prized subscription sink-hole), that I think they just don't allocate enough attention in that direction.
Oh they actually broke my game (Encircled) with an iOS update because suddenly, accelerometer access required user permission, so the damn thing wouldn't spin anymore! (no error / warning popup either). Users must've been thinking "dang, that's a boring game!"
It’s crazy how they advertise as the choice for creatives, then turn around and make it difficult for creatives to use their products.
Yeah years ago when I used windows (not for music) I do remember being able to use old apps for forever with no problems.
Slightly off topic. I wonder what is so different about Android that no one can make all these music apps for it. I read something about Android having a latency problem that couldn’t be fixed, which I don’t understand why that would be a thing. But then again I know nothing of how it all works. I’ve always heard windows was a nightmare for audio use as well. I just wish someone would make a stable environment for me to make music! lol Honestly I haven’t ran into an iOS problem yet. I’m still on 13.1 or 13.2 or something and it works (Beatmaker 3 older version and lots of Auv3). My only complaint is there isn’t a good DAW that does it all. I love BM3, but I want a real DAW audio editing capabilities. From what I’ve heard Cubasis 3 has a good audio editor, but it sucks for auv3 and everything else.
iOS with no glitches is like saying releasing new cars with no recalls. Probably never happen.
I’ve used Windows often enough and had several 90s programs not work, or require several work arounds or VMs to run. So, I’m not sure about this. Also, drivers that stopped working after XP. I’ve only switched to Mac in the past couple years, so don’t have experience with old software. Though I was running an application from 2000 some old game and it worked all through Mojave, but 32 bit it stopped on Catalina. This is only one example.
It’s in the terms and conditions you agreed to that it cannot be expected to work without error and that third party apps have the possibility to have issues after a system update. Though software often has these kinds of disclaimers.
iPadOS 14.2 has fixed all the AU issues I was having using BM3
That’s good to hear! I guess I’m gonna update soon. I still have to update BM3 as well. Glad to know it’s all running smooth.
iPadOS/iOS 14.2 has introduced a major problem for Ruismaker Noir. It now won't reload projects with more than one instance of the plugin.
I would love to look into the problem, but until Apple update XCode to support 14.2 I can't even run my debugger on the updated iPad.
I have confirmed that the problem does not occur on iOS14.1 and below
So far it seems this is the only app that is affected, but I haven't done extensive tests yet
well this sucks. Sorry Brambos. Hopefully will be able to fix soon.
Would not be surprised at all if Apple makes macOS Big Sur a mandatory requirement for the updated developer tools...
...I mean they want all iOS/iPadOS available for the ARM Mac's from day 1 unless developers have the time possibility to opt-out in time before the release and people mass downloading the apps to their Mac's when the ARM stuff ships before developers block it for their apps
The release candidate is out and works on Catalina. That would indicate that the final release will also. It may actually be released today.
I’m starting to really dread the disappearing AUv3 plugins bug 😤
I’m being forced to reset my iPhone twice a day to get the plugins to appear again.
Are you on 14.2?
Indeed I am