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
(Insert usual note: CPU monitoring in iOS can be misleading. https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing)
There's a tiny cpu % indicator at the bottom right of the screen. See above for why it's not more prominent.
Ok noted, so nothing like a GUI'd equivalent to ps terminal command (EDIT: top, not ps!), just that procedure for starting with empty project and building up, and practically testing, and noting the percent indicator changes. fair enough
As noted. in the article wim linked to, the cpu percentage readout is not very meaningful until the cpu is on the verge of overloading. So, noting incremental changes as you add things isn't particularly informative because of how cpu throttling and core assignment works.
All that said, AUM has individual node CPU readouts. That to me is useful as it can point out the relative CPU consumption of individual apps. That's what I'd use if trying to find out which apps might be causing overloads.
The beauty for me with Loopy is the way it can idle plugins. I don't worry much about overloads any more because as soon as I suspect things are beginning to bog down, I can just commit to audio clips and idle the plugins. Because they're still there in the project, I can go back to them at any time to add or change parts. The process is fluid and I barely concern myself with overloads even on my ancient iPad any more.
Yeah, same, idle in loopy is wonderful. but just keeping an eye on what does what, need to know for gigs to preempt issues, not wait for them to occur mid gig. good shout on using aum to additional test some stuff. cheers
The easiest way to test is to load up seversl instances of likely cpu hogs.
Meter is there but values are sometimes ... weird.
CPU use is not worth bothering oneself about on iOS except as a very general indicator, and always taken with an understanding of what is really being measured.
https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing#why_the_cpu_meters_can_be_misleading