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
Thanks @Tones4Christ !! 🙌
Wow, I am so loving the 90s chill vibes I am getting.
...such a nice touch with the little stories and emojies too heh.
Makes me want to just explore the patches even more.
Delightful thing this - just superb ... but it's very memory hungry and prone to throwing major spikes at you. It's actually very big for an AUV3. Just loading a few of them gobbles a lot of CPU.
I've spent the morning running 4 X D1s in AUM using Fugue Machine feeding a playhead to each. It's a benchmark test I try on my new AUV3 synths... standard patterns from Foogoo - everything held the same. Nothing special - no effects. None were possible. Lots of crackling and popping and spikes at 130% before dropping back to the 80s. Quite odd behaviour really.
Not sure how fast or reliable the DSP metering is really - the crackling was still happening at 80% - as if there were unrecorded spikes going on or not being picked up. Or it could be pointing to some flaws in some internal resource allocation somewhere . The overloads seemed rather "random" - not immediately following melody or chord complexity - driven by effects and processing in the D-1 presets I reckon ... there's a lot going on in those presets .... maybe a RAM rating for presets would be handy.
But it's a truly lovely bit of work - beautiful sound quality and superbly musical. Even with crackles it was magic. Could do with some code taming at some point .... I want a choir of 'em.
It’s working fine in NS2 for me with latest iOS on Air 2.
Tried a reboot yet?
Yes, it’s looking like I’m gonna have to update my iPad. Dang. I’m always skeptical about update when things are rock solid. I’m backing it up to iTunes now. Do u know if a restore from the back on iTunes puts 11.4.1 back on it? Or am I stuck on iOS 12 and beyond forever?
Fwiw, I think most people to find 12.3.1 even more stable than 11.4.1.
It’s a one-way trip. No way back.
If you’re reluctant, you might want to hold off to see if any other Pro users have better luck on 12. Or or see if a fix is found.
FWIW I have an iPad Pro 2017 12.9 with the latest version and D1/NS2 is working fine for me....
+1, iPad Air 3, Cubasis 2.8.1
Hm, that's strange. What iPad and iOS version do you have ? It works fine for me in NS2 .. (iOS 12.3.1, NS2 2.0.1) .. only thing which is not working is automation and pitch wheel / mod wheel but this is not working also in other DAWs (cubasis, bm3)
edit: Ok, i managed how to crash it :-) If buffer size is set to "medium" or "high" it works, if i set buffer to "low" or "very low" - it ends stucked in "Loading Digital D1 editor..." . Additionally, it crashes often also when i change buffer size so it is somehow related not just to speciffic buffer size but also to buffer size change.
edit2: Ok also when i try load more instances, some of them randomly stays in "Loading Digital D1 editor..." phase no matter of buffer size. When this happens, CPU load is at 100% and whole app is totally slow, at the end it eventually freezes totally and then crashes.
Here some crashlogs, hope they help identify issue:
The pro is on 11.4.1...just tried it on my updated ios12 air 2 and it works. Must be an iOS 11 issue
no, i edited my post ^^ .. there are some issues ..
That sounds like it is running at the wrong sample rate. What host? Is this through the speakers, headphones or an audio interface.
Even tho it is great as a "90s style synth" I'm getting some great modern sound frm this thing! Great stuff, just absolutely great!
I haven’t updated yet, what should I do? Wait for an NS2 or D1 update?
It crashes at every buffer for me
Yes! After a couple of emails back and forth with @analog_matt yesterday, we did come to the conclusion that it’s an issue with sample rate.
Installed the new update 1.1.1 ,same issue, second AU not producing sound , this time the GUI is not blank ,but if I change preset still no sound and GUI is lost . (AB3 host)
Good morning everyone! Thanks for your patience. We've been working around the clock the past 48 hours.
We're Pushing a new update right now that adds Sample Rate support for AUv3 in newer 48khz iPads (will fix the "out of tune" sound) + Better iPad 4 compatibility + other fixes.
As always, feel free to email me directly [email protected] with detailed bug reports to insure your issue gets the highest priority. 🚀
BTW, I'll be working on D1 through the July 4th holiday this weekend, so feel free to get in touch. I'll be around.
D1 doesn’t work on my IpadOs. Just for info.
And I'll be enjoying multiple versions of D1 in my tracks through the July 4th holiday weekend, so be sure to take a break too, chief!
This is really, really good @analog_matt
Likely to become my goto for staple sounds now it is AUv3. Well done to you and the team.
Please take some time out over the holiday period.
Appreciate the very real effort @analog_matt but suggest ingestion of at least some hot dogs to alleviate burn out etc.
Just noticed that if i try do 96khz mixdown in nanostudio, it mutes all D1 instances and they are not playing anymore, until next app restart..
Any chance this will be fixed too with this 48khz compatibility fix ?
NS allows mixdowns in various bitrates, not just default device hw rate like most of AU hosts - in NS you can do mixdown in multiple sample rates
If it helps, Matt (not you, other Matt
) wrote article about some details how to properly handle various sample rates in AU plugins, maybe you can find there infos which will save your time 
https://www.blipinteractive.co.uk/community/index.php?p=/discussion/479/some-notes-for-au-developers
exit: realized that D1 has problem also when host's buffer size is changes, it stop play any sound after buffer change and only host reastart fixes it.
Just a note to say the 1.1.1 update today still hasn't corrected the pitch problem. Using Cubasis 2.8.1, Air 3, iOS 12.3.1, speakers, headphones, all 48k. Haven't tried with the Focusrite 18i8, but that allows 44.1k which doesn't solve the main internal pitch problem of D1.
Update still isn’t working for me in NS2. 11.4.1 2017 12.9” iPad Pro. I’m always sure it’s related to iOS 11.4, unless someone thinks otherwise. I’m thinking of just going for it with ios12. I hate the one way trip of iOS versions. But I’ve been waiting for d1 since 2018
There are very few reasons to stick with iOS11 anyway. On any supported device iOS12 runs much much better than 11.
+1, gave my poor old Air 2 a new lease of life.
Ok, I like the sound of that, I’m gonna push the install button!
What host? What should actually matter is the host sample rate. A host can conceivably run at 44.1 kHz even if hardware is at 48 k and do sample rate conversion. Clients should be running at the host's sample rate. It is the host's responsibility to deal with the hardware sample rate.