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.

Is there an AUv3 preset manager?

2»

Comments

  • espiegel123espiegel123

    @ttk said:

    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    I must not be understanding the picture you posted. The picture you post also looks like each “super preset” needs to be manually configured, too. No?

  • wimwim
    edited April 17

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

  • uncledaveuncledave

    @wim said:

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

    If you had the same dozen or so items, requiring to be sent in various MIDI messages, a script configured by a table would make this easier. Once the script is written, a new preset would just require adding some entries to the table. This would easier than adding another new button, and adding the required actions to it.

  • wimwim
    edited April 18

    @uncledave said:

    @wim said:

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

    If you had the same dozen or so items, requiring to be sent in various MIDI messages, a script configured by a table would make this easier. Once the script is written, a new preset would just require adding some entries to the table. This would easier than adding another new button, and adding the required actions to it.

    The OP already said they hope the solution won't involve scripting.

    (I like scripting and I wouldn't want to do it that way. I don't see it as easier at all. 🤷🏼‍♂️)

  • espiegel123espiegel123

    @uncledave said:

    @wim said:

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

    If you had the same dozen or so items, requiring to be sent in various MIDI messages, a script configured by a table would make this easier. Once the script is written, a new preset would just require adding some entries to the table. This would easier than adding another new button, and adding the required actions to it.

    I have a few buttons that are essentially macros that make things less tedious.

  • Tones4ChristTones4Christ

    @espiegel123 said:
    @ttk : as an example. Here are buttons in my primary Loopy Pro guitar pedalboard project.

    Each of the buttons on the page, has several actions needed for a tone setup. They set the presets used by various AUv3, set some effects parameters and send some send MIDI to external devices.

    Here are the actions in a couple of those buttons -- they can have as many actions as you need. Actions can send MIDI, select presets, set effect parameters, and more.


    Here you see that the buttons have been set up to be triggered by incoming PC messages:


    This seems to be along the lines of what you have described and illustrated, no?

    Thanks for posting these pics and the explanation. I've been struggling with building my own Loopy interface forums pedalboard and seeing it this way helps a lot. I guess I might have been making it harder than it should be.

  • TentypeTentype

    @ttk said:

    @espiegel123 said:
    @ttk : as an example. Here are buttons in my primary Loopy Pro guitar pedalboard project.

    Each of the buttons on the page, has several actions needed for a tone setup. They set the presets used by various AUv3, set some effects parameters and send some send MIDI to external devices.

    Here are the actions in a couple of those buttons -- they can have as many actions as you need. Actions can send MIDI, select presets, set effect parameters, and more.


    Here you see that the buttons have been set up to be triggered by incoming PC messages:


    This seems to be along the lines of what you have described and illustrated, no?

    If not, what am I not understanding?

    First of all, Thanks for the detailed explanation, i really apreciate it.

    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    No app will guess the settings you want in your 50 custom presets unfortunately. So you're stuck making 50 custom solutions.

    Fortunately any software you use should allow you to build the first preset and copy /paste it and tweak it as needed which makes the work less.

    Again, I'd use loopy for this as @espiegel123 suggested.

    Making preset 1 takes the longest while you set up a button with all the incoming midi and outgoing actions. Get it setup and working perfectly. Then just copy/paste it and edit it for the next presets. 50 is a lot, but I've done worse for some performance templates. If you make a change you just have to edit the affected presets.

    It would be the same in any software or hardware macro system.

  • uncledaveuncledave

    @wim said:

    @uncledave said:

    @wim said:

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

    If you had the same dozen or so items, requiring to be sent in various MIDI messages, a script configured by a table would make this easier. Once the script is written, a new preset would just require adding some entries to the table. This would easier than adding another new button, and adding the required actions to it.

    The OP already said they hope the solution won't involve scripting.

    I know, but the suggested option of building each event separately using a GUI seems tedious. @Tentype has suggested that an initial button could be copied and adjusted to send the desired PCs and CCs for a new preset. That sounds a lot more reasonable than building each preset from scratch.

    (I like scripting and I wouldn't want to do it that way. I don't see it as easier at all. 🤷🏼‍♂️)

    Creating the initial script would be a bit difficult, but configuring the events would be very easy.

  • ttkttk

    @espiegel123 said:

    @ttk said:

    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    I must not be understanding the picture you posted. The picture you post also looks like each “super preset” needs to be manually configured, too. No?

    @wim said:

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

    @Tentype said:

    @ttk said:

    @espiegel123 said:
    @ttk : as an example. Here are buttons in my primary Loopy Pro guitar pedalboard project.

    Each of the buttons on the page, has several actions needed for a tone setup. They set the presets used by various AUv3, set some effects parameters and send some send MIDI to external devices.

    Here are the actions in a couple of those buttons -- they can have as many actions as you need. Actions can send MIDI, select presets, set effect parameters, and more.


    Here you see that the buttons have been set up to be triggered by incoming PC messages:


    This seems to be along the lines of what you have described and illustrated, no?

    If not, what am I not understanding?

    First of all, Thanks for the detailed explanation, i really apreciate it.

    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    No app will guess the settings you want in your 50 custom presets unfortunately. So you're stuck making 50 custom solutions.

    Fortunately any software you use should allow you to build the first preset and copy /paste it and tweak it as needed which makes the work less.

    Again, I'd use loopy for this as @espiegel123 suggested.

    Making preset 1 takes the longest while you set up a button with all the incoming midi and outgoing actions. Get it setup and working perfectly. Then just copy/paste it and edit it for the next presets. 50 is a lot, but I've done worse for some performance templates. If you make a change you just have to edit the affected presets.

    It would be the same in any software or hardware macro system.

    Thanks for the input guys, in fact all of made me define more precisely what i'm looking for.

    There are two answers to your question -> hence making the worflow easier

    1st : is the capability to copy-paste a button, as @Tentype says.
    2nd, is the functionality to remap a midi PC to another channel.

    In fact I'm looking for a blend between Mid Messenger and MidiFlow
    Do you know those apps?

    I'll try to show you what I'm expecting based on the Midi Messenger app.

    1) Creation of a preset wich will serve the basis of everything

    2) However instead of simply sending a fixed PC, I need the functionality to remap the PC to another channel, like in MidiFlow

    That way, the incoming Pc from my footswitch is sent directly to the apps to change their presets, no need to configure it for each Meta preset

    2) Save this preset 50 times

    3) when needed go to a particular preset and change a few values

    I hope it makes sense.

    Thanks for your time and answers anyway, I realise I'm asking for the impossible as it seems here:
    https://forum.audiob.us/discussion/56528/like-midiflow-but-auv3

  • ttkttk

    @uncledave said:

    @wim said:

    @uncledave said:

    @wim said:

    @ttk said:
    Now, for the proposed solution : so, it would mean creating as many buttons/controls as I have presets (~50)
    Then,I'll have to go through each one of them to configure their midi actions and do the midi learn.

    Ditto if i want to change something.

    Thanks for the idea, but that's quite a tedious workflow

    How could it be less tedious in any app? The same things need to be configured somehow no matter what app you would use, don't they?

    I'm not trying to be argumentative, I'm trying to understand what I'm missing.

    If you had the same dozen or so items, requiring to be sent in various MIDI messages, a script configured by a table would make this easier. Once the script is written, a new preset would just require adding some entries to the table. This would easier than adding another new button, and adding the required actions to it.

    The OP already said they hope the solution won't involve scripting.

    I know, but the suggested option of building each event separately using a GUI seems tedious. @Tentype has suggested that an initial button could be copied and adjusted to send the desired PCs and CCs for a new preset. That sounds a lot more reasonable than building each preset from scratch.

    (I like scripting and I wouldn't want to do it that way. I don't see it as easier at all. 🤷🏼‍♂️)

    Creating the initial script would be a bit difficult, but configuring the events would be very easy.

    @wim , @uncledave

    All right if there is not such an app, I'm listening.

    What scipt-based solution do you have in mind?

  • wimwim
    edited April 21

    @ttk said:
    What scipt-based solution do you have in mind?

    I don't have a script based solution in mind. I wouldn't use a script for something like this.

    Apologies in advance - I only skimmed your more detailed post about what you're after. My only input is perhaps you could run the output through mfxStrip to change the channel of the PC messages if that's all you end up needing to do. There's an AUv3 parameter to set the outgoing channel.

    Also ... why not just use MIDI Flow if it could be made to do what you need?

  • TentypeTentype

    @ttk It seems like what you're suggesting is maybe possible, but so much simpler to use just Loopy if you're already using Loopy. You don't need a second program.

    1. In Loopy, make a button. On the button add the PRESS action "Select audio unit preset" and select the audio unit (like Turnado) and select the preset you want.
    2. Add as many presets as you want as Press actions on that one button. Test the button to make sure it changes the presets the way you want.
    3. Then in Loopy choose midi learn. Select the button you just made, and click the pedal on your pedalboard that you want to activate that button.
    4. Copy/paste the button. Change the presets and the midi mapping.
    5. Profit

    I'm not any help with coding or midi rerouting on iOS, so I'll leave you to it if you're committed to using a different solution. 🙏🏽

  • uncledaveuncledave

    @ttk . I have some ideas, but I don't understand the need to remap the MIDI channel for PC messages. You have an external controller that sends PCs on some channel. That controller's MIDI is routed only to the script or buttons managing the "presets". The preset manager sends PCs on specific channels that are routed to respective apps, to trigger loading their presets. Where does the need for remapping PC channels come in?

Sign In or Register to comment.

© Vanilla Keystone Theme 2024