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.

Unfiltered Audio Battalion Public Beta

124»

Comments

  • Another new beta is out:

    • You can now drag up/down and left/right on the BPM indicator in standalone mode to change the BPM.
    • Muting a voice and then manually triggering it will no longer produce a short noise burst.
    • "Reset all locks" will now remove the lock from the BPM indicator if it is locked.

    @EnvelopeFollower said:
    fullscreen please

    Is this for the iPhone version? The build yesterday should have fixed this by removing the white bar at the bottom, but let me know if it's not working on your device.

  • Definitely buying this one!

  • @trickyflemming said:
    Another new beta is out:

    • You can now drag up/down and left/right on the BPM indicator in standalone mode to change the BPM.
    • Muting a voice and then manually triggering it will no longer produce a short noise burst.
    • "Reset all locks" will now remove the lock from the BPM indicator if it is locked.

    @EnvelopeFollower said:
    fullscreen please

    Is this for the iPhone version? The build yesterday should have fixed this by removing the white bar at the bottom, but let me know if it's not working on your device.

    yes the iphone version.
    would be great to have the whole screen.

  • on my iphone12 only needlepoint and tails are fullscreen, standalone and auv3

  • @EnvelopeFollower said:
    on my iphone12 only needlepoint and tails are fullscreen, standalone and auv3

    edit: bassmint is also fullscreen

  • @trickyflemming @amusesmile
    Hi, I have a suggestion.

    The font of 8 variable(?) parameter names highlighted with yellow borders in the screenshot above is hard to read due to the color of the font itself. So they would be easier to read if they were the same color as the highlighted “1, 2, 3, 4”. (For example, in the case of the screenshot above, the legible font color is white.)

    [Note: I presume this issue is not specific to ‘TestFlight-Battalion for iPadOS/iOS’ only. So I presume this issue does not need to be fixed right away.]

    *
    By the way, thank you for the improvements in the ‘save preset dialog’ and ‘draggable BPM indicator in standalone Battalion’!

  • ^^^ Especially when small fonts are involved, contrast is key to legibility. It's a good suggestion to make all of the fonts white in this case.

  • @cramdog said:
    @trickyflemming @amusesmile
    Hi, I have a suggestion.

    The font of 8 variable(?) parameter names highlighted with yellow borders in the screenshot above is hard to read due to the color of the font itself. So they would be easier to read if they were the same color as the highlighted “1, 2, 3, 4”. (For example, in the case of the screenshot above, the legible font color is white.)

    [Note: I presume this issue is not specific to ‘TestFlight-Battalion for iPadOS/iOS’ only. So I presume this issue does not need to be fixed right away.]

    *
    By the way, thank you for the improvements in the ‘save preset dialog’ and ‘draggable BPM indicator in standalone Battalion’!

    I feel like that'd imply visually that those knobs control those parameters, which is true but it's also controlling different parameters on the non-selected voices. I do think from a UX/UI standpoint a visual difference is the right call but it could be less extreme to help with legibility. The user needs to know that it's not only moving those parameters. Originally there were no names at all but I like being able to see what's on the selected drum to jolt my memory.

  • @trickyflemming said:
    Another new beta is out:

    • You can now drag up/down and left/right on the BPM indicator in standalone mode to change the BPM.
    • Muting a voice and then manually triggering it will no longer produce a short noise burst.
    • "Reset all locks" will now remove the lock from the BPM indicator if it is locked.

    Thank you for the updates, you're doing an impressive job. 🤩 I wanted to bring up one bug, just in case you aren't already aware of it.

    On the ‘Performance’ page, the ‘undo’ function is not working properly for the randomize button.

    It works as intended for all manual tweaks. But, for example, if you hit the ‘Randomize’ button three times, the ‘undo’ will only revert the states to one step before those three actions.

    The only way to make ‘undo’ work for ‘Randomize’ is to tweak at least one knob after each execution of the ‘Randomize’ button.

  • edited April 16

    @amusesmile said:
    I feel like that'd imply visually that those knobs control those parameters, which is true but it's also controlling different parameters on the non-selected voices. I do think from a UX/UI standpoint a visual difference is the right call but it could be less extreme to help with legibility. The user needs to know that it's not only moving those parameters. Originally there were no names at all but I like being able to see what's on the selected drum to jolt my memory.

    @amusesmile
    Hi! Thanks for your reply and explanation.
    On second thought, I think my suggestion was indeed extreme in a bad way. Since my suggestion was based on the biased use of only one ENABLE switch is enabled for one specific instrument (= Other 7 ENABLE switches are disabled.) and reading 8 knob parameters with the one specific instrument selected. In other words, my suggestion was not user-friendly and could mislead users. I’m sorry.

  • @cramdog said:

    @amusesmile said:
    I feel like that'd imply visually that those knobs control those parameters, which is true but it's also controlling different parameters on the non-selected voices. I do think from a UX/UI standpoint a visual difference is the right call but it could be less extreme to help with legibility. The user needs to know that it's not only moving those parameters. Originally there were no names at all but I like being able to see what's on the selected drum to jolt my memory.

    @amusesmile
    Hi! Thanks for your reply and explanation.
    On second thought, I think my suggestion was indeed extreme in a bad way. Since my suggestion was based on the biased use of only one ENABLE switch is enabled for one specific instrument (= Other 7 ENABLE switches are disabled.) and reading 8 knob parameters with the one specific instrument selected. In other words, my suggestion was not user-friendly and could mislead users. I’m sorry.

    How about a colour closer to the dark grey / black end of the spectrum so that it stays obvious that it is something different. It just needs to have more of a contrast to the blue. With the current light greyness it is essentially invisible and almost impossible to read at smaller resolutions.

Sign In or Register to comment.