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.

MIDIx - New app by Fingerlab - Open for Beta-test

13»

Comments

  • relpotrelpot

    @egobeats said:
    Every once in awhile a cc just stops moving. I haven't been able to figure it out. Absolutely love the app though. It might be my favorite cc app, along with polybud

    Thanks for the feedback ! I will check this issue "Every once in awhile a cc just stops moving", and hopefully fix it for the next update.

  • relpotrelpot
    edited July 2

    I just want to let you know that a new MIDIx update v2.0 is available for testing on TestFlight:
    https://testflight.apple.com/join/meu4rHxC
    It should be available on the AppStore in a week.

    Here's the list of changes:
    • Added Audio Unit parameters support
    • Added MIDI Mappings
    • Added Notes polyphony settings
    • Added Notes custom mode (select the notes you want)
    • Added precision mode for Faders by sliding your finger on the fader's side
    • Added double-tap on a Fader to reset to default value
    • Minor bugs fix

  • Robin2Robin2

    @relpot said:
    I just want to let you know that a new MIDIx update v2.0 is available for testing on TestFlight:
    https://testflight.apple.com/join/meu4rHxC
    It should be available on the AppStore in a week.

    Here's the list of changes:
    • Added Audio Unit parameters support
    • Added MIDI Mappings
    • Added Notes polyphony settings
    • Added Notes custom mode (select the notes you want)
    • Added precision mode for Faders by sliding your finger on the fader's side
    • Added double-tap on a Fader to reset to default value
    • Minor bugs fix

    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

  • GavinskiGavinski

    @Robin2 said:

    @relpot said:
    I just want to let you know that a new MIDIx update v2.0 is available for testing on TestFlight:
    https://testflight.apple.com/join/meu4rHxC
    It should be available on the AppStore in a week.

    Here's the list of changes:
    • Added Audio Unit parameters support
    • Added MIDI Mappings
    • Added Notes polyphony settings
    • Added Notes custom mode (select the notes you want)
    • Added precision mode for Faders by sliding your finger on the fader's side
    • Added double-tap on a Fader to reset to default value
    • Minor bugs fix

    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

  • relpotrelpot

    @Gavinski said:

    @Robin2 said:
    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    Yes I confirm, I have made the parameters of MIDIx available for automation as AU parameters, as it's not possible to access other plugins AU parameters.

  • Robin2Robin2

    @Gavinski said:

    @Robin2 said:

    @relpot said:
    I just want to let you know that a new MIDIx update v2.0 is available for testing on TestFlight:
    https://testflight.apple.com/join/meu4rHxC
    It should be available on the AppStore in a week.

    Here's the list of changes:
    • Added Audio Unit parameters support
    • Added MIDI Mappings
    • Added Notes polyphony settings
    • Added Notes custom mode (select the notes you want)
    • Added precision mode for Faders by sliding your finger on the fader's side
    • Added double-tap on a Fader to reset to default value
    • Minor bugs fix

    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    @relpot said:

    @Gavinski said:

    @Robin2 said:
    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    Yes I confirm, I have made the parameters of MIDIx available for automation as AU parameters, as it's not possible to access other plugins AU parameters.

    Thanks both, thought that would be it. I assumed the first option wouldn’t be technically possible but one can dream…setting up cc numbers is such a pain in the arse!

  • GavinskiGavinski

    @Robin2 said:

    @Gavinski said:

    @Robin2 said:

    @relpot said:
    I just want to let you know that a new MIDIx update v2.0 is available for testing on TestFlight:
    https://testflight.apple.com/join/meu4rHxC
    It should be available on the AppStore in a week.

    Here's the list of changes:
    • Added Audio Unit parameters support
    • Added MIDI Mappings
    • Added Notes polyphony settings
    • Added Notes custom mode (select the notes you want)
    • Added precision mode for Faders by sliding your finger on the fader's side
    • Added double-tap on a Fader to reset to default value
    • Minor bugs fix

    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    @relpot said:

    @Gavinski said:

    @Robin2 said:
    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    Yes I confirm, I have made the parameters of MIDIx available for automation as AU parameters, as it's not possible to access other plugins AU parameters.

    Thanks both, thought that would be it. I assumed the first option wouldn’t be technically possible but one can dream…setting up cc numbers is such a pain in the arse!

    Not if you use AUM midi control finder. Search the online AUM manual for those words if you're not familiar with it. Gamechanger!

  • Robin2Robin2

    @Gavinski said:

    @Robin2 said:

    @Gavinski said:

    @Robin2 said:

    @relpot said:
    I just want to let you know that a new MIDIx update v2.0 is available for testing on TestFlight:
    https://testflight.apple.com/join/meu4rHxC
    It should be available on the AppStore in a week.

    Here's the list of changes:
    • Added Audio Unit parameters support
    • Added MIDI Mappings
    • Added Notes polyphony settings
    • Added Notes custom mode (select the notes you want)
    • Added precision mode for Faders by sliding your finger on the fader's side
    • Added double-tap on a Fader to reset to default value
    • Minor bugs fix

    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    @relpot said:

    @Gavinski said:

    @Robin2 said:
    Apologies for my lack of understanding @relpot, but when you say you’ve added AU parameters support, do you mean that it’s now possible to select the visible AU parameters of other plugins as targets rather than having to assign cc numbers to them first? (That would make things so much easier to set up!).

    Or do you mean that you’ve made the parameters of MIDIx available for automation as AU parameters?

    Must be the latter, I think I get what you're asking for with the former, if I do, that's just not possible, I think.

    Yes I confirm, I have made the parameters of MIDIx available for automation as AU parameters, as it's not possible to access other plugins AU parameters.

    Thanks both, thought that would be it. I assumed the first option wouldn’t be technically possible but one can dream…setting up cc numbers is such a pain in the arse!

    Not if you use AUM midi control finder. Search the online AUM manual for those words if you're not familiar with it. Gamechanger!

    Thanks, I’ll definitely look into that, not a big AUM user but I do have it. Cheers.

Sign In or Register to comment.