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
I wonder if turning on "low power mode" to limit animations would help?
I just fired up Audiobus 2 and built a preset that previously gave me problems in Audiobus 3. What a bliss to be using AB2 UI, apps load almost instantly, it truly feels like a Ferrari. I’ve actually tested swiping between apps and none of them gave me spikes that would go too far, I also tried apps settings that I know are quite taxing to the system: all fx up in Turnado, Octaver preset in ToneStack, stuff in Samplr etc. The last before the last group of spikes on the right is me opening the right hand menu drawer in AUM. The last one is when I double clicked on home button to to go to all windows view. I will try the same with AB3 when I have a moment.
This is actually with 128 frames settings and using Tc helicon voice fx rack that I wasn’t able to use on my air 2 even at higher buffer settings.
And this from another CPU monitoring app, pretty much confirming the same thing. In the pic below I tried a lot of stuff in the background using a midi controller and that can be seen at the beginning of the timeline. Then when I start to swipe between apps the spike show starts.
@MusicMan4Christ said:
Guys I truly recommend looking up Brambos Battery thread. There were tons of great iPad tweak suggestions that made a huge difference with cpu spikes. In a bit she’ll the biggest culprit was Siri. It has been really embedded in the background Processes. I went in settings and one app at a time disabled Siri. Disabled background stuff, but not just disabled it, you must lock the darn thing in restrictions in settings. There you must specify to lock certain things from retaking effect again. Once I did all these things my Air 1 not only got a new life, it actually felt like a new iPad. I’ve been blessed with a new iPad2017 and will redo all these changes in settings to ensure I get the most stable cpu processing and stop all unnecessary background junk!
I copied this above comment from a post that closed and followed the recommendations that **Musicman4Christ **recommended.
There were three main things that my son and I changed as we had all the other configurations still in tact in the Brambros thread.
The three changes we made:
1) Turned off WIFI
2) Turned off SIRI Completely in settings
3) Turned Off Auto Updates
Those were the only three things that were not turned off.
Update:
Knock on wood, but so far I have not had DSP spikes. I also played in Cubasis for the first time and I was able to record a few tracks without interruption. I will continue testing and report back if it solved our issue.
Thanks!
@Chris_Randall
This is such a bizarre and counter-intuitive report that I had to try it myself. Yup, I'm seeing the same thing. Albeit not as extreme as Janosax, but still, reported CPU usage goes down when the Audio Damage UI is open. I'm seeing it in all AD effect AUs that I have (Dubstation 2, Eos 2, FuzzPlus3, Replicant 2, RoughRider2).
I do not see this with other AUs (apeSoft, Amazing Noises, Humbletune). Those behave as one would expect; the CPU usage goes up when their UIs are opened.
In some cases (most notably with Replicant) the issue only happens after the AU UI is opened for the first time: e.g. CPU is initially showing 15% (and this is with it running):

Open the UI and it goes up to the low 20% range:

Close the UI and it goes up again to over 30%:

