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 Goes Red on Graphics/UI
I’ve gotten and still do get so annoyed by the fact that when you open an UI in AUM to tweak the parameters whatever, dsp goes up to red and start the worlds most frustrating sounds. I can have a lot going on with many instruments and effect plugins rollin and as long as I don’t open anything, the dsp stays around 50-60% (as an example). Then you wanna tweak something and hell is soon upon you.. arghh!
The strange thing is that it doesn’t seem to matter too much what UI it is although ones with a lot of movement is tougher. I know some UI, like e.g ButterSynth uses huge images for the interface so one could suspect that would start eating on memory.
Can this not be fixed somehow so memory for UI is allocated (or whatever it’s called) separate from driving the sound. I got this feeling that AUM handles this worst of all but that might be completely wrong.
I dunno I understand nothing of this, I just felt I needed out of my system. When I got my M1 w 16Gb ram I thought that I would never have to experience this shit again, so wrong...
Comments
Maybe share that on the AUM Discord server. Jonatan responds to most things.
https://discord.gg/NkXb6aD7X
I suspect the problem is more likely with processor time than memory. AUM runs the the plugin, and it busies itself constructing its GUI, animations, etc., causing the processing time to exceed the buffer time. A larger buffer size might alleviate the situation.
I feel like AUM has been spiking my DSP regardless lately. Maybe my iPad’s getting a bit old though.
Still happens with 1024 buffer. Not just graphics in AUM. Also happens switching to any other app (e.g Xequence). Seems to get worse, longer session has been open. At least in my device/use case. Any changes in graphics can cause spiking.
ButterSynth is heavy in any host regarding CPU usage. What other apps are you using?
Opening an AU’s ui can spike the cpu in any host. It depends on the AU. This is especially true if the CPU is only lightly “stressed” when the AU ui opens because of the way iOS prioritizes things.
Have you been noticing the issue for a while or only since the very recent update?
As far as I know, AUM does not support multi-core audio processing in the way that Cubasis and Logic Pro do, so it's still possible to use up DSP resources pretty easily. I'm probably explaining in a way that reflects an incomplete understanding, but that's the gist.
I seldom use Butter, it was just an example(e.g) of a heavy hitter. I don't have many goto apps, hence it vary a lot and, ( @uncledave ) I do know how to take measures to try to harness the "going red" stuff like sometimes I drag other apps to the left to disable them temporarily so I can work with whatever it might be, now, rising the buffer isn't that much fun though when you play guitar as I often do, over 512 and the latency is too noticeable (and every now and then I accidentally delete the app when I just want to activate it again (grrr undo, where are you))
I didn't start the thread to get tips on how to avoid it as I think I've gone through most solutions available, but rather a frustrated call out .. to the wild..
It's always been there but it took me a year or two (I'm a bit slow, I know) to understand it was the (whatever) apps UI that caused the increase.
All good 😊
I want to clarify that I love working with AUM, it really suits my mindset and approach. I guess that's what make it all so frustrating. I mean I could just use Cubasis instead but, I want to use AUM.
That being the case, this isn't really AUM issue. It is the nature of how the OS works.
Oh this resonates with me. I do think multithreading would really boost AUM’s game. It makes sense that it can get bogged down easily running everything from one core if you start asking it to do more than a couple things at a time. And I agree that Cubasis handles tasks more efficiently CPU wise, but for the stuff I like playing (generative, live guitar, etc.) AUM just feels so much more straightforward to set up MIDI and complex audio routing.
GarageBand has been handling a lot of my use cases surprisingly well that AUM is starting to struggle with. That being live setups where the software gets out of the way. It can’t do nearly as much but I’m sketching out fun stuff.
For real-time audio, multi-threading is more challenging to implement than you might realize — and many implementations increase latency to be able to do it. Jonatan wrote an informative post about it:
https://forum.loopypro.com/discussion/comment/1369610/#Comment_1369610
If it's true that it gets worse the longer the session has been open, then it could point to a memory leak in one of the plugins you're using. It could be an AUM memory leak as well, but that's less likely given how many years AUM has had to shake those kinds of things out.
Sadly, that's the reality with devices optimized for battery and heat conservation. It doesn't matter how powerful the device is compared to a desktop, the operating system still scales things back aggressively when it decides it can. We wouldn't notice that with most apps, but with music, the glitches while it allocates more power are noticeable.
I know it's tough to hear, but once we get to that point with our devices, committing to audio and idling plugins is the only way to manage things. We're fortunate that AUM and Loopy Pro which can idle plugins, and other DAWs with "freeze tracks" capability can make it so that we can do this. Some apps make that easier than others. Unfortunately it's not super easy and fluid to do that as you go in AUM.
Yeah, I've been thinking like so as well, although it's so far from my safe space I get nervous just admitting that I've done so. 😃
That on the other hand I had not considered at all. Appreciate the educating input. 👍🏻
Thanks for notifying that a more powerful processor than mine won’t fix this issue @Pxlhg
Thanks for technicals @wim