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 - effects no longer visible in LFO destinations?
Can someone see if they can replicate an issue. I’m loading mLFO into the midi slot but none of my effects are showing up in the destinations as it has in the past. I even opened up old previous projects and it works fine there! But I can’t do this when creating a new project. I’ve tried with over a dozen effects and none of them show up, so it’s not an issue with the effects.
Anyone else had this issue or it just me?
Also to add, I tried restarting my iPad as well and this didn’t solve the issue. Don’t want to delete and reinstall for fear of losing all of my saved templates and projects.
Comments
@j_liljedahl any recommendations?
Have you tried rebooting?
It might be helpful if you posted screenshots or a video demonstrating what you see.
@HotStrange : are you looking in the right place? If you are using midi to control
Effect parameters you send the midi to AUM’s midi control not the effects themselves. Many effects don’t take midi input directly. But all that have AUv3 parameters to control will show up ⬆️ n the midi control configuration. But might not show up as midi destinations.
Can’t test extensively at moment but know that Mlfo still isn’t working after update in AUM. All connections look ok that were working on old project but nothing happens. Have moved over to MMM by gs dsp which seems ok
FWIW I’ve just tried mLFO and Rozeta and mapped them to a gain node in AUM, and the knob (the exposed control next to the node) turns itself with both.
I’ve connected the LFO to the control by tapping the output node of the channel, then the control icon, set the MIDI source (blue text top right, then picked the gain node and then gain control, set it to match the LFO’s channel and CC number.
So, not an exhaustive test, but both LFO apps seem to be able to twiddle AUM’s knobs.
My bad, mlfo is working..but still not on old project…the out section goes up to 16 but seems to stop working on any number above 2..anyone know the theory on this?
I was gonna say I use mLFO a lot it was fine a day or two ago.
Start with the old turn off device and turn back on.
@espiegel123 @Poppadocrock @Zerozerozero @bygjohn thsnka for the replies!
It seems to be working now. I turned my iPad off for a little while and back on, also deleted and reinstalled mLFO. Not sure which of those things worked but as soon as I opened AUM it was all good. My old projects which used mLFO are all there but mLFO is invalidated upon reloading the template so it may be an issue with that app. Will contact the dev about it.
Sorry, yeah I rebooted and deleted and reinstalled mLFO and it’s working now. I was using effects that I know show up in the destinations from past projects and they wouldn’t be there or they wouldn’t connect. Still have that issue with old saved templates but I can use it on new projects for now.
Not sure. When I load mLFO on my old projects it crashes immediately, goes red and says invalidated. And when I click on it to reload, it reloads but will no longer send the midi output. Not sure if it’s an issue with state saving or what. Probably gonna contact the dev about it. It works fine on new projects but not old ones.
mLFO probably had an update and forgot to handle backwards compatibility when loading state saved with an older version.
Thanks for replying. That seems to be the case for sure. Haven’t had a chance to try it again yet but AUM seems to be working fine as always.