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
Maybe the compromise is a better library of standard features that developers can pull from? I certainly hope creating AU apps becomes easier as we still see new apps where developers say they wanted to develop an AU but it was too difficult.
At least hosts should offer alternatives. It’s Ok changing a standard, but many a time have I programmed a sound in the stand alone for it to not play ok in a host. Take a new app like Quanta - try some of the sounds in your DAW of choice. Crafting a sound for hours that then plays like a damp squid in your DAW of choice is such a pain!
Maybe a bit, but not much. Because as long as standalone apps are still demanded, people will expect each app to have Virtual MIDI, CoreMIDI (in and out), Ableton Link, IAA, Audiobus (audio and MIDI), Bluetooth LE, MIDI Clock Sync, Audioshare, Files support, bla bla bla. I mean... none of these things are simple drop-in components. And they all interfere and conflict with each other. These are all "basic" features in the minds of users, but even just figuring out an architecture where all these "standards" work together peacefully is a nightmare
Together this big ole heap o' spaghetti redundancy requires massive amounts of development, debug and support time which could be avoided by simply doing it once: in the host. So all subsequent apps can benefit from it. It's a much more realistic scenario, which equally applies to having onboard sequencers, keyboards, XY controls, etc.
As technical complexity grows (and becomes the norm), modularity becomes the only feasible direction to keep things manageable from a development point of view.
That's what I mean by getting rid of the redundancy. I'm by no means saying these things are not important. There are just too many of them to keep putting them in every single app
This 👆
Hot take:
As more and more users move to AUv3, we're going to see less robust user interfaces built into sound generator apps.
Right now, the hardcore AUv3 market is under 5k people.
When Synth One adds AUv3, there's going to be an AUv3 Synth with 100,000+ users.
100k+ users may expand the AUv3 market and awareness overnight.
(Maybe, it will be the kick in the rear Apple needs to pay more attention to AUv3).
Additionally, this will hopefully inspire developers to create additional controllers, via Host Apps or plugins.
We're at the beginning of a tipping point.
That would be very cool. There are some great developers who are doing just that -- Props to @cem_olcay who is planning on implementing some features of his upcoming ScalesBud plugin into AudioKit Synth One.
Hopefully, people support his generosity by buying copies of his apps in the app store.
I so want an:
‘I’m hardcore AUv3’ - t shirt
Modular design clearly sounds like the smartest approach for now and also very exciting. Bring it on!
It’s down to the host. View switching in a well done host should be as seemless as view switching in a standalone app. Hosts need to improve for the real benefits of AU to be felt.
Is there, though? It seems like the tide is going in the opposite direction, and two respected Devs have confirmed that in this thread.
I don’t get that. Here are two pics of Spacecraft. One in host one standalone. Major difference?
Yes, if you only want to use one app at a time, obviously it's more efficient to have it be an all-in-one app. But once you want to start running multiple apps simultaneously (which is what 90% of the people here do most of the time), using self-contained standalone apps results in far more clumsy app-switching, instability and nasty inconsistencies wrt connectivity than using those same apps as AUv3 in a host.
If this no stand-alone model is the future why has it not disappeared in the desktop world?
Yes some apps need their controllers as part of the AU itself to be true to use concept. As seen though this is possible. The same is true of having any midi input device if desired. So in that sense we agree that some are best kept together, yet they can still be full screen AU with little difference to use and many advantages of AU. Some however are much more suitably split imo.
The advantages of the split approach are many though and if done right, you would not notice the difference between using them as a standalone app.
The host is the key to making the seperate feel just like using a singular app. The host needs always onscreen switching and a fast way of loading saves.
If a certain design UI (midi interface input design) is important to an app, it can be sold as a packaged AU pack by the dev. As I say, it’s important that the host controls things well - most do not at this time as AU is still developing and many AU hosts have yet to catch up.
I'm actually a big hater of app switching. But I don't count swapping AU views inside a host as "app switching". In something like AUM, apeMatrix or even Cubasis, it's a simple matter of minimizing one panel and expanding another. That's hardly "app switching" in my books. It's simply a way of coping with screen size constraints.
You know what I'm happy with? External MIDI keys. Glad my problems were solved.
I definitely think that when a well designed host finally makes its way here, you may feel different. When the hosts and AU midi apps get really good, they should gel just as well as a stand alone app, yet you will just load a preset from the host that will be whatever you want it to be. Saves from the host will back up everything from sound design to input UI used. It’s probably hard to grasp the concept until it finally happens - if indeed we get that far. Apple could ruin it all for us at any time lol
There's what we might like, and then there's reality. Synth app makers often don't provide elaborate or innovative built-in controllers, and no reason to think that's going to change.
I've never used an Omnichord, but I'd love to have a host like AUM where you can choose from a variety of touch screen controllers. Playing the standard piano keys interface on an iPad is one of my least favorite activities. If developers with imagination and some experience of playing an actual musical instrument could just focus on that one function, we'd get some more options that would be able to trigger any synth hosted. I see that as more likely than many devs suddenly building new controllers into their apps.
I like if a standalone app has a great controller built-in (like GeoShred), but that's not going to happen often. I find AUM quick and easy. A modular approach would provide great flexibility.
Yep, just have the standalone host a midiFx AU controller.
I like it.
Using AU midi controllers in host opens up all those wonderful touch screen iOS interfaces to be used at the load of a preset.
Even self designed interfaces that could be saved and shared between us users. Imagine a KRFT style designer that controls any AU midi exposed from any AU app.
Also to take this approach one step further, we need more iOS specific hardware midi controllers. When the hosts get great, hopefully we will have some great hardware controllers join the party too.