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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Saving widgets

oscillotusoscillotus
edited June 2025 in Loopy Pro

Hey folks! I was wondering if it possible in Loopy Pro to save a group of widgets with their mapping so that I can load them up with a linked instrument or effect? I want to avoid remapping everything when I create a new template from scratch. If not, maybe there is a workaround or tips to make it faster?

Thanks in advance :)

Comments

  • espiegel123espiegel123

    @oscillotus said:
    Hey folks! I was wondering if it possible in Loopy Pro to save a group of widgets with their mapping so that I can load them up with a linked instrument or effect? I want to avoid remapping everything when I create a new template from scratch. If not, maybe there is a workaround or tips to make it faster?

    Thanks in advance :)

    I have an auv3 loopy instance into which I copy common widgets. You can copy project profiles to global profiles export and reverse the process.

  • oscillotusoscillotus

    Could you please give me more details about this? I understand a bit but just not enough to wrap my head around it...!

  • espiegel123espiegel123

    @oscillotus said:
    Could you please give me more details about this? I understand a bit but just not enough to wrap my head around it...!

    Which part is unclear?

  • oscillotusoscillotus

    @espiegel123 said:

    @oscillotus said:
    Could you please give me more details about this? I understand a bit but just not enough to wrap my head around it...!

    Which part is unclear?

    Let's say I have a LP project where I have a jAmp Percussive. I create a few slider widgets to control Mutate, Soul, Vocab, etc.

    I then create a Loopy Pro AUv3 inside the same project and copy the widgets into it.

    It is after that that I don't fully understand. The part with project profiles and global profiles.

  • espiegel123espiegel123
    edited June 2025

    @oscillotus said:

    @espiegel123 said:

    @oscillotus said:
    Could you please give me more details about this? I understand a bit but just not enough to wrap my head around it...!

    Which part is unclear?

    Let's say I have a LP project where I have a jAmp Percussive. I create a few slider widgets to control Mutate, Soul, Vocab, etc.

    I then create a Loopy Pro AUv3 inside the same project and copy the widgets into it.

    It is after that that I don't fully understand. The part with project profiles and global profiles.

    This may not work well for your use-case as references to plugins are project specific.

    I have loopy AU project called library.

    If I want to use it, I load it as an AU.

    I copy widgets from the main project and paste them into a page in the library project.

    Unfortunately, this won’t not work well for widgets that are tied to plugins because plugin references are project specific.

    —-
    On the control profile side, in control settings, you can duplicate a control profile to a new global profile. You can then open a project and duplicate the global profile to the project profiles. In some cases you need to re-select the targets.

    —
    This is an area where there is not a super efficient workflow.

  • oscillotusoscillotus

    Thanks @espiegel123, will have a look tonight. Maybe the best solution would be to create a sort of master template with everything I use most with a few widget groups per page and disable the plugins I won't need and move up the pages the widgets I want to use.

    Quick follow-up question. If I have a dial widget with 16 increments that select things in a plugin and want to have a second instance of the same plugin with its dial widget, is it possible to duplicate the widget and somehow tell it, "change only the plugin for each increment", or do I need to change each increment manually?

  • espiegel123espiegel123

    @oscillotus said:
    Thanks @espiegel123, will have a look tonight. Maybe the best solution would be to create a sort of master template with everything I use most with a few widget groups per page and disable the plugins I won't need and move up the pages the widgets I want to use.

    Quick follow-up question. If I have a dial widget with 16 increments that select things in a plugin and want to have a second instance of the same plugin with its dial widget, is it possible to duplicate the widget and somehow tell it, "change only the plugin for each increment", or do I need to change each increment manually?

    You will need to change each step

  • oscillotusoscillotus

    Aight! Thanks for taking the time @espiegel123, I appreciate :)

  • quadbusquadbus

    What's the benefit of this over copying the widget to a new page in the project?

  • oscillotusoscillotus

    @quadbus said:
    What's the benefit of this over copying the widget to a new page in the project?

    Sorry, I don't understand what you are meaning 😅

  • espiegel123espiegel123

    @oscillotus said:
    Aight! Thanks for taking the time @espiegel123, I appreciate :)

    Are you using the App Store version or the 2.0 beta? 2.0 handles destination preservation better than 1.x when copying/pasting between projects.

  • oscillotusoscillotus

    I'm on 2.0 beta. Will try it out tonight!

Sign In or Register to comment.