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.
Auria fabfilter preset name changes?
Maybe I’m late on this and it’s been discussed but whenever I close a project and later open it the fabfilter preset name changes back to “default” from the preset I had used before closing. But I think it might be the name changing only and not the settings.
True? Bug?
Comments
@Jmcmillan The way Auria/Auria Pro handles presets (and definitely on the FabFilter plugs) is that user presets are saved in the grey Auria preset window and not within the plugins internal preset menu.
Visual Aid:
You can still use the internal plugin menu to choose the factory presets, etc but anytime you’re saving a custom preset in a project it has to be done via the Auria preset window next to the BYPASS button.
Hope that helps brother...
Thanks! But I’m not changing any settings, just using stock preset. Still need to save?
I have the same thing happening. I use one of the presets, then close out. When I come back the next day, it says "default" instead of the name of the preset I had selected. The good news is that it is changing the name only, all of the settings are just as I left them.
Yes it's a long standing bug, no-one seems to know if the issue is with FF or Auria.
Ah ok. I remember reading about it but wasn’t sure this was the same bug. Thanks!