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.
Bug? Loopy pro Auv3 not remembering widget settings after project close
Hi guys. I’ve noticed my widget control surfaces in loopy aren’t saving their parameter settings after I close a project in Logic for ipad. Is this a known issue? And is it Logic specific / are there daws where it saves parameter states properly?
I realize I can just save a loopy project to save the widget states but it would be really helpful if this could be patched. Is there a specific page for bug reports?
Comments
Can you post screenshots showing what you mean? What actions to the widgets perform?
If the widgets only send midi, see this wiki article: https://wiki.loopypro.com/Tech_Note:_Persistent_Send_MIDI_Widgets
Thanks for the reply. So from what i understand it’s like that by design. I have dial widgets sending midi cc from loopy loaded as an Auv3.
I still think an option to remember their positions should be included, because if we use it to control some other AuV3 it will set every parameter being controlled in that AuV3 to zero which is a bit of a pain. Same thing if we use it to control some hardware synth. It doesn't make any sense for the midi cc widgets to reset. Imagine if this happened on a PC daw, you save your project after some tweaks and reload it to find all the knobs in a rack set to zero. This has no practical value whatsoever
Sorry, deleted double post, i keep pressing the quote button instead of edit 🙃
The method in the above tech note will work for knobs and buttons too. Just add a duplicate control and add a trigger widget on the original with the dummy widget as the target. Then add a project wide follow action to trigger the original widget on project load.
I understand your point and the current situation is that you can use stepped dials and radio buttons to accomplish what you want.
It wouldn’t be a minor change to have widgets not get their value from the state of what they control. (Loopy has no way of knowing what state the thing you sent midi to is in).
Thank you for the help, I’ll give this a try.
Regarding loopy remembering the settings. I wasn't implying that Loopy read the plugin parameters, only that it remembers what state the widgets in Loopy were in when the project was closed, even if its not midi mapped to any plugin. Kind of like saving a loopy project, except now it also saves the positions of the midi widgets
@espiegel123
Isn’t the method I described above a bit more generalized and simpler? I’ll admit I’ve only used it a few times and have only lightly tested, but so far it’s seemed to work for me. I could well be overlooking something though.
That works too. I am not sure that either is more generalizable or simpler than the other but maybe I am overlooking something.
I understand what you want. I am saying it isn’t as small a change as it might seem.
Knobs and sliders don’t remember their positions at all. They reflect the state of the thing they control. I understand that it would be desirable in some cases if they did. But it isn’t a trivial change. It can be fairly simply worked around; so other functionality may take higher priority.