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
Glad to help. Good luck
I think > @Richtowns said:
Your feedback was crucial. I was able to track down the bug with this replicable use case. I think I have nailed it. Requires more extensive testing but I have been playing a lot of patches for a long time and it has been steady!
I think I will only be able to deploy a new beta in the beginning of the next week as we have just entered weekend and new versions require human review from Apple.
Thank you all for your feedback and support!
This is great to hear!
Ok, this is good news. Please keep us posted!
There is a new version 2.0.1 (build 100) available for testing which hopefully fixes this problem. Who wants to try it?
The burst is not happening! Although I see some residual audio kicking up after playing a bunch of notes. Check out this video when I start playing around C5.
https://streamable.com/u9p07
Damn thing just about deafened me last night when I tried it with my headphones on!!!
Must resist the morbid curiosity to make tha damaging sound, why is it so tempting?!
I have seen very similar behaviour in other apps too, and I think that it's not "only a DRC bug" but an issue with lower layers like iOS audio too.
Avoiding loud cracks generated by a synth is one thing, but the audio system should never end up in a state that it remains dead even with other apps.
So here's my question to @sinosoidal
What have you done to fix the bug? Limit output levels?
What exactly causes iOS audio to go silent? DC offset maybe?
This should really be described and forwarded to Apple's iOS dev team.
I've had this happen while I developed an algorithmic reverb, and yes, it was due to accumulating DC offset in the feedback loop. Maybe there's an overflow somewhere in CoreAudio when extremely large values occur, and it crashes? CoreAudio also does some final processing (limiter, etc.) before the output so maybe that gets confused... hard to say. The accumulating DC offset would of course be a bug in the client application, but the audio permanently shutting off due to it is of course an Apple problem
Yep, Me too.
It doesnt seem to happen with only one note but two notes at the same time (or maybe the portamento?!) and this weird (can be up to 10s) echo happens. And this does seem to tie into what @SevenSystems is saying. Im sure together we can work it out
Good to see this progress. I've been a bit tentative to dig in since my first experience. Thanks for staying on it you all.
The bug was caused by an invalid memory access. It should be fixed on version 2.0.1 that has been released today.
Working great over here! Can’t duplicate. Nice job ironing it out. Really happy to have it as AU.