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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
No worries, here‘s another informative update (source is the elektronauts forum btw, devs seem more active there)
I have so much fun with Battalion rn. So easy to dial in interesting sounds. To automate parameters with other parameters. And the sequencer is just nuts. I feel like I finally found home with this plugin. I'm looking forward for the next update and for multi-out support in Loopy Pro.
One thing I have yet to figure out. I’m trying to get a true, non-repeating 50% probability on a continuous 1-step pattern in Battalion.
When I use the per-step PROB slider set to 50%, the resulting “random” sequence seems repetitive.
Does anyone know why the per-step PROB modulation seems to generate a fixed, repeating pattern? Is this by design?
@trickyflemming : Hey there... i just checked, and it appears that the FX sends are all prefader when using by itself and post for 2-8 when going indiv. That still causes a lot of issues if you try to live mix anything.
Can you please put in an option for ALL tracks to have pre or post fader FX sends? Pretty please?
It just occurred to me why more people are noticing this lately, and that's because of the Standalone behavior. So, the way this was designed is that PROB settings will always be the same on a given bar on a DAW's timeline. That way, if you render your song multiple times, the output is deterministic instead of being different each render. However, Standalone is essentially looping the same bar over and over again (since there's no timeline).
Definitely. It's burned me before as well. I'm wrapping up this engine update and then I will work on that. The patterns code is ready, but patterns won't be in this update as we're waiting on graphic design. I'll try to do the pre/post stuff in the patterns update while Papernoise is looking at everything.
The’re not very responsive at unfiltered audio.
In what way? I mean, they've engaged here a lot, they've acted on many suggestions here. Someone wrote a question here day before yesterday and the next day the dev responded in this thread. I'd say that's very responsive.
Sorry I meant by email. It took months for a reply. I answered to that and haven’t heard back since.
It was a nice reply though.
Not here to negatively talk bout devs
My apologies! It's just two of us at Unfiltered. We tend to answer emails in batches once or twice a week and occasionally things slip by. Things have been hectic lately (story time coming in about a month or so). The Battalion 1.1.4 beta is almost ready and should be up soon. Here's the current contents. The patterns code is pretty much ready to go on another branch, but we need to do graphic design on that:
1.1.4 (in progress)
Rad changes, thank ya kindly for the update! 🤷🏻♂️
No apologies needed.
I do hope still to get a reply to my email.
But if thats impossible it’s oke
You are awesome! Thank you very much for such nice products and for keeping in touch with your users
Thank you @trickyflemming for getting back and for the updates
Looks great! Love the creative range of sample engines. The app that keeps on giving. Look forward to testing it out 😀
@offbrands try changing the octave down one. With the AUM keyboard C-1 and C#-1 work but in midiSTEPS I had to use C-2 and C#-2.
I didn’t have any problems with crashing FWIW.
MIDI notes are not specific, they are relative. Middle C can be (usually) C3 or C4. That’s why “C0” is C-1 on the AUM keyboard but C-2 on midiSTEPS. It has to do with what manufacturers defined middle C back in the early days of MIDI. This had to do with a typical 88 key piano versus shorter synth keyboards which were around 60 keys.
(From Google) Yamaha MIDI middle C is C3, whereas the standard scientific pitch is C4. Both systems refer to the same MIDI note number 60, but Yamaha uses C3 and other manufacturers/software (like Roland) use C4. The difference stems from different octave numbering conventions used by various companies.
@anickt how do you change the octave down from Note 0? I also get these crashes. It is absolutely a bug.
You do it in whatever app you are using to send the MIDI notes. If I just had the C#-2 step it would advance every time it hit that step.
I’m using Loopy Pro to send Note 0. I don’t think it’s possible to change the octave. FWIW I just tried sending C-2 in Drambo and Battalion can’t handle it. It doesn’t crash, just glitches out for a while. Ah, D#-2 crashes it. Yeah, this is a bug.
IDK - I’m on an A16 iPad with iPadOS 26.1 with no crashing. Good luck!
And @meek3 ?
Here also an extra bump for preset change fix.
I just tried this in Drambo and changing presets with those two notes works just fine, so it looks like there's another factor at play.