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.

Riffer - discuss

13»

Comments

  • @CracklePot, @Jumpercollins - I've just tried this myself and I can't reproduce the issue where the keyboard arrows disappear. Is this still happening for you? Any idea how to reproduce it?

  • @Michael
    Ok. After trying all the various scenarios, I think I found the glitch.
    It happens when you load up the same instance in an Audio input and Midi input.
    The Order you load them doesn’t seem to matter, but once both are loaded with the same instance, the KB for either/both will lose the arrows.
    New instances seem to work fine though, even with that broken one still loaded.

    So basically, the same instance loaded into Midi and Audio inputs will make the KB collapse arrows disappear, but only for that instance.

  • Ah! Thanks heaps, @CracklePot, I can reproduce that too. It's a Riffer bug (it's reporting specifically that it doesn't support fullscreen when in that state), but I've adjusted AB3 so that it's going to basically ignore those reports and always offer a keyboard toggle. If the AU really doesn't support fullscreen, it's just going to be centered in the space with black bars, so it's fine.

  • @Michael said:
    Ah! Thanks heaps, @CracklePot, I can reproduce that too. It's a Riffer bug (it's reporting specifically that it doesn't support fullscreen when in that state), but I've adjusted AB3 so that it's going to basically ignore those reports and always offer a keyboard toggle. If the AU really doesn't support fullscreen, it's just going to be centered in the space with black bars, so it's fine.

    Awesome. You are very welcome @Michael. Glad to be able to help. :)

  • Update is smooth.. Thanks..

Sign In or Register to comment.