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.
AUM. Anyone updated yet
Hi
AUM works like a dream
Don't want to update if anything got broken
But to be honest I doubt it, as this app is so amazing!!!
And so so well programed
Comments
I haven’t updated yet but I’m wondering what some of the updates mean. Like what exactly is “keep running bypassed AU plug-ins, but set shouldBypasseffect to allow optimization”?
It sounds like when you bypass effects it takes them out of CPU?
The bypassed AU app instance keeps running but it doesn’t effect the sound chain so that when you add it back in again its timing will still be the same.
Another question I have in general is: Are the MIDI Ctrl mappings saved with each Session or are they global? Obviously I would want my controller knobs to have unique assignments for each song/session.
Your MIDI setup is saved as part of your AUM file. If you have IAA apps, they may not save your MIDI settings. If you have an all AU setup, all MIDI settings will be saved. You can also combine Audiobus 3 and AUM together to take advantage of IAA apps that have Audiobus 3 state savings and route MIDI from Audiobus 3 to AUM .
There is no reason not to update AUM. If there's an update, just do it.
The new bypassing update helps keep AUM more stable when using AUs, which can cause instability and cpu spikes when bypassing and re-engaging Audio units, I've been testing this for a few weeks and I get far less problems with AUs than before. The only downside of this is that when AUs are bypassed they still affect the cpu.
so basically it's a great update for stability
nice!
Is that the same behavior as before, though, as far as still affecting the CPU? For example, I have one mastering project that has ~12 tracks, each with a bunch of AU's assigned to individual tracks and in total it really taxes the CPU. Is this likely to help with that, or is there a chance it will crush it?
It just means that the overall cpu usage will be the same even if the AUs are bypassed, before when AUs were bypassed the cpu usage would drop. So for me it just means ejecting any unused AUs in the session to reduce overall cpu if necessary depending on your device and cpu load.
But ... what if it screws up the App Store or messes up my emojis?
Last couple of days I was having trouble closing AU windows. The X button was unresponsive and I had to push it a bunch of times to close the window. Now it seems back to normal, but I don’t see it in the update notes specifically.
Felt like I was going nuts before.
I still have the closing problem
Thought it was me, but it's really annoying
Update works perfectly on iPhone 7 Plus, AU presets window close now properly in landscape mode it’s nice!! Long awaited bug fix for me.
No AU closing issue here, and when bypassed AU uses cpu much less but it’s not zero. Had some demanding sessions last days and everything is ok.