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
Okay, @sinosoidal and @xglax :
I've been running it in standalone, in AUM, NanoStudio (interface partly hidden), Logic, Cubasis and GR2.
No problems what so ever. Now I've just changed some presets and turn knobs without intent but: no crashes or issues. It feels more ready than some apps released (!)
One thing I noticed is my iPad gets very warm, I mean it always does when start running stuff but it felt like a few degrees more 😃
I'll try to do some more thorough testing when I get the time. For now: very cool (or warm) app.
I haven't pushed it too hard but it's been rock solid and I haven't found any bugs. Nothing to report. That said, without getting deeper into it it's hard to say if everything is working exactly as intended! Granular effects can be mysterious! I'll be putting more time in this weekend.
Sorry but latest build does not load at all in my Logic project (I even tried on a blank project) and the only way out is to force close it.
I also tried re-installing it and rebooting the iPad.
I wanted to see if I could be of help so I started Logic which opens the project I just tested GRFX with (without issue, see my post above). Logic freezes and I can only assume it's because of what unlink experiences.
I did test automation then, with previous version, and had no problem, all was there.
Just to be more precise I was testing DRY/WET automation in the previous release and this wasn't working, I didn't test any other parameter.
I guess that doesn't matter now since it's a new version but I only checked if there was any parameters and there was. I did express: "all was there" which was a bit dumb as I did not check if it was.
Anyway, I hope they find what causes Logic to freeze, or not loading GRFX, and fix it. 🙂
@unlink @sinosoidal
I did a restart and Logic started, but it took a long while. Now to the funniest thing: GRFX was replaced by K7D!? I have not used that plugin in Logic, ever. 🙃
Well, guess it was a smart move because at least now I'm not locked out. I will not even try GRFX (in Logic) until we know what's going on.
edit: typo
This app is great on guitars for thickening and giving harmonic space. Also good on simpler synth presets to embiggen them. :P
Deleting the app and reinstalling it has made it appear in my AUv3 lists in AUM and Drambo. Hooray!
We are still trying to understand the cause of this need. It is not sistematic. It does not affect all users. There must be a catch somewhere.
The iOS version in use can play tricks when it comes to properly registering the AUv3.
Launching the stand-alone at least once after initial can in some cases help and if that doesn't work then a reboot after first launching usually does it.
@Pxlhg @unlink
Latest beta (6) fixes the Logic issue and the also fixes parameter automation. thank you for your feedback
Installed TestFlight beta on iPad mini 5 a couple days ago with no issues regarding not showing up in AUM.
Just installed on m2 Pro AND iPhone 11pro with no issues regarding visibility in AUM.
Both iPads and iPhone running latest OS
Should share that I had issues with it showing up on M2 iPad Air on first launch
I downloaded it, opened it up solo, gave permissions, then went to close it out and search in AUM, Drambo, Loopy, and BAM, no go.. uninstalled then I did what I usually do - download, close all open apps, open new app solo, give permissions, then close down app, restart iPad, turn back on, then open it up as an auv3.
After that whole bit, then it showed up just fine.
Idk if that’s even needed, I’m just in the habit to do that process whenever install any audio app on any Apple devices, the one time I didn’t do that it did this whole not showing up thing lol.
A part of me is wondering if I was typing the app in wrongly but no I’m 99% sure I searched correctly
It loads without issues and the automation is working. Just one minor thing, if I draw a line which goes to 0, the value actually goes to 5% when it reaches the bottom 😅
That’s so odd. I didn’t open it solo first… on any of my devices. Just installed, opened AUM, add a channel, then add GRFX. Right there every time, and I didn’t have to give it permission for anything on any of the installs.
Just a quick test with the iPhone shows the permission! First time I opened it on here.
I haven’t seen any app not ask for permissions when it comes to mic use. Not sure how it would pass that barrier
Opened up just fine in AUM and solo as mentioned, Fairly certain I didn’t restart this phone since install.
Oh, if launched in standalone it asks for permission… but I was saying that I didn’t first launch in standalone. I simply installed then went straight to AUM where I could add GRFX and use it. No issues with deleting or reinstalling to get it to show up. Just installed and worked as expected across three different device installations
Ohhhh apologies! You stated that clearly and I was much less with my response.
Though I guess that answers my thought on how an app would cross that permissions barrier, just needs to be hosted in an app that you previously have permissions to.
That seems like a large omission from the standpoint of privacy and apples sandboxing approach… I mean I get it but also, weird. I guess overall it makes sense. Host being the main thing needing to have permission.
I feel like I read somewhere to do that in a manual or you could encounter issues with an app, can’t recall what software/app, but ever since I usually just do that, rarely any issues.
I mostly giving specific detail for the dev to figure out what’s going on, ie. One user (me) who didn’t open the app and thus also didn’t grant permission… didn’t have to delete and de-install… vs others (like you) who first opened the app, granted permission, then could see the app in AUM.
Just giving specifics in case there’s a clue in there
Yeah no worries I get ya
This screenshots makes think: is this actually useful on a phone device? It will be impossible to make it usable with the same design and layout in such a small screen.
What do you people reckon?
@sinosoidal loaded as an AU, in landscape it's very useable. But in portrait the clipping problems mean some of the controls are inaccessible when you make the window big enough to work with.
If the controls re-arranged into a vertical format it would be great.
I somewhat agree for myself - but really hard to know for sure what’s best to do. I can’t see very well so for me it doesn’t work!
I’m know there’s a lot of people who benefit from having a phone and being introduced to music and getting the chance at a lower barrier of entry to get some music apps and potentially start their journey, learn, grow musically from it.
So in that vein, I’m totally for you any and all devs for having their apps available to iPhone only users, if they can swing it and make it happen and it’s not a bad experience.
This screenshot is a bad example as well, I have a smaller phone screen, and never use it for music, was just testing out that small issue. I don’t think I’d use it like this seriously.
Full screen on iOS is actually quite nice!
I've now tried it in Drambo as well, worked fine until I tried with @rs2000 superb generative project (thanks man). I placed GRFX after the reverb and it choked badly after some time. To start a fight* I replaced GRFX with Quantum Granulator and it runs smooth as hell.
*joking
Haha, I'll test with Drambo once I get access to the GRFX beta version.
Not sure if it's Drambo's "fault" because my patch is fairly lightweight.
I expressed myself poorly, nothing to do with your patch, on the contrary it was an excellent test, sounded awesome without and with both plugins mentioned. However: I've done some more testing and I'm not sure what Gustav has done because his plugs are usually pretty heavy but this one is not, and it's granular. Go figure.
GRFX seem to want about double the sauce comparing these two in various scenarios.
Now, it's not for me to do or say, it's just happened like so, and no shame on anything. They're both (the plugs) something I will use often.
Edit: -
I’ve been driving it in Drambo this morning and I definitely experienced some CPU spikes. And after a while, the interface started to get really laggy. Restarting Drambo set everything right again, but I wonder if there’s some kind of memory leak going on. Really cool effect though, using it on drums produces some phenomenal rhythms.
Yeah, I was experimenting with trying to bypass the effects at the bottom row but couldn't really figure out how without it sounding wrong. Many presets have automation from the LFO's to those, so..
I was thinking of Klevgränd OneShot which has effects built in (2 for each drum + 2 send + master) and, I think @wim, suggested to turn off the ones on the drum modules (in AUM) to get the cpu down. And it works really good to do so. It has multi out so you can always add your own.
I'm not sure how the same could apply here though, just thinking out loud pretty much. 🙃☺️
Thanks for your valuable feedback. We have listen to it and refined important details based on it. Thank you very much!
The release candidate has been uploaded to TestFlight and 25 new seats have been open. If you haven't had the chance to try it, this is your chance: https://testflight.apple.com/join/V4YzTnUJ
Thank you very much!