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
Aha, I can reproduce this, thanks!
Found and fixed. It is a fix in the lower levels of event handling so I hope it won't break anything else. TestFlight testers: please test the upcoming version thoroughly for weird tap behavior.
Always happy to do that. Spare your valuable time for development
The question then becomes whether you want/expect it to paste at the green time marker or the position you long-tap to open the pop-up menu?
@dwrae
What's the version number of this update ? I haven't seen an update yet in the (Dutch) App Store. I'm still on 2.0.3
Found and fixed, thanks! Funny thing is that this has been in the Android version for years as well and was never reported.
I'd prefer to paste it at the green time marker position since otherwise, positioning will never be precise enough. When the time marker is already covered by a clip on this track, how about pasting it exactly after the end of the covered clip? This way it would be easy to paste a few properly cut loops in a row.
I just added both options to the menu. If you have the grid turned on, it can be enough precision. You can check it out in today's TestFlight version.
Wow. Thank you
I like the way you think! Keeping both options is best
I think I found and fixed it. Note off's weren't always sent to the right MIDI channel.
Super excited about fix for the keyboard issue
That was supposed to be an unambiguously joyous emoji not a sardonically laughing one
Amazing! I would say that pasting at the place you long press is best. Precision doesn’t really matter as you can easily drag it along bar or two. But both options is even better
PLEASE, PLEASE, incorporate positional velocity on internal keyboard and drum pads — ie y axis up, down, or center.
And importing our own Sound Fonts would be excellent.
You can enable key velocity in the app's settings (not for drum pads though). You can import your own sound fonts. Either through the 'Open in' functionality or firing up the Media Server from the Project menu and copying them to the app's SoundFonts folder.
If we’re talking ‘please, pleases’...
At some point do you think you might consider a keyboard you can restrict to a particular scale, and restricting the piano roll to the scale (by hiding notes not in that scale)?
Basically like Gadget. Which I think is very popular with people less comfortable with knowing scales and playing piano.
I second this. With just these 2 add-ons you will become the best daw on iOS. At least from a purely writing perspective.
@dwrae : You mean drum velocity is not possible period , or just “positional“ as @LeadDev1 queried?
At this moment, you can only set the pads to a fixed velocity using the Edit button at the top left. I can add velocity, I'm just not sure how well this works on small phones where the pads are small. Would you suggest vertical velocity within the pad or slanted (?), where the top-right corner would be full velocity, giving a slightly bigger velocity range? Would the bottom or bottom left corner be velocity 0 or a bit higher?
Help! I cannot open WAV file inside AEM.
Why so ?
Every file I try to import from Audioshare is denied access.
I am on Iphone SE with latest IOS ....
Thks for your feedback,
Johnba
It's probably related to either the spaces or the double colon : in the name. I'll check it out, although I don't know how to create such a file name since file names shouldn't be allowed to have a : in their name.
Replying to myself here: I have now added another option 'Drum pad velocity' in the app's settings. When you turn it on, the vertical tap position in the drum pads determines velocity, ranging from 20 to 127. If one prefers fixed velocity where individual pads can have a fixed velocity set up, that is still possible.
Ah, it's not the colon or spaces, it's actually the 'accent grave' on à. I'll see if I can fix this quickly.
Cool!! That opens the door to more realistic (acoustic) drum programming with multilayer sound fonts.
I've often missed that feature outside of Arturia iSpark.
Thanks!
What are the chance of AEM opening the last project you were working on when you boot it up?
(Like Gadget or Auria).
Also it would be really useful to be able to rescan/refresh for 3rd party midi ports. Right now it only does this at launch.
Thanks Boss!
Your app is awesome
@dwrae :Ok, so don’t update the manual, lol.. I’m getting along fine following the video (I’m on #4 now) and any anomalies in the video (2) have been answered by you here in a timely fashion.. Already added velocity to drum pads? Seriously? I’ve never seen another developer be so active and on the case here w the possible exception of @SevenSystems . You must never sleep as you seem to live and breathe this stuff .. Don’t stop now, great work..
+1