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.
Sharing Control Profiles across projects
In Loopy Pro I have some bindings to a computer keyboard (created via midi learn) that I'd like to share across projects.
To do so, I created a copy of a project specific profile (where I have the bindings set up) as a global profile, then from the other project from which I'd also like to leverage these bindings, I located the newly created global profile and selected the radio button next to it.
These bindings are to on-screen buttons.
Following the steps I mention, above, seems to work, but should bindings to on-screen buttons be leveraged from project profiles, not global ones?
So should I copy that global profile back into a project profile.
If so, how best to accomplish this?
(and if it works via the global profile reference, why should I do this last step of copying the global profile back into the project profile?)
Thanks
Comments
Global profiles aren't good to use with widgets because the specific references to those widgets get lost or jumbled between projects. Widgets you add to a project aren't global entities, they only exist inside the project, so Loopy doesn't have any way to know which widgets to bind to across projects.
If you do a lot of that kind of thing, then you probably should use local profiles, then leverage templates to make new projects, or just copy the project and work from there.
You're on the right track for copying local profiles between projects. Duplicate the local profile to global profiles with the copy at the top right when you have the profile open. Then open the new project and go to the edit screen of the global profile and use the same icon to duplicate to local profiles. You may need to edit references to widgets since it's unpredictable whether they'll be right or not.
And after copying the global profile to project profile, turn off the global profile.
Good catch.
Thanks. After the last step of saving the global profile to a project profile (in the target project to which I wanted to move the original profile from the other project), when I went to turn off the global profile, it was already off (ie: radio button deselected). Not sure if that's expected, but just wanted to let you know since @espiegel123's last comment seem to imply that had to be done manually.
Also, as a final step any reason I shouldn't just delete the global profile when I'm done (if the only reason I had to create the global profile in the first place was as an intermediate step to creating the new project profile?).
Thanks!
@danm: if you don’t need the global profile, there is no need to keep it.