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.
CPU Load Comparison Article - Contributions Welcome (PLEASE HELP!)
Misconceptions about what the CPU load indicators mean are so common that I've tried to get an article started on the wiki and hope that knowledgeable folks here can help improve and refine it so that we can just point to the article when the topic rears its head.
I've made a rough start at:
https://wiki.audiob.us/cpu_load_comparisons_and_testing
If you have something to add or correct or good threads or articles here or elsewhere to point to, please consider sharing your expertise.
Comments
Great idea.
I’d also love us to attemt to devise a system for benchmarking plugins too.
It’ll probably be tricky, but ideally we would be able to give every plugin a universal CPU load rating from 1-10
And also give an estimated load capacity for each iPad model. For example, a 2018 iPad pro might have 40 units capacity (potentially)
There are some methods that people used for running some benchmarks and I have linked to threads that mentioned them. Perhaps someone would be willing to add sections to the wiki article with the recipes used (and links back to the source)?
I also like the idea @espiegel123 and really like the benchmarking idea along with cpu load rating as suggested by @tk32 and agree that it’s very tricky since everyone’s workflows/hosts/devices have such wide variation, but nowhere near that of desktop. It seems doable with some dedication, cooperation and a format of some sort to maintain result consistency.