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.
I broke iFretless Bass somehow, anyone seen this? ((not) FIXED)
Okay, here’s the sequence of events:
- AUM session contains iFretless Bass and is loaded and everything is working
- Go to Files app, duplicate the AUM session file (AUM is running in the background)
- Open the duplicate session file, which opens it in AUM, replacing the running session
- IFretless Bass refuses to load, channel produces feedback unless muted
- Creating a new session in AUM, iFretless Bass still refuses to load
This condition has survived a reboot, the installation of iOS 17.3, and a deletion and re-installation of iFretless Bass. Other AUs load fine as far as I can tell. Standalone iFretless runs fine. iFretless also refuses to load in Logic Pro now with similar behavior.
Anyone run in to this? Ideas on how to fix it?
ETA: changing sample rate setting to 48kHz seemed to cheer it up.
ETA: new version of the app breaks AUv3 entirely, at least for me.
Comments
Best to contact the devs. Haven't tried with the bass app, but ifretless guitar is not loading for me as an auv3 in aum. So far suggestions to delete, reinstall etc have not worked, but they're on it.
Good to know, and that’s a good suggestion. I will reach out to the developer. I feel like there’s a corrupted plist somewhere, but I can’t imagine where.
Oh, huh, I got it back. I looked at the settings in AUM, saw that the session was requesting 96kHz sample rate but getting 48kHz, set the preferred rate to 48, saved the session, re-installed iFretless, and it was able to load. After that it was also again able to load in Logic. So maybe something was triggering a sample rate mismatch that was causing the crash? Anyway @Gavinski you might check your preferred sample rate in AUM and see if changing the value does anything for you.
Ok fixed, thanks, Yes, for whatever reason, my sample rate was set at 44.1, changed it just now to 48 and the app loaded fine first try. I’ve informed the dev too in case that helps others, nice one.
Strange little bug. The fact that it triggered the inability for the plugin to load in Logic due to a setting in AUM has me scratching my head. Maybe it's an OS bug?
And another update. Mani Consulting released a new version today to address an "AUv3 bug on iOS 17", which I assume is the behavior I saw yesterday. Unfortunately this new version has killed AUv3 functionality entirely, at least for me on my iPad.
Not sure if this helps, but the sample rate and buffer size are system parameters, because all audio apps have to use the same settings. Sometimes, like when you first load AUM, an app can change this system setting to another supported value. That then becomes the default setting, at least until an iPad restart. So it is possible that AUM enabled a sample rate that was incompatible with iFretless Bass, and caused Logic to inherit this setting.
Quite possible! It’s strange, because the whole time AUM was reporting that the running sample rate was 48kHz, just that the “preferred” rate was 96k. But yeah, something about the mismatch between preferred and running rate made it mad. Buffer size selection didn’t make any difference.
Here’s a fun wrinkle: I noticed when the iPad is docked with a Magic Keyboard, the plugin fails. Undock the iPad and the plugin loads right away, no AU host restart needed or anything. Doesn’t matter if power is plugged in or not. So for kicks, I paired a Bluetooth keyboard, and it’s the same effect. Apparently it is the presence of a keyboard that trips it up somehow? Anyway I will report this to the vendor; I just add it here in case someone is having similar experiences.
Ifretlass bass fails inside both AUM and Logic (at 48k) for me on my m1 iPad Pro running the latest iOS. It seems to load fine as a stand-alone app.
It’s working fine for me on a Pro M2 11”, 17.2. But I don’t have an external keyboard.
The keyboard thing reminds me of the problem identified a while back with some magnetic cases that messed with the audio system.
Haha, I think maybe Apple's devices have gotten a little too "Magical". This one definitely seems tied to the keyboard but I'm curious about what @Tovokas is experiencing. @Tovokas, do you have a keyboard connected? Some other Bluetooth device? USB hub?