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.

Call for testers: Audiobus MIDI learn

2»

Comments

  • Sent a request yesterday but no reply as of yet. Are the TestFlight invites automated?

  • @Carnbot said:
    So currently the only way to use an app for the midi learn source is to use virtual midi from the sending app, but you can't send midi via an Audiobus midi lane? I've been trying this but no luck in case I've done it wrong :)

    For now, yes: you need to select the third-party's virtual MIDI out port. More sophisticated routing coming soon.

    @Korakios said:
    Will midi learn (for AU parameters) work for hardware controllers only or midi apps are supported too?

    Virtual MIDI works too (as described immediately above); more to come.

  • @Empolo said:
    Sent a request yesterday but no reply as of yet. Are the TestFlight invites automated?

    Nope - sent out now.

  • edited December 2018
    The user and all related content has been deleted.
  • edited December 2018
    The user and all related content has been deleted.
  • Couple simple questions...

    How do I restart tutorial for midi learn, it only showed me the play button step.

    How do I find & bind AUv3 parameters?

    Cheers

  • @rs2000 said:
    Regarding Pick-up mode vs value jumps:
    What type of relative/incremental MIDI CC is currently supported?

    1000% agree... You MUST support at least 63/65 rel midi or it’s pointless. Fixed midi mapping in software is stupid and just leads to jumping parameters or other poor UX...

  • @MonkeyDrummer said:

    @rs2000 said:
    Regarding Pick-up mode vs value jumps:
    What type of relative/incremental MIDI CC is currently supported?

    1000% agree... You MUST support at least 63/65 rel midi or it’s pointless. Fixed midi mapping in software is stupid and just leads to jumping parameters or other poor UX...

    Strong words :lol: Yeah that's coming, next update in a couple weeks.

  • @SpookyZoo said:
    Couple simple questions...

    How do I restart tutorial for midi learn, it only showed me the play button step.

    If you mean the little intro screen, that goes away once you've "bought" the IAP. There's not really a tutorial though, just a brief pointer. I'll update the manual shortly.

    How do I find & bind AUv3 parameters?

    Tap the AU icon on the audio or MIDI screen, then you'll see a parameter option.

  • @Michael said:

    @SpookyZoo said:
    Couple simple questions...

    How do I restart tutorial for midi learn, it only showed me the play button step.

    If you mean the little intro screen, that goes away once you've "bought" the IAP. There's not really a tutorial though, just a brief pointer. I'll update the manual shortly.

    How do I find & bind AUv3 parameters?

    Tap the AU icon on the audio or MIDI screen, then you'll see a parameter option.

    Cheers Michael.

  • @MonkeyDrummer said:

    @rs2000 said:
    Regarding Pick-up mode vs value jumps:
    What type of relative/incremental MIDI CC is currently supported?

    1000% agree... You MUST support at least 63/65 rel midi or it’s pointless. Fixed midi mapping in software is stupid and just leads to jumping parameters or other poor UX...

    It's fair to grant Michael enough time to add the MIDI CC feature, including relative control.
    It's not only about the control messages but much more about communicating with all the eccentric iOS apps in ways that are all but transparent.
    Everybody who has tried to map an endless controller with visual feedback on classic desktop software knows what I'm talking about. Audiobus has to take the role of an advanced DAW (like Ableton Live) that wraps functionality around plugins that don't support the feature themselves.
    I think that relative and mappable MIDI controller support should be in our DAWs and IAA and AUv3 apps in the first place, but not every developer agrees on which "common iPad usage scenario" to support.

  • Awesome! Update just dropped on the AppStore!

  • @Michael said:
    Hehe, that's great, @lukesleepwalker =)

    That's a good idea - I'll do it, but not in this initial release; until then, you could add a binding within each preset which is the same trigger, which just loads the next one in the queue.

    @lukesleepwalker said:
    Another present under the tree this morning!

    @Michael The tip you mentioned above about including the same MIDI binding in each preset works great. You might put something in the documentation about that feature as I suspect others will be looking for one-button preset switching.

    How did you get it to work? I assigned the same midi binding to each preset but it doesn’t do anything.

Sign In or Register to comment.