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.

Addictive Pro Arp Lock

It doesn't work when using global randomiser on Arp page. Anyone else finding this ?

EDITED

Comments

  • Lots of people reporting this "problem"
    There's about 3 threads it's been mentioned in, fortunately the solution is simple
    Just change "trigger" on the arp page (in "common") from "standard" to "hold keys"

    Not the clearest bit of design though.

  • Thanks but that's hold not lock. I'd already figured the hold thing out.

    When you are using the randomizers you should be able to "lock" certain pages so that they do not respond to the randomisation. On Addictive this function is called "fix". Here it appears to be called "lock". I have tested this with the reverb and that is how it functions there.

  • edited September 2016

    On another note, I don't think the randomiser is working properly but it might be my misunderstanding of the design compared to addictive. The global randomiser, top right, should work globally whichever page you are on. In the the arp page this is certainly not the case. It just changes the arps, regardless of lock status.

  • Ok....so it appears the only page where arp lock doesn't work is when you use the global randomiser (top right ) actually on the arp page itself . Is this a bug ?

Sign In or Register to comment.