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.
The issue of Devs not allowing AUv3 apps to run on Mac M1 [Logic Pro users]
It seems more and more devs release AUv2 on Mac and AUv3 on iPad.
This is a big issue because if you create a project on the iPad with the app on Logic Pro and you then load the same project on the Mac none of the settings on the app are saved.
This is because they are different versions of AUv.
The only way it works properly is if both iPad and Desktop are AUv3.
Let me know if I’m wrong. I’m surprised that other folks are not seeing this as an issue. Maybe I’m doing something wrong.
Comments
This is just about the devs economy - it ain’t justice to sell a supergreat AUv3 app/plugin on the Mac, but the price from iPad platform…
Different pricetag Mac versus iPad may be difficult to achieve…
I understand the economics but if you are a Logic Pro user on iPad and Mac M1 then it makes interoperability useless. It’s currently pointless owning the app on both platforms if you want to share files.
Is there a feasible solution, though, unless devs start selling AUv3 apps at desktop prices with full licenses for iOS / desktop, as Pianoteq did?I can stomach that in the case of an exceptional app like Pianoteq, but the vast majority of iOS apps would not sell if priced at desktop rates.
Best to maybe just export some stems and get on with things. Life's too short.
If you understand the economics, you have your answer. You might not be happy about it, but if it isn’t economically feasible for them to do something, they aren’t going to do it.
Apple may hope that releasing Logic will change the economics, but it hasn’t happened.
You can’t expect developers to choose to lose money just because Apple released Logic for iOS.
Some FAC AUv3 plugins are available in the Mac app store as separate purchases with a higher price, which seems like a reasonable solution. I don't know if Logic would identify them as the same plugin though.
I wonder if there’s a way to either lock the plugin or make it less than useful on desktop, maybe even work but not be adjustable, and then have an IAP to make it work nice?
I’m probably taking way out of my job description/pay grade, but I’ve heard the term ‘ifdef’ in these contexts…
The answer is (depending on the developer) “it depends”. Moog’s presets generally carryover from GarageBand iPadOS files moving over to Logic Pro and GB on macOS. But a large number of plug-in effects (at least from my experience) do not and must be re-entered. It’s a time waster, but there doesn’t seem to be a common method for developers to ensure continuity? Maybe this would be the time actual developers could weigh in to educate the rest of us?
Thanks folks. Your input is greatly appreciated.
I personally wouldn’t mind paying extra for the AUV3 plugin for desktop.
That’s a good idea!
Every AUv3 plugin can be installed on both iPad/iPhone AND Mac, but the Mac version must be unlocked with cash if we wants to change presets or change the parameters that a Logic project insert onto this Mac AUv3 plugs/instruments…
Just give them with the vst version.. like they usually give the protools version
I’ve mentioned this a few times now in different threads but there are two issues: plugin IDs and plugin state. If the developer uses different plugin IDs in the iOS and desktop versions then your plugin is not even going to load at the destination, unless the developer does the interesting fix that IKM did with MixBox so that a single plugin can identify using multiple IDs.
MultiTrackStudio tries to work around some of this by letting you specify both a desktop and iPad version of a plugin in the same plugin slot. If you move your iPad MTS project to the desktop with an incompatible plugin then you can set up an alternative version of the plugin and it will then remember the state of both depending on which platform you are on. You still have to do the initial manual setup but can then move back and forth without needing to repeat this effort.
I am not a plugin developer but there would need to be some way of identifying the version of the plugin from which the state was written. This might be different for AUv3 vs AUv2 (assuming they even have access to state written by different AU versions), plus you would need code to migrate data between different release versions of the plugin. If this kind of meta data is not provided for free by Apple then the devs would need to code it themselves. If they did not include version hints in their blob then migrating between plugin states could be tricky. For example, you might have v1.4 of an AUv3 plugin on the iPad and want to open the project in a v2.0 of the AUv2 version of the plugin on the desktop where the data format has changed considerably due to new features etc. Even worse, imagine trying to support going from a v2.0 data format to a v1.4 version of the app.
The FabFilter plugins do carry over the settings. I have all of them on both platforms. It is a bit hit or miss though. For example, I was mastering a song the other day when I was out and about and made sure to only use FF plugins. then I opened it up on my Mac and while all tracks had the inserts where they are supposed to be, on several tracks they were initialized. Hopefully this can be sorted, as the experience of using the apple pencil on the 11 inch ipad when in a caffe or even outside is very, very good and real work can be accomplished - and then continued in the studio.
If this helps, only Audulus 4 won't work on importing iOS to macOS projects. All FabFilters works, also FAC, Moog, Mela, miRack. Only Mela, Audulus and Moog are universal, the rest of them bought separately for desktop versions.
I have at least ten more universal ones I didn't install, so I can't say anything about them.
I still have scars from the FabFilter purchase, even though it was on summer sale.
Edit: Forgot to mention, my MacBook is an i7 not M series.
Have you reported the issue to the Audulus developer? I believe that it is supposed to work.
Yes, going to notify Marc, I need more time to test everything, the last few weeks were hectic.
It would be good if apps could be free to download and then you pay an IAP to unlock whichever platforms you want to use them on.