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.
Loopy Pro Update Version 1.0.18
The user and all related content has been deleted.
Comments
I have used “Cantabile Performer” (PC) and “Camelot Pro” (iPad) for performing live. Both support backing tracks (linear), plugins (instruments & FX) and setup changes (“Scenes” in Camelot; “States” in Cantabile). Camelot features a PDF reader and Cantabile uses Notes to show Chords/Lyrics. Plugin changes can be changed on the fly, but the backing track remains linear. Can Loopy Pro match any of these two programs? I have very limited knowledge of Loopy Pro, but it looks like I could slice up my backing track and make “Song Sections” that could be manually or automatically selected. Is this correct? Thank you!
@Michael I've got a bug in this release: one-shots in the AU that have midi-mapping aren't firing. Just tried it inside a fresh project - M1 iPad Pro, NS2 and latest Loopy...
Some more info on this. Tried the same thing in Cubasis, and the mapping works there. Here's a video of me trying it in NS2...
https://streamable.com/r4p52k
It's not just newly created projects either, all my existing and in-progress projects with Loopy Pro in NS2 have stopped working.
Not that it should matter: does it make a difference if the host clock is running or what Loopy’s sync setting is? In NS2, trigging a loop is working?
Did you Midi learn the note or enter it manually? If manually then perhaps the octave is off due to differences in octave naming between apps / hardware.
if you Midi learned it, then what is the diction type. Sometimes things are detected as Hold when you really need it to be On or On/Off.
Could the clip be set to “hold to play”?
Where is the note coming from? Hardware or another app? If another app, is Background Audio turned on in Loopy? [edit nvm. I missed that this is in th AU version]
Could be a routing issue as well. Screenshots or a video of your process might be helpful if none of the above isolates it.
I can definitely reproduce that! Looking into it now, @FastGhost
I have tried to replicate the problem. Everything works fine here.
I do notice what seems like a bug. Unless a one-shot completes playing, the initial transient is lost when retriggering the sample.
Okay, totally my bad. Fix is en route. Wish I could use x.x.x.x version numbers, haha. Here comes 1.0.20.
Okay, it’s now available @FastGhost
Truly incredible service, thanks @Michael, you’re the best.
☺️
That should be fixed too
I had a project where by swiping up I could arm a clip for recording. After the latest update this makes Loopy crash. Already deleted and reinstalled Loopy but when I go into clip settings, reorder them and attach the swipe up/down or long press to record it again will crash Loopy.
Restarted my iPad, fired up loopy and did not make any changes at all. Standard clip settings where swiping down should stop recording bit it will crash. Removing that action from swiping down is oké. It seems to me that the action of Record is giving some issues.
Does this happen in a new default project or only a particular one?
Hi @Michael , you mentioned in the past that reversing loops would be in the next update. Just wondering, is this still likely to happen some time soon?
Dammit @Michael, I hate to be that guy, but it's still doing the same thing:
https://streamable.com/vuaw77
I bought Loopy Pro on release but have been waiting for the reverse feature to be implemented before jumping in and learning the software properly. Totally my choice to do it this way but definitely hoping it happens within the first year. I realise of course that you have many competing priorities.
That’s interesting! Would you mind sending me your crash logs and your project? (https://loopypro.com/manual/#reporting-crashes)
Whoa! I just tried the exact same steps and it’s working perfectly here… if you open up the system settings screen, does it definitely say 1.0.20 at the bottom?
Yes, absolutely – I’ve already started it, it’s just been waylaid by a bunch of bug fix updates and I’m also splitting my time between that and my work on the Mac/VST version. But it won’t be long.
Shame on my part…..instead of choosing an action like record or stop I had toggle switched on. Seems like that caused the issue, my bad!
Ooh no, 1.0.19! Must have been a lag making it all the way to the UK App Store! Can confirm that .20 is working here too and that you’re still the best.
No no, definitely my bad – it certainly shouldn’t be crashing. If you don’t mind, I’d definitely like to see at least the crash logs if not the project as well so that I can fix it
Phew!
Followed the steps and (think) I’ve just send you a log!
Thank you very much! I think I can see what’s happening
Hey @Michael - the latest TestFlight version is 1.0.18 (build 234) on my iPhone.
🤷♂️
Yep. App Store version 1.0.20 fixes it.
[edit] … well, 99.9% fixed. Sounds like just a couple of samples are missing from the beginning here. I have a kick with a click right at the beginning. The click is still there, but micro faded a tiny bit whenever the sample is retriggered before the end is reached. It’s definitely not my imagination.
Yep, it has a 128-frame microfade to avoid clicks. I plan to allow people to adjust that for one-shots in an upcoming version, for those that have really hard transients.