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.26
![[Deleted User]](https://secure.gravatar.com/avatar/c65f3204a06d27ec73276b6045ed7d23/?default=https%3A%2F%2Fvanillicon.com%2F91feed79a2b1ce0d17ae51ed4913d76d_200.png&rating=g&size=200)
The user and all related content has been deleted.
Comments
Crossing my fingers Keyboard Shortcuts will be shipped next year! 🤞
Me too, since I own an Apple pad keyboard. Thanks for your great work , @Michael …
Haven't checked roadmap recently, how's multi-in and multi-out for AU looking? I think my ideal workflow would be hosting LPro in AUM.
I’m kind of out of the loopy loop but is there any idea so far on when midi loops might become a reality?
I guess 'Midi Clips' with Notes, Multiple CCs and AUParamter recording/automations per clip etc. with option to overdub and edit the recorded data is somewhere on the roadmap?!
Currently I'm spending most of my time with LogicPro on my Mac using the iPad as a sketchpad/sound-module so I'l also out of the Loopy Pro Loop
(For me it's more economical this way as I don't have to get apps for features that are already present in LogicPro).
Cheers!
@dobbs @Samu
Hoping midi clips are in the near future but currently using Atom Piano Roll 2 in Loopy Pro has been a lot of fun.
Definitely built in integration of midi functionality would be ideal but I have a feeling that it maybe part of a paid update/ v2 release.
Yes @Samu it’s an item on Michaels roadmap website
I’ll have to give the atom/loopy combo a chance, so far I’ve kind of put off learning Loopy and when I wanted to loop I just used L7…
Michael has been working like a dog
Beta updates almost weekly / sometimes daily
The man is a machine
I am sure his aim is to please everyone , I guess we all just need to be patience
If anyone can do it Michael can
Yer we all can’t wait for midi clips. Gonna be great.
Whilst we wait for midi loops, atom2 works great in hold mode with play and stop follow actions. Only thing holding it back is the unpredictable order of play and stop within groups of clips, otherwise it’d be pretty perfect.
Here’s a link to a simple loopy template I made.
https://drive.google.com/file/d/1wXKrAOInBro0FhXinmKuxUuVTrahxLpt/view?usp=drivesdk
It’s got 6 groups of dummy donuts (A-F) with 4 donuts in each group (1-4).
There’s also 6 instances of atom2, each with 4 patterns.
Each donut launches the corresponding atom and switches to the corresponding pattern within, eg. donut B3 will launch atom B and switch to pattern 3.
If you play around with switching clips, you’ll probably find the issue I’m talking about, where an atom stops unexpectedly.
Let me know what you think.
Have non-time-stretched loops been implemented? I couldn't find anything in the changelog or roadmap, though I'm pretty sure it was there at some point
Yeah you can toggle time stretch on and off per clip
And globally.
Thanks! I'll give that a try
Thank you for sharing.
It seems like I'm misunderstanding the setting; if I disable time stretch on a clip and then reduce the playback speed, the pitch seems to be preserved, which I understand as "time stretching". I was expecting the pitch to be lowered, as if I was reducing the playback speed on a tape machine.
The time-stretch setting determines whether loopy time stretches clips when the tempo is changed. It isn’t related to what happens when pitch-shifting.
Got it, thanks for the explanation!
Just by way of clarification...
The model doesn't work like that. There are no IAPs for features and there won't be any V2, etc. releases. Loopy will continue to develop as a single product. Each 12 months from the time of purchase there will be an option to pay for another 12 months of updates. If you elect not to pay, you keep the product just as-is, only missing out on new updates. If / when you do opt-in for another 12 months of updates, you get 'em all.
The roadmap gives an idea of the features in progress, but doesn't give estimates of when they will arrive. It does give you the opportunity to vote on priorities and to propose additions.
MIDI Looping currently is in status "Planned" and has the highest number of upvotes by more than 2x of the other planned features. However, it's also probably one of the biggest effort requests, which of course affects the priority.
I think the following is a fair characterization of the situation with MIDI Looping and some other high priority items. This is my between-the-lines reading of things and I hope it isn't out of line for me to share my tea leaf reading.
Things have taken a bit longer to get to its current state than anticipated -- in large part because there have turned out to be quite a few OS and hardware surprises that have required a lot of time to workaround while preserving Michael's desire to have it work well even on some pretty old devices. It turns out that there are all kinds of unexpected weirdnesses that have come to light that took a lot of work find solutions for. One example: some devices that allow sample rate switching behave very differently from each other and some of the OS calls don't properly deal with the situation [some hardware seems to be really always be at 48k but fakes 44.1k and returns some strange timestamps -- and different hardware does it differently]. Unlike most iOS sound apps, Loopy can be master or slave and making that work solidly has been tricky thanks to some of the issues like the one I just mentioned. Add to that getting more real-life data about MIDI Clock jitter and the many ways that AUv3 implement specs, has added up to there being more work than anticipated.
Also, being out in the world and getting feedback from lots of people (side note: with apps like this open betas provide a lot less information than you might think) necessitated making adjustments to make Loopy responsive to people's needs and use cases.
Anyway, Loopy is a really ambitious project -- more ambitious than might seem at first or second glance.
My sideline view is that rather than come up with hack fixes as issues come up, Michael has taken the long view to make the framework flexible and future proof and solid.
WIth projects this big, it is really hard to estimate how long it will take to implement things (especially when it turns out that the hardware and OS have many surprises).
Anyway, I know that MIDI Looping is important to Michael along with some other high priority items -- and I think knowing how long it will take to implement them is really hard to know.
Plus (IMO) not only is it next to impossible to commit to timelines that aren't complete guesses, it's also a no-win scenario. People take estimates as "promises" and get pissed off when they're inevitably missed. Or, they get pissed off because the developer estimates longer than expected timelines, either because they're being realistic and it just takes that long or in the effort to minimize missed dates. Or, features get short-changed in the effort to squeeze them into those time frames. Or the developer takes the pressure on themselves, sacrifices their family life, and burns themselves out.
It's just not worth it. That roadmap is an amazing step toward as much transparency and feedback as possible. But I'm totally glad that it doesn't include time estimates. And I hope it never does.
(Hey ... just a note ... the above comment isn't meant as a retort to anyone who's asked about timeframes. It's just my own standalone musing.)
+1
Already built, just waiting for some other bits before I push out 1.1
And yeah, MIDI loops are a massive priority, but I'm spread relatively thin at the moment working on other things which are also a big priority – like the Mac/VST version, reverse/time effects and overdub feedback, as well as general ongoing bugfixes/improvements. It won't be very long, but it won't be next week either, as much as I'd like it to be!
@wim
Thanks !
MIDI Clips will be huge and I am sure imho it is a pretty serious undertaking. Feels like a major “Version upgrade” if Loopy Pro followed the more common update/IAP path. Either way if anyone is on the fence about LP not having midi clips please dont let that stop you from getting LP. Atom Piano Roll 2 is a great option until MIDI clips are released.
Excellent, thanks a lot @Michael!
Drambo ain't half bad as a midi looper inside Loopy either. LK too, I imagine, though I haven't really tried more than just a light test or two.
The funny thing is, as the creative flow released by committing to audio right away took hold for me, I've barely looked back at midi looping. The idea of having all those midi clips sitting around tempting for me to obsess over tweaking them to perfection seems kind of ... impure in a way. I miss it less and less all the time.
You've always been a fun-damentalist, bless you
@Michael is a genius & dedicated & great guy …yada,yada,yada …
but I really don’t understand this need for midisequencing within the app that cannot already be achieved with
Atom2 , LK , Drambo or others .
& no disrespect to @Michael , but what makes people think his first attempt at coding a midisequencer is somehow going to better what is currently available from devs who have many years of midi sequencer coding under their belt (or anytime soon)
I’m still waiting for the audioside of things to get done , along with the midicontrol of it ( Mackie Control request ) ,
& for the damn manual to be finished before I consider handing over my money .
For all the updates we are yet to reach 1.1 ! & I notice there are way more “fixed” than “added” in each update .
The roadmap & user votes is useful input , but I hope @Michael has the sense to ignore midisequencing requests
until the main functionality of audiolooping is finished & rock solid .
Everyone praises IOS for its modularity , but everyone wants each app to do everything ,
with talented devs all working their socks off covering the same ground , for an ever thinner spread of the financial reward .
sigh .