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.
AUM issue under iPadOS 17
Hey @j_liljedahl since iPadOS 17 I unfortunately get problems in AUM (on iPad Pro M1) with a few FabFilter and Audio Damage plugins. It shows „Bad Signal!“ under multiple channels. It doesn’t help to restart iPad / AUM / or the session. Also changing sample rate or buffer size won’t solve the problem. Only if I disable and enable separate plugins the channel sometimes will work again.
Do you know anything about that issue? Can I do anything about it?
Thanks man! 
Comments
@jacou : as the alert says, a plug-in is sending an illegal value. You should contact the developer of the plug-ins generating the bad signal.
That message isn't indicating which plugin in the channel is the culprit. Can you narrow it down to find which one(s) it is?
(I betcha it's enso.)
That’s actually a problem too. As you can see it says bad signal under 3 of the 4 channels. When I deactivate plugins on a bad signal channel the bad signal message sometimes disappears after deactivating some plugins, sometimes just stays or appears again after a while. But if I deactivate a fabfilter or audio damage plugin doesn’t really matter. All plugins seem to be affected. There definitely seems to be a glitch somewhere. Some kind of miscalculation is my guess.
Is there no one else having that issue?
I’d be willing to bet the culprit is on channel 1. Ch 1 has a send to Looper and Looper feeds to Verb. There’s a ripple effect going on.
Since ch 2 has no error, my guess is the offender is whatever is in the first slot of ch. 1 since that’s the one plug-in that ch 2 doesn’t have. Just a guess based on process of elimination though.
The thing to understand is the bad signal isn’t an AUM glitch. AUM is only reporting the bad behavior of a plugin. The only way to resolve it is to remove the plugin generating the error - if you can figure tout whic one it is.
Jonatan has elected to pop up the error notification rather than accept audio glitches or crashes caused by plugins. It’s by design.
I see. Yeah it makes sense what you say. I never had that prior to iPadOS 17 though. So I guess some plugins might be effected by the update. Let’s see if I can find the problem plugin.
There seems to be something going on with Dubstation 2 and OtherDesertCities. Since I deleted them from the project the problem didn’t come back. Hopefully it can be fixed.
You probably will need to contact the developer with details about how to reproduce the issue so that they know that there is a problem and how to reproduce it.
Getting loads of erratic bad signals…
Driving me mad latest iOS iPad Pro…
Dubstation 2 is one culprit, though erratic?