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.
Audio units that work in Logic on Mac and iPad
I was surprised that Bleass Omega doesn't work on both the iPad and the Mac in Logic. If I load a project on the other platform, I get a message telling me it's not compatible.
Which got me wondering. Which AUs work in both?
Comments
Moog D, 15 and Animoog work on both systems. Only one purchase needed.
But I found them not the most reliable on Mac.
Otherwise I’m using lots of Audio Damage stuff on both systems. Had to pay for the Mac version separately though.
Good question. I haven’t found a list, but you can go a long way with iPad apps from these developers, many of which are also Mac compatible:
Rob Jackson
Fred Anton Corvest (FAC)
Yonac
Moog
Brambos
iceWorks
Weston Fletcher (Lo-Fi Tape / Piano)
Markus Teufel (Octachron)
Arter Antoni Nowak (Augmatic GRE)
Artera (guitar amp SIM)
Mela works on both Intel and Apple Silicone Macs.
Nearly all Fingerlab’s Apps work on the Mac
Koala
Thanks all! Those are some good lists to get me going. I have a bunch already, but only on the iPad.
i have a ton of music apps and i'm setting up a mac mini m4, so i'll pitch in.
AUv3 plugins (iOS apps) that seem to be working in Logic Pro on a Mac Mini M4:
MIDI FX:
AU Generators:
AU Instruments:
AU MIDI-controlled FX:
Audio FX:
it's great to have patterning and chordpolypad, igor's inventions and the apesoft soundlab, the moogs of course, and all of these things.
then there are vsts.
Fantastic list colonel_mustard
@colonel_mustard 👍
Howdy, there's an important distinction that doesn't often come up in these discussions as it's not really obvious in user land. But, I like to bring it up from time to time, with apologies to those who've heard it before
There are essentially two options for making an iOS app available on macOS.
(1) Apple Silicon Mac Availability
Starting with macOS Big Sur, compatible iPhone and iPad apps can be made available on Apple silicon Macs. Apps will run natively and use the same frameworks, resources, and runtime environment as they do on iOS and iPadOS.
The developer can enable this, simply by checking a "Make this app available" option on App Store Connect.
(2) Native Build / Universal Purchase
In this case the developer uploads essentially two different apps that use most of the same code, and makes both versions of the app available as a single, aka Universal Purchase.
This has the advantage of being able to support older Intel-based Macs and also supports Catalina. This also gives the developer the option to focus on platform-specific differences.
I think the majority of the apps you see available on both platforms use option (1). Personally, I prefer option (2) - it's a bit more work, but there are also some technical benefits to it, especially during development.
As an aside, I haven't yet seen any options on the developer side to make apps automatically availbale for Neo. All I see right now is options for Silicon Macs and Vision Pro. Edit: This is probably due to the SDK version I'm using - there's a forced update for developers on the 28th April, if memory serves.
Very useful information @Rob_Jackson_Music
Just to add a bit more clarity...
Even without a separate macOS-native build, the developer may need to include different code paths for macOS and iOS. There's a list of possible reasons for that, depending on the AU itself and the QA team's standards & diligence. There could be issues coming from desktop apps that will impact even the iOS version's behaviour (if the developer prefers the plugin performing exactly the same regardless of platform).
As a side note, there is also AU validation on macOS, which either comes free or requires a ton of work in unfortunate cases.
Obviously whatever effort (+ followup work) you put into ensuring proper interoperability with host apps on iOS, you typically do the same for macOS host applications before you enable availability.
So I'd recommend avoiding phrases like "simple checkbox" and variants thereof.
good knowledge, gang.
fyi, nearly all of the apps in that list carry the disclaimer: "Designed for iPad. Not verified for macOS."
the moog synths (animoog z, model 15 & model d - not the moogerfooger fx, which sell for $$$ as vsts), chordpolypad & steppolyarp, fac chorus & phazer, mirack, fugue machine rubato, layr, solderbox & battlestation and radio unit are all officially "mac apps".
also, i was trying to remember why i'd left out ivcs3 & mood and it's because their standalone apps crash, but the plugins are there and they seem to work as normal.
bit maestro's another one that has a janky standalone app - in this case, rogue ui scaling - but the plugin seems to be ok, and it's a good one, bit maestro (an oto biscuit-inspired crunchy thing - i shall keep it!)
@colonel_mustard most excellent list am recommending you are elevated to general_excitement.
much obliged, field marshal goodyear.
dulce et decorum est pro fora scribi.
Adding to that -- native versions with intel support:
Apple Silicon only:
Fair point. But in theory, that's all a developer would need to do, and I suspect many do just that.
In practice, there's a difference between theory and practice.
all 3 of the yonac zodiak effects (echo, plate, octavizer) appear to be working fine in logic on an m4 mac mini.
i'm tripping over tape echoes and plate reverbs on desktop, but not octavizers - it's good! satisfyingly just-deep-enough imo.
If memory serves, when Apple Silicon Macs first showed up, developers had to submit an update removing the availability to keep existing apps from being made available automatically.
fwiw, Rob, as one still stubbornly clinging on to my 2015 Intel MacBook Pro, I really appreciate the extra effort. 😎
It's also a strong contributing factor to my insta-buying of your apps.
Cheers @wim! I still use my semi-retired 2015 MBP for testing - still a very capable piece of kit! Kinda makes you wonder if anyone's still saying that about an 11 year old PC...
All I ever say about my old Windows notebook is, "Surely there must be something worthwhile I can do with this?" The answer is always "No."
My Raspberry Pi 4 gets more use. Way more use, actually.
Not really, no. Not even in theory. If you google it, "gotcha" lists average at 7-8 bullet points (fortunately I only ever had to deal with one of them... mostly).
And then there was the issue whereby multi-threaded code on M1 got "trapped" on Efficiency cores, and you needed to get up to speed on Audio Workgroups, etc. But this is no longer a Mac-exclusive issue anymore
It's a different question though if you're using components and techniques that are built with universality in mind from the get-go.
Also out of the very last 3 plugins I installed, only 1 worked. But that's just a sample size issue, as I remember having generally more luck overall since the availability of the M1 (though for example automation problems in Logic Pro seemed to affect even very highly acclaimed apps).
@zoltan - making an iOS app available on macOS, is literally, just a checkbox.
Making sure it actually works, yeah, sure... different story
I don't know if the App Store review team actually test on macOS if you make an iOS app available like this.
I suspect not, which is (maybe) why you see a message on the App Store along the lines of not verified for macOS.
Oh I see
Terry Pratchett logic then. A bit unexpected, but when in Rome...
"All Fungi are edible. Some fungi are only edible once."
That checkbox defaults to on / true for new apps. I don't think it's safe to then assume all developers will test their app on macOS, even if we both agree they probably should - that's kinda my point basically.
Or rather, the difference between this, and a native macOS build / universal purchase.
ChowdhuryDSP’s BYOD, ChowCentaur and Chow Matrix work on my M1 Mini.
you're quite right.
i left them off because he also does free mac-specific versions, but there might be advantages to sticking with the apps in terms of preset sharing and minor ui differences, or something along those lines (i've not investigated - just thinking aloud here).
all of his apps are available for free to everybody, everywhere, on on mac, pc, linux and ios:
https://chowdsp.com/products.html
he's a bright spark, that jatin chowdhury.
@colonel_mustard Honestly I’ve had them on my Mini for a while and I don’t remember if I installed the iOS version or not! And I don’t think I knew about Linux versions either. Thank you for bringing this to my attention (again?). I know some Linux using producers that might not be in the know.