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
Oh that I don't mind
I need to edit what I recorded anyway...
It's just a little silence at the beginning, no showstopper
I don't think you're doing anything wrong. I think AUM just needs a mode to wait for a play signal to actually record. MultiTrack DAW does this (which you could also use).
Link doesn't 'get started'. The global play button under the Audiobus icon starts every app that also has a play button in the Audiobus connection panel (so pressing play in the example you provided there would start Loopy).
I never said that. It's just that Audiobus supports state saving. But we won't extend the support for this feature to third party host apps, because it would lead to apps other than Audiobus triggering state changes. This would lead to a very confusing and opaque system which is the antithesis of what Audiobus is trying to be. If you have further questions about this, please contact me directly.
So are both of these buttons considered the "global play" button, or just the play button on the Audiobus icon?
Ah, that makes sense! Thanks!
No, only the one under the Audiobus icon is the global one. The one in Loopy's section only starts Loopy.
Final public comment : sorry if I've obviously failed to make clear that Audiobus would still be the only app that could trigger state changes , at the top layer , with all other host apps loaded into it ..so it would be a single global preset , which is what I understood was the raison d'etre of StateSave .
Sorry if my disappointment at Audiobus let slip any bitterness .
I will leave the thread before another one on this forum gets closed .
Ok. Thanks for the clarification! :-)
Please PLEASE let me midi map audiobus remote triggers to midi notes. Would actually make apps like patterning useful in a production context even when they don't have midi in but do have audiobus remote support. Then I'd be able to trigger pattern changes from a midi controller or even a sequencer track in modstep/cubasis/auria pro etc. It could even be used to have 1 single midi controller trigger multiple apps via audiobus remote.
I would love it if The next AudioBus version could host AUs. I only host things in AUM because I have nowhere else to host AUs. ... well, that and the mixer and because of the routing that lets me set up sends and the nice little bitty targeted FXs and midi routing and the file player and ...
But the point is I would love to, as much as possible, load everything in AB to take advantage of the simpler, better, more consistent app switching, controls, and AB Remote.
If I do load AUM or any other host into AudioBus, I fully expect to have to use whatever equivalent of "state saving" the host offers. Save there, then save in AudioBus. Restore session in AudioBus, then restore session in the hosts. @Sebastian I see your point about not wanting to complicate things beyond that by trying to have "one app to rule them all" for state saving. Sounds nearly impossible to me anyway.
That would be an update to Audiobus Remote, which is not the scope of Audiobus 3. But I'm not ruling out that we might do this later. You're not the first one asking for this, it's a pretty cool idea.
We're waiting for Apple to announce what they've got planned for Audio Unit Extensions this WWDC. Currently AUX are just not appealing to most developers because of multiple reasons (more work/effort to implement them in addition to other technologies, bad monetisation options, etc.) and it would take time and effort for us to provide solutions for these shortcomings.
I'm not ruling out that we might support them at some point (big changes under the hood in Audiobus 3 actually make it possible for us to do so when we decide to do it), but they're not going to be part of version 3.0.
Thanks for replying. I don't mind waiting. Take your time.
I will consider adding a "prepare recording but wait for play trigger" in AUM, but can't you just tap the AUM rec trigger in the AB panel inside SoundPrism? And for apps hosted directly in AUM: use their IAA host transport panel to start AUM's recording.
I think the benefit of the 'prepare for recording' option is that it saves one tap (a tap that would also have to be done at the same time as a tap on the play button, which makes it hard to do).
did I miss something or there are only about 10 AUs or something out now?
Maybe a few more but yep, that's it.
Being accurate there are 21 apps related to AU (host, instruments and FX) , two apps that are getting AU in the near future, and there's one new app that's supposed to come with AU as well. of course there's more but it's hard to keep track.not a lot.
Exactly. Also, if I have a lot of apps attached, I have to hit the global play, the record, scroll on the audiobus panel to get to the right apps (if I have a lot of them open), plus prepare to play, all at the same time. Please do add a "Prepare Recording but wait for play trigger" option @j_liljedahl !!! It would be really appreciated, and VERY, very useful!!!
Thanks for replying! It's always nice to understand the reasoning behind these things. No complaints here! There are perfectly acceptible workarounds.
The big turning point for AU in my opinion will be when the AU:FX series make their way to this format. It's going to be a big day! WOW Filterbox will also be very nice and has been confirmed by Sugar Bytes to be on it's way (eventually).