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
We can definitely replicate this issue but I would not call it a LK issue though.
Loopy Pro is destroying all AUv3s when the app goes into background and restoring everything back when it comes foreground. As far as we know there isn't any other host that does this otherwise this problem would have arose already.
@Michael I will send you an email so we can discuss this and other details we have seen while replicating this issue.
I haven't been very active lately but I do like to remember it did happen even with the latest update (LK and iOS) but it could been a version back. It does still happen anyway but I have no clue how to force it to, if I did I would have sent you a video.
This started happening to me where the window goes blank. I was able to reproduce it. I can later see if it still happens. It is in AUM.
We are trying to reproduce it sistematically. It is very hard. It happens rarely and randomly.
Are you able to reproduce it sistematically? What's your iPad OS version? What is the minimum AUM session configuration that makes it happen? Thank you!
@sinosoidal I am running new M1 ipad on iOS 15.2. I have AUM set pretty much default but buffer at 1024 see screen shots…. Here is the interesting thing. I have used LK for a LONG time and I have never had this happen, until I added Loopy Pro into the mix…. I am not saying that Loopy is causing it or it could be I am sending midi to 2 different synths on same channel.. but as soon as I added loopy and started to record loops this is when it happens. The other issue it that sometimes I can go through a session and it does not go blank. Does LK dump any logs locally that I could send????
As a workaround I found out that if I tap on the project menu to open it, then just close it (without changing project of course) then the next time I need to use the keyboard in an input field, the keyboard opens correctly.
Maybe a hint to a solution to this problem @sinosoidal ?
I’ve, unfortunately, been sidetracked by work, a new dog, and new hardware, haha. I haven’t played around with it since around my last post. I’ll try and get back at it and let you know, but I honestly can’t say when that will be.
I feel like the answer is probably somewhere in this thread but I can’t find it: for some reason, in clip properties, I don’t see the option to assign a midi cc to trigger the clip. I see it mentioned in the manual and have even seen screenshots of the UI, but that setting does not appear for me, whether I have LK running standalone or as an AU. I’m sure I’m missing something obvious, but I’m stumped!
How often does this happen? Does this happen sistematically? Can you easily reproduce it? How? Or is it completely random?
No worries. Thanks for your reply.
To use cc for clip midi triggering you must press the "Midi Learn" button on the top bar of the Matrix module. When pressing this the clips and buttons will have a purplish overlay meaning that you're in the midi learn mode. Then, you just need to press the clips you want to trigger (they will have a white outline when this is done), one by one, and send the midi cc information to LK. The clips will have a little label indicating which cc and channel are assign to them. Exit the midi learn mode when you're done and you're good to go
@sinosoidal …. I tried for 30 mins to get it to do it and it would not do it again. Sorry.
That is the challenge we are being faced right now. The problem exists, many people had it already but we can't reproduce it in a sistematic way. It is very random. We will keep struggling.
We are really commited to squash this one. Any relevant piece of information on how to reproduce it is very welcome. Thanks!
@onerez
When the problem you've reported happened, were you using any external controller to control LK?
I def want to get back into it. Once I do, I'll make sure to report any bugs and get screen vids if possible.
No. Just using iPad by itself.
Thanks for your response. Don’t worry about it… It turns out this is an issue with the external hardware, the drum machine only seems to accept one midi note at a time from my ipad, no matter what app sends it. Was not an LK problem.
I have used the drum machine before without this issue. But there was a firmware update on my drum machine and I suspect that might have had something to do with it.
The first time the issue came up for me was also the first time I used LK, so I immediately ASSUMED it was LK and it wasn’t!
For anyone interested: here my experiences with this app so far.
Warning: long and confused rambling incoming..
TLDR VERSION: I am having issues understanding how to record tracks live, while having the track continue to progress to the next scene and still record instead of recording one super-long track loop in the matrix while all the other tracks continue moving to other scenes.
For context, I am a mostly-improvisational musician and I would akin my AUM workflow to that of a dawless old school techno setup (regardless of what genre of music I’m making), if I had to sum it up. As such, I’m constantly trying to find a good way to record all my projects in midi form instead of relying on huge audio recordings for everything…easier to edit later, and easier to take a cool idea and replicate it later!
anyways, here’s hoping this feedback is helpful and also perhaps people could share their workflow best-practices with me!
Overall, I love LK so far..My only problems are that it’s a little finicky for my style of live-loop jamming and improv. also sometimes LK crashes when I make a scene too long… but those are probably more so ‘me problems’ more than anything
if I plan out my scenes and enter note data with a more organized and thought-out approach, I never have issues. It’s only when I go a little crazy with effects and additional channels in AUM, as well as the long clips, where I usually have problems.
I’m looking for a quick way to quickly lay out several scenes in a row that are triggered to move on to the next one by default. Right now I’m having to build those settings manually and I’m not sure if I’m doing this right. Also I’m looking for a way for live armed tracks to move down the scenes, so if I’m recording midi while playing, everything will still go to each next scene while I’m performing, and it will record during that whole process?
The only way I’ve found to do this is to go in and manually build every scene and track, and duplicate them, but it still seems to just make that track loop I’m recording super long on that one scene, and then the other tracks keep going to the other scenes even tho the one I’m recording doesn’t?
example: I put down a drum track and bass line track, both with midi data. Then a piano track without midi data yet. Tell that scene to play next scene after one loop. Duplicate to certain amount of time and make a few changes at certain points for drum fills. Now I start from beginning, wanting to perform a keyboard part through the scenes. It just makes the piano scene super duper long in that track, or loops it and keeps adding more and more midi notes, while the other tracks go down the other scenes.
Is there a way to make this piano track continue to move down to the next scenes at the preset bar intervals while I’m still live-recording? I do this all the time in korg gadget, like ‘loop track 4 times’ rules in some scenes, and then the next scene could be totally different, all while live-jamming on an armed track that records all the midi data and moves on to the next scene recording it in there….but in LK it seems like the scenes progress with different rules per track if I’m recording vs letting it play back. Then it just records one super long track loop in the matrix while all the other tracks keep going. Ugh I am sorry I can’t explain it very well haha …
anyways, I kinda thought that was just ‘how it works’, so I went with it…then I’m able to get a lot of good material down but my loops end up too long and then it crashes. Not to mention I can’t really get the same timing down cuz everything was playing in diff scenes … I probably overcomplicated my explanation here, but I don’t know how else to describe it. Is there a ‘don’t loop track while recording’ setting that’s that I can’t seem to find? Or maybe it’s a ‘move track to next scene and continue recording’ that I need? I’m not sure ….Any help from anyone here would be appreciated lol
It just sucks when I do all that and haven’t saved in a while and I lose a ton of progress. The only thing I could think of for actual app feedback on that would be ….Perhaps there’s a way to implement a way to opt-in to an ‘auto-save’ feature? Maybe every such-and-such minutes it saves a cache of your project? Cuz if I’m in creative mode and I lose progress, AUM doesn’t seem to save anything in LK when I pull up the last session, even if parameters in other apps were saved.
Other than all that, I love the way you can automate midi parameters and all kinds of things all in one spot, right inside AUM. It’s the closest thing to a real daw workflow in AUM that I’ve found, at least for my purposes
Looking forward to what the future brings and for any advice on my (probably shortsighted) workflow 😁
Well, it is hard to read everything without getting tired. It is a long post
You could try the following:
keep it going to next scene without stopping using next scene launch button
in the end, set clip or scene follow actions
Let me know if this helps.
Regarding the crashes. It is a bit confusing the way you describe it. Are you able to reproduce the crashes sistematically? What does it take to make that crash happen? Are you able to make a screen capture showing us how to reproduce it? That would help a lot.
The auto save feature makes sense. We will open an issue for that.
Thanks for your feedbaack!
Since the beggining of the week that we have been trying to reproduce th> @onerez said:
Since the beggining of the week that we have been trying to reproduce this problem. It is a rare and random ocurrence. We are definetely able to reproduce it but it can take 3, 5 or 8 minutes tests and sometimes it doesn't happen.
We have uploaded a new build that had an update to the underlying framework we use for our apps. We have been trying to reproduce the problem with this new build without success. We are now looking for others feedback about it.
@gregsmith the issue with UI disappearing on Loopy Pro happens if background audio on Loopy Pro is not enabled (which is not by default). For now, an easy workaround is to enable background audio on Loopy Pro.
Which build is it? I don’t see this in version notes. Last one for me is 1.11.8 272.
I encountered some issues too, like full crashes with LK AUM node asking for reload, and also LK UI freezed (aka LK still sending midi but all graphics freezed and touch unresponsive). I can’t see how to reproduce steps. It’s on iPad M1. Let’s see if this build helps with that too.
That's precisely the build (1.11.8 - 272). We didn't mention I'm mentioned here because it is too vague. However, if we can confirm the issues are gone with it, then we will mention on the update notes.
The issues you describe are exactly what exactly what we are trying to find a solution for. Those are indeed not easily reproducible but as far as we can tell, its more prone to happen on M1 devices. Please give it a go and let me know if it makes any difference. Thanks!
Just spent 30 mn with it and not a single issue. Let’s hope it’s fixed, I will test it more in days to come
I don’t like it when “midi learn” is the only way to assign CC’s. It’s fine for hardware controllers I guess but there’s many cases where you’d just like to input the value manually. To me that should always be an option. You might want to set the CC beforehand and map the control later.
Yeah it’s better especially when there is midi traffic like several midi messages sent by a single button. Manual value setting makes life a lot easier.
Exactly. In Drambo's MIDI learn, you tap the item once for automatic learn, then tap again to receive a full edit popup. This seems like a slick solution.
Please could you consider implement record button in AUM instead of knob @sinosoidal that could be super useful:
Good news!
We will try to figure out a solution for this. Thanks for your feedback.
Still testing the crash fix @sinosoidal
Before I had a crash every two sessions so 50% of the time.
Since latest beta I made perhaps more than a dozen of sessions on three/four hours and I had only one crash.
It was after clearing a big AUM session with tons of AUV3 (no LK), then opening directly my LK template and starting recording, happened after 2 mn. This was already a condition which seems to be there with crashs I’ve seen before with LK. Perhaps something in memory, even if it’s a 8 Go M1?
After this one, I always closed/reopen AUM before using LK and not a single crash!!!!!! I’m super happy, really!!! Thanks for that fix. LK multichannel input multi recording and abletonesque capabilities are really cool for midi live looping and fast production 😎
This is good news. Really glad to hear it. During the weekend we have released this version to App Store. Let's see what more data tell us.
In the mean time, we are working in version 1.12.0 and making a significant revolution in the midi composer. We should be able to post a new beta really soon to have your early feedback about the changes.
In summary, we are merging the automations editor with the notes editor using a toggle button. This will allow to end with the second drag bar, saving more space and at the same time giving more space for automations editing.
We are also introducing curves to automations lines. By simply dragging a line up and down we can control the curvature.
Another change is to have the tools under the properties inspector layed out in tabs to avoid toggling panels and scrolling up and down.
I'm really looking forward to share this with you.