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.
Audiokit plug update breaks existing projects in Logic Pro
I’ve emailed @ @AnalogMatthew that the new updates to VHS synth etc break any existing projects for me in Logic Pro.
What happens is that the project loads but the plugs are not detected by logic anymore. You can however start a brand new project and logic will see the plugin and open fine. This is just affecting existing projects.
Tested on m1 and m4 iPad before and after plugin update on 18.1 iOS.
Comments
It sounds like he may have changed the AUv3 AudioComponentDescription identifier. That string is used by hosts the reload AUv3 plug-ins. If the app updates its identifier, it appears as a new app, and the old app is gone. He needs to do like KQ Dixie; retain the old identifier as deprecated, and add the new one for new instances.
Even after the new logic update 2.1 I don’t see the updated audiokit apps. LP says not identified and even started a new track and don’t see them. They are very responsive as standalone and that’s awesome!
Matt's current forum handle is @AnalogMatthew. That other handle is not him.
Thanks @wim corrected to @AnalogMatthew
Yup. Screwed up a ton of my old projects in Cubasis 3 as well. Fuck.
Contact the developer and hopefully, he will be able to address the problem.
I’ve had this problem with several AudioKit apps for over a year.
Matt got back to me and said VHS and others have been handed over to spacemushrooms.it to service going forward and that we’d need to message them.
I’ve sent an email but also encourage others to message also if you have a ton of projects like myself using these apps that are now broken. Just a shame they changed something without any warning.
Here's my response to what is happening:
https://forum.loopypro.com/discussion/63134/a-new-chapter-for-our-older-retired-audiokit-apps/
While I'd encourage everyone to read this first:
https://forum.loopypro.com/discussion/63134/a-new-chapter-for-our-older-retired-audiokit-apps/
If you're in a hurry, this will probably help:
USING THE AUv3s IN YOUR DAW:
You’ll now find Digital D1, FM Player 2, Digitalism 2000, Bass 808, Retro Piano, and VHS Synth listed under “Space Mushrooms” instead of AudioKit in your DAW.
Here’s how to get them working:
PS, please be nice to the new stewards of the apps. Thank you. Without them, I fear many of those apps would have been retired from the app store. I will be helping them with the transition.
Thanks for the clarification @AnalogMatthew but the issue being that if you have multiple projects including any of these plugs you need to have remembered what patch or unique settings you’ve dialled in otherwise that sound is now lost.
I just think it would of been fair for the new developer to at least give us a warning this would happen so we could record these settings before updating or at least freeze / print the track with the affected auv3.
Has there been any updates direct from spacemushrooms on the issue as I’ve contacted them with no response.
Cheers,
so much empty rhetoric behind such a poor customer service…
You’re totally right—this whole situation is a mess, and I get why you’re frustrated. The thing is, AUv3 music apps getting acquired is still kind of new territory for everyone, but yeah, with the way things are going in the industry, I think we’ll probably see more of this happening.
The problem here is that the manufacturer code in the plugin changed, and that’s why a lot of DAWs aren’t recognizing it anymore. The only fix I know of right now is to remove the plugins and re-add them, which I know is a huge pain—especially if you’ve got big projects relying on them. I’m really sorry this is causing issues for you.
I wasn’t allowed to talk about the acquisition publicly before it happened, and the whole thing happened so fast. There are only a few hundred people still using these apps, so it was tricky to handle. That said, the bright side is that without the new developer stepping in, these plugins might not have been around at all.
Again, I’m sorry for the hassle—it sucks, and I wish it could’ve been handled better.
Matt is trying to keep the app alive. Yes, it sucks right now but there’s a solution in progress.
Whenever Apple launches an update, devs have to scramble to make it work. And now, when a dev has to change their plans, it adds another layer of complexity.
It will be resolved. But it takes time.
Sure
From here it looks like he’s trying to save face. The only progress I see here is that up until now when he was announcing his new apps, he had to answer questions why are his apps not working properly and drop some empty rhetoric (literally every time) about upcoming updates that never fixed existing issues. From now he can just ignore these comments and refer his ex-customers to someone else.
Apple has nothing to do with this issue, so you’re simply wrong there.
Changing ID will break existing projects and there is no fix for that (nor it is a surprise), and you will have to replace plugins manually.
But yeah… let’s not call out dodgy devs in the spirit of Christmas or something
Save face? You’d rather your apps disappeared completely?
Probably would have never noticed if they did.
I would rather they worked, or get fixed when issues reported.
The apps going to a new developer ensures they continue and they get the maintenance they need.
I guess considering that these apps have failed repeatedly to load in a saved projects, the current state could be seen as a worthy continuation. Other than that I don’t have high hopes of a new team fixing old issues for free.
I know it's too late now, but just another reminder that these kinds of issues can be avoided if people can use iMazing regularly to back up apps to a Mac or PC. The free version is enough to do this. If an app is backed up before an update is released, one can restore any backed up previous version that can still run on that device.
Sure, but these apps WILL be updated now. That's the good part of the story.
Been a few years since I developed an AUv3 host, but can't the display name (and manufacturer) of a plug-in be different from its identifier? Then the new developer could've simply left the identifier as is, finished!
Aw man this has broken all of my older sessions inside of BM3. I cannot remember the presets I used for some of these songs
I’ve been dealing with a similar issue bringing old iPadOS GarageBand files over to macOS Logic Pro for the last year and a half and many iPad plugins have no desktop equivalent. LOL. It’s annoying.
I get why you’re upset, I totally understand. And honestly, I wouldn’t blame you if you decided not to buy another AudioKit app again. (To be real, I don’t think there will be any more “big” apps from AudioKit moving forward aside from free and open-source projects, but hey, who knows?)
For those who know me, you already know I’m not here to win a popularity contest. But here are a few facts:
For folks following things, I could’ve stepped away from AudioKit last year. But instead, I stayed on and put in the work to build King of FM, King of Digital, and King of Bass—free or low-cost upgrades that replaced the older apps most people were still using. I could’ve started fresh and done something totally different, but I stuck around because I care about keeping these tools alive for you guys.
If you think I’m a bad developer, that’s fair – feel free to tell the world and skip future apps. And if you feel like you didn’t get your money’s worth, I’ll happily PayPal you the $6 you spent years ago for three or four of those apps. Seriously, no hard feelings.
At the end of the day, mobile music-making is supposed to be fun. That’s the whole point of this, right? Thanks for hearing me out.
Now, I have to go teach some kids. Can’t wait to come back and read all about how much I suck. Hopefully, the kids are kinder than the internet today. ✌️
@AnalogMatthew I wouldn’t worry about a small number of very vocal critics. You’ve already gone above and beyond to make sure these apps will survive beyond AudioKit. Some people will always complain and never be satisfied.
They're probably more mature than some of us here. Hang in there bud! Most of us love and respect the heck outta you!
It's not a matter of whining; it's a matter of the usual problem: sometimes when developers update apps, they fail to take into account the actual consistent naming of them, so any project in Cubasis etc., that uses them, loses the preset specification. Which then screws up the entire project. This matters to those of us who are actually releasing material commercially, deadlines etc. (and others I assume as well, whatever/wherever the project is destined). Synthmaster apps had that problem, which was immediately fixed/remedied. Others, not so much. Like never. One of the worst symptoms of the iOS music app platform.
Yes, and that is really unfortunate, and always worth discussing. It's the personal character attacks from some that I hate to see.