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
Yeah, sure!
@sinosoidal @blueveek also recently added drag and drop to Atom, so could be another resource.
Thanks! I've dropped him a message.
Is anyone having troubles launching the latest beta (218)? Both standalone and AU crash when I try to launch them
Are you able to upload or send me crash report?
Yes I have the same problem.
The feedback you provided via TestFlight does not contain crash report!
Standalone and AUv3 or just AUv3?
Do you guys allows under your privacy settings to share data with developers? I'm not receiving the crash reports on Xcode.
I have had a lot of crashes today in the Auv3 in AUM, but it was beta version 217. Where do I set up, to allow to share data with developers?
https://support.apple.com/en-us/HT202100
After enabling it, please reproduce the crash a couple of times.
Or, you could also send me the AUM project to see if I cant replicate.
That's really strange, because I have everything enabled under "analytics and enhancments". Are the crash reports stored somewhere on the iPad so I can send them to you?
Send me a AUM project that is causing the crash.
When I had the crashes earlier today, LK also crashed when I tried to create a new AUM project and then add LK as a Midi processor. I sent a mail to you earlier today about it, but it was beta version 217 and I have just installed version 218, so I will try and see if I can get it to crash too.
I switched on sharing analytics with app developers and sent feedback again. Did you get my crash report this time?
@sinosoidal
I found 2 reports in analytics and enhancements/data named LK and date and time, I have sendt them to you.
Don't have nothing yet. Weird!
@white has shared crash reports with me. Maybe he can tell how to retrieve them.
My crash logs are located here. The screenshot is in danish, sorry:
Open a log and then you can share it.
thanks!
I've just published build 224. Based on some beta testers feedback, the crash at startup is solved by deleting and installing the app again. If LK crashes at startup, please delete the app and install it again from TestFlight and please let me know if it still crashes.
Attention: Before deleting LK, ensure that you backup .json files inside LK/Imaginando/LK if you rely on project manager instead of host state saving
This build has all the changes that are supposed to be on 1.10.4:
Drag and drop support of midi files to AUv3 (without import dialog) works really well 😊👍
That's awesome!
Where can I found Q button for quantize after recording?
Open the clip properties panel by pressing the “i” button top right, then open the "note tools" section. Quantization will be applied to selected notes, you can select a few or all by clicking the “select all” button. Then just press the “quantize” button:
branis thank you 💪🤛
@sinosoidal Thanks for adding drag and drop! Noticing some odd behavior behavior though, depending on the midi file imported.
I exported midi files from Atom 2, and they are not importing at all with drag and drop; file import works fine. Not working on iPad Pro 9.7 2016 13.6 or iPad 2018 9.7 14.4.
Loopbud exports are only importing to the 1st clip slot in top left corner on 14.4, regardless of how many tracks there are and where you drag and drop. Creates new tracks under 13.6.
Also, used exports from Piano Motifs, but those appear to multiple channel midi files, even when it's a single melody export. These are creating multiple tracks, which is likely expected behavior on 13.6 and 14.4.
For drag and drop, is it possible to support dropping onto clips rather than creating new tracks?
In first place let me thank @blueveek as he as helped me unlocking an important detail with the drop action on iOS. Thank you @blueveek!
So if you use the import dialog everything works as expected?
If you use the import dialog everything works as expected?
Are you able to send me those files so I can use them for testing?
I'm not sure if the drop action on iOS will allow me to know the exact x/y location of the AUv3 windows where the drop occured. Likely not.
Thanks for your feedback!