From here on, opening the UI drops reported CPU usage to low-20s, closing it pushes it up to over 30%.
Another point: this is on an iPhone 6s. On my iPad Pro 9.7" it's a bit more unclear. In some cases I see the issue, but it's only a couple of points and could just be random fluctuations (but seems pretty consistent).
I just spent a bunch of time with Cubasis building up a fairly complex track with a bunch of effects including internal and AU reverbs on several tracks with no problems. The CPU meter was hovering around 60%. Doing something similar in AUM with the usual synths and effects causes glitches. I also get glitches in FLSM with not too complex tracks. Never had any glitches in Grooverider. Air 1 with latest iOS. Kinda strange...
unfortunately that's not made any difference for me, still spiking in AUM. pro 12.9 2017
Yeah, I think most of us regulars will have that covered.
Definitely good keeping those tips floating around though.
My iPad Air is doing much better than that...
I think it’s important to specify your buffer settings. I get minimal spikes at 256 samples, but as soon as I switch to 128 samples any changes in the GUI causes fairly large spikes. This is 2017 iPad Pro. What are everyone else’s experiences when changing the buffer?
Soundshaper - Forgive me if this seems like a basic question, however I am still new to all this. Where do I check the buffer size or change it? Thank you and I can report back.
Thank you CracklePot,
Appreciate it. After much playing today, I am glad to say that when I am not switching any UI's just have the AUM and CUbasis running that I have not had a single DSP Spike artifact after making the changes earlier. I can confirm that the buffer is at 256.
SO far so good....Thank you everyone for making me and my son welcome here and for providing your experiences on DSP spikes.
Glad to hear things are running smoothly for you guys now.
Just for the record, I’ve been using these two apps for checking CPU behaviour on a timeline. They’re both free.
System Monitor Ultimate by Arvydas Sidorenko https://itunes.apple.com/gb/app/system-monitor-ultimate/id740765454?mt=8
System Status Lite by Kenichi Yoshikawa https://itunes.apple.com/gb/app/system-status-lite/id992911130?mt=8
I totally agree with you, hence why I've gone back to Desktop in creating projects But I still use Air 1 as a sound source (sound Genertator) into the Desktop. Also I use he iPad as a scratch pad for ideas( making loops, Midi or WAV, then put hem into Ableton, or FL Studio, etc)
Hi
Apologies for the duplicate. I can see this is a hot issue.
After reading your entries I guess I'll start with looking at all that background processes and animations (Siri and the rest). Let's see how it goes.
Thank you again for your help.
Thanks for the links. I was going to ask what was used to make those CPU graphs, but you have already provided an answer.
I’ve noticed today, in an AB3/AUM loopy several AU FX (no Audio Damage) project, that audio is more stable at 128 buffers when I hide Audiobus switching toolbar. Cpu goes from 50/60 % to 44 % in AUM when I do that. At 256 buffers, things are much more stable. 256 is nice for playing virtual instruments, but for sax recording I need 128 for proper monitoring timing. Already noticed that audio was more clicks free at 128 when visualizing Loopy window instead of AUM. But hiding AB toolbar makes audio really stable, with more consistent cpu usage while reading AUM cpu meter. Definitely graphics over audio priority issue.
Also, all usual tricks are a necessity: disable Siri, visual animations, background processes, etc. And don’t forget to use plane mode too. Perform a reboot is very efficient too. Using a ram cleaner app is useful too, I use iDoctor device but it seems it’s not available anymore on AppStore. Usually clean ram or do a reboot before every important music session.
Edit: it’s on iPhone 7 Plus with iRig Pro i/o, 44.1kHz.
@StMichaels could you please add to the threads title to state their device, iOS and apps they’re using?
It might help developers to get a better idea of what’s going on since it’s now become the main thread on the subject.
Could do with something like
DSP Spikes on IOS 11.2.2 (include device and apps you’re using)
... or something along those lines.
Thanks
So I'm finding just scrolling around the AUM channels can cause the spiking with AUs, so it's not just screen jumping but does point to graphics being the issue.
This isn't just an 11.2.2 issue though, it's 11.x and was also the case before on 10 because I remember trying to troubleshoot spikes with Gabriel with the Audiobus 3 beta.
I can certainly see the benefit of some kind of iOS audio developer group which could approach Apple about this collectively.
At least Apple could give us an Audio priority mode or something
I have been considering an iPad upgrade from the Mini 2 to the 2017 iPad.....this sort of stuff makes me want to not bother and invest in something that works properly instead.
That Zoom R24 is looking more and more like a better investment by the day.
It's all about your needs. If recording audio is your principal musical activity, and you want something reliable, the Zoom R24 is a possibility. But you will not have huge capabilities of today's music tools. A good laptop, Windows 10 or MAC, with any DAW will outperform hardware studios IMO. And these are stable and mature platforms. iOS is younger, and not dedicated to professional musicians IMO. There are issues here and there, always a feature that miss or bugs. Desktop music softwares are not bug free, but on a properly optimized rig you're good to go this platform again is mature. An iOS setup even tweaked for music still can have some issues like those CPU spikes. But where iOS iPads and iPhones shine, is all about mobility, touchability and creative apps, where desktop/laptop music tools don't really evolves anymore since a decade. This is what we like about iOS music IMO, despite all those issues, not professional environment, and to be honest we all know Apple don't really listen to iOS musicians. We have to do with that tool how it is today. If it becomes really unreliable, I'll switch back to laptop, but I use with almost no issues my iPhone 7 Plus daily on complex live AB/AUM/Loopy setups, produce in Gadget, Blocs Wave, Beathawk, Xequence, and I love so much those apps, I never have been so prolific than on iOS, there are huge qualities to that platform too. BTW, if I buy an iPad not sure I will go to a Pro, because they're not that "pro" for what they're asking for. iPad 2017 seems more adequate and well priced.
There's the magic word that may have just made my mind up for me
I’ve just sold my Pro 10.5. It feels good to be back on Air 2. Everything runs smoothly but I had to roll back to AB2. Now I have everything I need and will need for the foreseeable future. AB2 actually works quite well with AUM and presets recall perfectly. There is an issue of apps plugged into AUM only listening to host tempo changes but I’m simply saving AUMs tempo as an Audiobus preset and it just works. All in sync, super fast, all loading as intended, including Samplr and Loopy sessions. Bliss.
Ah, £500 aren’t burning my pocket either
I wish I heard more stories like this on a more frequent basis.....It IS a nice place to be when it works...but oh so frustrating when it does, then it doesn't, then it doesn't, then it does, then it doesn't LOL
Funny you should say that, for some reason Loopy is again not recalling the tempo when session loaded via Audiobus preset.
Michael knows about this so should all be good soon. Apparently it is picking up some random Link tempo.