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 problems?
Still a newbie so maybe I'm missing something.
Running Nave into Sugar Bytes WOW and then recording in Loopy - constant signal breakup. Basically just a crackling mess, exactly like CPU overload when recording on a desktop DAW. Same result when just outputting to speakers. Nave on its own is fine but as soon as any FX unit is added, signal breakup. Any suggestions?
Cheers
Comments
Close all apps completely by double clicking the home button and kill all background stuff. Open Audiobus before anything else, set the buffer size in Audiobus to 512 (the slider at the top). Then start opening Nave, WOW and Loopy. In most cases, the first audio app that you open will dictate what buffer size every subsequent app will use. If that doesn't work, not even after a reboot, and you're on a later device like iPad 4/Air/rMini, do a hard reboot by holding down the home button and power button, past the red shutdown slider, let go when you see the Apple logo. If you've been using IAA there might be some stuck background process hogging the CPU.
If you're on iPad 2, both Nave and WOW will really push the CPU to the limits (depending on presets etc).
WOW is also very CPU intensive. Sometimes I have to load it and just give it a couple minutes to calm down before I can use it. It seems to like that better.
Your best bet might be to record your Nave part and run your recording through WOW after the fact.
.
Thanks guys - it's an Ipad 2. I guess that's the problem. I can understand how Nave and WOW would chew up the CPU. Guess I'll just have to learn how to work within the limits.