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
Audio Damage apps are all pretty CPU efficient as far as I can tell from pretty regular use.
Thanks. I'll take a look.
Some very efficient ones (many instances possible):
Bram Bos Phasemaker (the most efficient that I know!)
KQ Dixie
AD Phosphor 2
AD Quanta
IceGear Laplace
iSEM
bs-16i
AudioLayer is efficient with only one or two instances but even with the simplest programs I have never been able to use more than 5 instances in Cubasis at the highest audio latency and without any insert, send or master FX enabled.
I'm a big fan of Phasemaker and have been making patches for it lately, but that's not my experience. While not being heavy on cpu (like, say, Model D), it definitely uses more cpu than the lightest AUs in my experience: KQ Dixie and Icegear Lorentz.
I'm using an iPad Mini 4, and I check cpu use via single instances in AUM. Maybe that's not the best approach.
¯_(ツ)_/¯
How is everyone evaluating what is a low CPU app? Guy feel or using some sort of meter?
Pretty sure we established earlier in this thread that any sort of logic will be refuted as not logical enough or not my logic, so I think guy feel is, instead, the most logically accepted
Guy feel... lol
I've noticed that average CPU usage and possible number of instances are not exactly related. What I've done is play a little repeated test clip of 4- to 5-note chords in Cubasis, load the AU synth to test and duplicate the track until either dropouts or 100% cpu and silence happened. On an iPad 2018, I could load 20 instances of a Phasemaker 6-op fm patch, 17 instances of KQ Dixie, 16 instances of AD Phosphor 2 and 11 instances of Laplace.
The most resource-hungry with multiple instances were AudioLayer, Zeeon and Synthmaster One. Even Model 15 was slightly better but I guess that depends on the cabling
This makes a lot of sense to me as being potentially much more accurate than simply looking at the cpu meter in AUM when using one instance of an AU, which has been my approach.
Using the AUM meter and sometimes this other overall metering app, forget the name but it shows a nice over time graph.
That sounds like System Status.