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
Hmm, I'm not aware of this feature in AUM myself
Do you mean that apps can be bypassed? Note that they're still running while bypassed, it's just their audio that gets ignored. So, they are still started, and not really disabled.
Do you mean they fail to load? I don't have those apps installed on the device I have at hand, so for me they naturally fail to load. I see they are in a bypassed state however, but that doesn't mean they aren't started.
Don't bother investigating, it's a known problem either with Xequence or Audiobus, we're investigating and hoping to have it fixed shortly!
Yep, only the best -- Coshida Beef in gravy (jelly doesn't cut it!).
(I even put it in the microwave briefly before "serving" to bring it to the same temperature as a freshly caught mouse 😉😉😉)
Note to everyone: there's currently an intermittent problem when the state (project) of Xequence doesn't get saved or restored correctly in Audiobus presets. We're not sure if it's a problem in Xequence itself or in Audiobus, but working hard to have a fix ready.
You might want to save your project using Xequence's regular "Save as..." button just in case for now!
Except that it isn't true
As I said a couple of time, the apps does start, they're just bypassed - meaning that AUM runs them outside of the signal flow. They are still running however, taking up CPU resources, etc.
That's how IAA apps work. And the reason we get "IAA zombies".. IAA apps can be launched in background without their UI showing up in the multitask view in iOS. The same happens when Audiobus launches AB3 apps in the background.
Just wanted to mention that if you are AU heavy it’s helpful to restart the host as you move between files. What I’ve noticed is that RAM doesn’t free because it keeps the previous files AUs open until the host dies. This makes it really easy to get OOM issues in situations you wouldn’t expect.
...
Yeah, I have a similar request in my list of features to consider: a way to "unload" a whole channel, meaning it actually unloads all apps/plugins in the channel and just shows a greyed-out placeholder channel, until user chooses to reload it. That would sort of remind a bit of "freeze" functionality in DAWs, you could record the output of the channel and then unload it to save CPU, and perhaps play back the recording in another channel using a FilePlayer node (if wanted).
Excellent work.... At this point, especially with the audio bus integration, we need mult midi channels to send to Xequence.
I know youre working on it... thank you!
Does this support AUV3 Midi effect apps like Rozeta?
I set it up the ways described above and can't get it to work. If it could host though..... Routing midi Rozeta input to Xequence OUtput, then back from Xequence OUtput to Aum, then from Aum to the desired instrument track, then Audio back to AB3, and all without issues. yeah, right.
Rozeta to Xequence on an AB3 midi lane with Xequence set to midi through. Now a new lane with Xequence sending to the app of your choice. This works great. When the Rozeta groove is running the way I want it then I simply record the midi in Xequence and either stop or remove Rozeta. Works great.
@tja thanks for sharing, Audiobus Presets are quite amazing. Glad to finally have AB in Xequence now. (Of course each time I open a preset, I have to buy a dozen more apps, but at least it's tax deductible!
)
Here’s a simple example. Rozeta > Xequence > Ruismaker > AUM. Midi through needs to be enabled in Xequence. Also it’s a good idea to be sure AUM and Xequence are closed before opening the preset. It failed to load properly once for me when they were already running.
Audiobus preset 'Xequence Rozeta Midi Thru': http://preset.audiob.us/WIBRLBwDYf33ILA
From another thread -- Is this what you wanted?
https://forum.audiob.us/discussion/comment/538496#Comment_538496
You should be able to use the “Virtual Midi Out” in the output slot of AB3 and direct it to AUM. Then in AUM select “AUM Destination” for your target apps.
Or, continue to host the apps that don’t receive AB3 midi in AB3, but on the audio page only. Then use the virtual midi out to route to them directly rather than through AUM.
The virtual midi out is a newer (somewhat reluctant) capability added to AB3.
If that’s confusing let me know what you’re trying to do and I’ll post an example.
Any recent changes to 'best way' of setting up this AB3 > XEQUENCE > AUM triangle?
@tja @wim I've been primarily using a pure Xequence > AUM setup but thought I'd try to include AB3 for the perks mentioned here.
When I download the two AB3 presets above, nothing is setup within Xequence. Is there still manual stuff to be done in addition?