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.
Issues at 2048 frames for latency in AB3 and AUM
Yeah yeah, I know, that's insane latency, but since I'm not interacting live, I'd rather have the processor power on my base 2018 9.7in, so cut me some slack 
Anyways, I've found 2 apps that do NOT like the 2048 latency settings so far.
Both Zeeon and SF-1 Stereo Filter crash in AB3 and AUM when I have them set to 2048. Every other app I've rocked so far has had no issues running at 2048 frames. Has anyone else run into this issue?
Comments
These issues are in the plugins not the hosts. Report to the developers of the plugins with which you are having issues.
I've reported it to everyone except SF-1 so I'll get on that. I was more curious as to if anyone else had experienced it.
Yes. Some plug-ins don’t like huge buffers. Someone recently reported that Model D suffers from this.
My experience is, buffer size over 1024 rarely saves any CPU if at all, but can occasionally cause trouble.
Most noticeable downside for me was the timing issues with some AU midi seqs/generators (they kinda become lazier), so I’m going 1024 max, and only when needed and actually helps.
The law of deminishing returns applies here. 1024 and upwards don’t necessarily give you better performance. I think the sweetspot is somewhere around 512 if you need CPU over latency. Any higher and you start increasing workload again (every frame still has to be calculated and 1024 frames is a ton of calculations for one buffer).
With convolution apps and a substantial IR, though, i often find that at 1024 the performance is MUCH better than at 512 on my device (iPad 6). At 512, it is often unusable with a long reverb IR at 512 and works well at 1024.