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
Hi @sinosoidal , I have a problem with restore purchases of the Matrix module.
I have to restore every time I close the app, the purchase is not maintained at the next start.
I have already tried a fresh install.
It happens both with the AppStore version, which I bought, and with the TestFlight version.
Thanks
ipad Pro 1st gen - IPadOs 13.7
I have the same problem with the app store version. In the testflight version I am unable to restore purchases.
iPadOS 15.0.2
LK on the App Store has currentl a bug that does not persist in-app purchases.
LK 1.11.5 beta (build 264) is supposed to fix the problem. Please ensure that your are running build 264. I've just confirmed with build 264 and everything is good.
Yes, the beta is LK 1.11.5 beta (build 264), but nothing happens when I tap on restore purchases.
Standalone or AUv3? For me it works.
Can you try to reboot your device to see it makes any difference?
Both in standalone and Auv3.
I tried this:
I have no problem restoring purchases in the appstore version 😊
Same thing here, but after doing it a few times and alternating the Appstore version with the Testflight version now the build 264 works
Deleted. Something is wrong in the way I’ve set up LK (just need to find out what it is…), not the app itself.
It was fixed by creating some new presets. Thanks.
Back again. Still encountering the same problem. Thought I had fixed it, but it keeps persisting.
I use LK to trigger loops in Koala. AUM is the host.
When I play a scene in LK, the loop in Koala is not triggered - the first time around.
However, as soon as the scene (and its clips) in LK plays the second time around, then Koala starts playing.
If I use Atom to trigger the loops in Koala, they play instantly, so the issue seems to be with LK.
One strange thing: if I very slightly delay the note offset in the LK clip, then it will trigger Koala the first time around. But, if it starts at 1.0 on the timeline (as I want it to do) it doesn’t trigger Koala - until the second time around.
Solved, kinda.
As soon as I revert to the default patch in LK and set up the clips again, everything triggers at the right time.
But if I use my saved template for LK projects, then the problem occurs. I’ll try to make a new template and save it and see if the problem comes back.
@sinosoidal here is a(nother one!!!) feature request
It could be super interesting from a performance perspective to have dual view mode, like with Touchable Pro. Having clips and mixer on the same screen is super useful. It can work with two instances, but true dual view will give wider controls:
LK double instances
Touchable Pro dual view
Yes! I was thinking this too. Not seen touchable so good to see a use case!
I’ve been getting some crashes recently using LK in AUM. It’s quite a complex song but nothing too crazy. The LK interface stops responding and the current scene keeps playing. If I try to reload the AUM preset, the LK instance won’t open. I have to completely quit AUM and load again.
Let me know if I can help to debug it.
Is there any chance you have a MIDI loop going on? (LK sending to anything and getting that echoed back to it, or vice-versa)
Just checked and it’s just the aum keyboard that’s sending midi to LK. Thanks for the suggestion though.
@sinosoidal
There is something very wrong with LK in AUM and I have reported this same issue before, a few versions and weeks back
The big problem is that it goes into a sort of ghost state so you don't get any crash reports. But, I managed to record some of the issues (not the cause) which are that you can't open clip menus, saves does not take (goes for everything in AUM).
The velocity can not be drawn when selecting multi-notes but the whole bunch moves. A selected note can't be moved, instead it replicates itself when you try.
Hope this little gif clip helps (Latest Beta iOS 15.02 iPad Pro 2021 11')
I've noticed that you have the shift button enabled. The "issues" you're reporting are behaviours related to the shift button being activated, that will give you extra functionalities, such as note copy, overall velocity changes and so on
Try disabling it and see if the problems persist
> >
Ok, but I am talking about major (silent)crashes here not just functionality which I appreciate the lesson on. I still get those greyed out screens every now and then too. Everything I demonstrate in the video is the shift, even clip menu stop responding. That last one could go, right. I do feel a bit embarrassed but I do persist in: something is wrong
Is there a way to set up a clip to be armed for recording and to receive notes from the built-in keyboard, switch to the keyboard layout and have recording start when either you play the first note or press play on the transport button?
@xglax
Indeed , like the "start recording on scene launch" is settings ( up right ) , a " start recording on transport play " would be very very welcome and useful
And, when pressing transport play again , that it relaunches in quantisation what was playing
Lov'
Hi everyone,
I have a starters question about LK (stand alone).
When using the shift button I should be able to add a new track and/or row (with the +/- buttons that should appear) if I understand correctly?
Cause pressing shift in the main screen while in Matrix mode, doesn’t do anything for me. The shift buttons do turn green though.
Uh yeh?? Must have gotten broken in the last update. I know it worked before.
It’s broken in the AUv3 version too.
[edit] it seems the new workflow is to long-press in the empty space to bring up the menu to add tracks, etc.. Which leads me to wonder what the shift buttons are for now?
Hi @sinosoidal
I’m having a problem with LK and AUM’s midi control mapping. If I map my controller via AUM midi control to the Record Arm parameter across 8 tracks, it only ever remembers the track 1 mapping after saving and closing/reopening the session.
I’m presuming this is something to do with the timing with which LK shows it’s currently available parameters when AUM is launching, i.e before LK has opened its own project (but that’s admittedly a very amateur theory).
Is this a bug or just a fact of life? Is there a workaround (although remapping each time is not the end of the world)?
Thank you - I may have sent this request via the beta feedback, but I’m not sure that was the right place or if I actually sent it successfully. Also sorry if it’s come up before and I missed it.
Hi Wim, thanks!
Yeah that works as you suggested, which sort of makes the older Imaginando tutorial videos obsolete.
Wonder if that is by design, or the buttons are broken.
You can add Tracks and Scenes with long press on Master button.
As far as I know, the Shift key is used to:
The first one is the only time I ever use it. The devs listened to us and made most shift actions long press instead.
I use shift to arm/monitor several tracks at the same time, crucial for that.
Can someone please advise, if there is a way to enter triplet notes in the Piano Roll?
Okay thanks!