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 DSP issues...help?
Hi! I'm have a problem recently with my iPad Air 3 running AUM where I am unable to run many instances of anything without it overloading and glitching. I have a video example of it running DrumComputer (I know--high CPU app but not the only one with issues) where the DSP is single digits until I load the app, it shoots way up. Strangely, it comes down a lot when I have the windows open but goes back up when I close it. I don't know what's happening but it's ruining everything. 😭 Any ideas? iOS 13.6, latest build of AUM
https://www.dropbox.com/s/xal924wcqd61snv/RPReplay_Final1615143015.MP4?dl=0
Comments
Sounds like the usual CPU throttling issues. iOS is constantly modifying core clock speeds for increased power efficiency and hence battery life. It pops up quite often in the forum ... search for “throttling” and similar terms.
The AUM CPU meter indicated what percentage of currently available CPU processing capacity is being used. If the CPU is running at 50% of its max capacity, and the AUM meter also reads 50%, then the AUM set is actually using 25% of its maximum processing capacity, if I understand correctly.
I notice it more ironically in AUM sets with fewer AUv3s loaded. With a heavier CPU demand, iOS is more likely to maintain higher core clock speeds, resulting in less throttling,
Try lowering the buffer size.
Thank you both! I know the DSP measures is not a reliable gauge of usage but it is actually affecting audio stream in this case which is frustrating. Guess I could unintuitively try working it harder. My buffer is at 256 but I'll lower it and see if that helps. May as well also update iOS to see if that is a factor.
Lowering the buffer makes your CPU work harder. You need to increase the buffer size to lower the CPU load.
I agree with @craftycurate, this looks like CPU throttling. My workaround in the past was to always run an instance of RE-1 with its UI open, even if I was not using the effect. This seemed to prevent throttling entirely.
I do similar. As long as the CPU load across the whole set doesn't drop too low, it should keep the CPU clock speed up, but without any way (I know of) to monitor this in iOS, it's impossible to tell for sure.
Opening a GUI may well open a new processing thread, requiring an additional core or something, which will increase available CPU, hence the apparent drop in AUM CPU load. This kind of apparent CPU drop is very common when opening a GUI in an AUM set with very few apps loaded.
I have the same issue - I don't think it has much to do with CPU as with audio levels. What I discovered is that when input gain is 50% in settings, everything works fine but distortion and drop outs start when it's 100 - that's when DSP hits max. Looking for a way to turn it down but cant seem to figure that out. Will sell my iPad if I can't resolve this. There's a setting under audio in Cubase where it's automatically lowered and so I'm able to load as many plug ins as possible without issues. but then the input gain gets taken over by sth else and distortion kicks in again. Just annoying.
if you get in the habit of setting up a master bus that the mic travels through, you can use it to adjust the output gain and if it seems onerous to adjust that fader, you can put a limiter on it,
@oddSTAR Sth else I observed is that my keyboard controller was sending out 4 or more zones (depending on how many internal keyboard sounds I have layered). Changing it to just one sound helped a lot too
Didn't know you could set up a master bus on AUM. Hmm
Choose any bus as a the source at the top of an audio channel. Make that bus the destination of all your tracks. It takes about 30 seconds or less to add to most projects.
Less time than retrieving snd extracting audio from a screen recording. And adds less cpu overhead.
thanks- tried it and it's really handy.> @espiegel123 said:
thanks- tried it and it's really handy.