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
Ah, it was that second thing. thanks.
@sinosoidal, I'm having some issues with LK not remembering the correct controller shape when I reopen my AUM file.
The first pic shows how it should look (I've saved this as a preset in AUM too). but when I reopen the file it looks like the second pic.
Looks like it might be a problem with having 2 points in line? Maybe there's some other way to do what I want.The looper (GTL) has a command that on first press will record, second press will play. So I need 2 clear triggers, no ramps or anything as that sends multiple messages to GTL and it rapidly swaps between record and play during the ramp.
Also I'm having an issue sometimes where the loop gets triggered too late. I'm not sure if this LK or something else, but if I trigger the loop directly with my footswitch its OK, but if I trigger an LK clip to start the loop at the next bar sometimes the timing goes out. I'm actually wondering if that's because the trigger is RIGHT ON the bar line, not slightly before. NOt sure about that. It was working ok sometimes though.
Let me know if I'm doing something wrong here!
Excellent!
Could you please add a function to select a group of notes and make a custom scale from it?
@SimonSomeone Interesting. Placing two automation points exactly at the same horizontal position should not even be possible.
That is not entirely true. If you want to perform a discrete transition from lets say 0 to 1, you will need two nodes in the same position.
Next build will have the custom scale ability enabled.
This should be resolved on the next build. Are you in TestFlight already? If not, send me a message. Thx!
I'm really glad to tell you that this problem has been resolved on build 142. You just need to accept TestFlight invitation and give it a go. Please confirm us that the problem is resolved. Thanks!
Got it. Thank you!
Two questions:
Would it be possible to lift the sharp keys (C# D# F# G# A#) a little bit so it looks somewhat like a keyboard?
Also, wasn't there once a "Fold" function in the piano roll like in Ableton?
Hi @sinosoidal fixing audio glitch work fine! Thank you so much!
Hey, just downloaded and this seems great. Am I right I’m thinking that this doesn’t (yet...) have the possibility to do percentage quantise on notes in the piano roll?
I'm pretty sure we don't do that. But I couldn't really understand what you mean. Can you help us out? Thx!
Thanks for replying. What I mean is that when it comes to quantisation in LK is it an ‘all or nothing’ affair? In, for example, Maschine on the desktop (I think also Logic, and Atom piano roll, but not sure) I can record some midi notes from a keyboard and then have the option of quantising them a little bit, say 50%, rather than snapping them perfectly to the grid.
The advantage of this, is that these sorts of program can tidy up my sloppy playing, without making the rhythm too mechanical sounding.
I hope this is a bit clearer, sorry I am still something of a novice with this stuff. As you say I am pretty sure LK doesn’t have this, but I just wanted to be sure there wasn’t something I missed. I am really enjoying the app anyway.
Thanks for your explanation. That makes all the sense now.
We have been improving LK a lot in the last couple of months. We want to create a dedicated section in composer for notes operations. I'm sure this is something we can easily deploy.
By the way, we are testing the release candidate for 1.8.1 with the following improvements:
@sinosoidal Whoa, that's quite the changelog for a .0.1 release!
Any chance you all are considering integration with the Launchpad controller?
That would be fantastic if possible
Gets my vote.
Hopefully these are easy questions to answer. I don't use Live.
Seems an obvious feature but does LK allow sequencing of clips? I've spent quite some time with the demo, manual etc and haven't figure it out.
Related to the above, is the Matrix IAP required to enable this?
no bm3 even not supporting this feature(
A song mode would be awesome with clip arrangement per midi channel on a timeline.
You can use follow actions to sequence the clips, I hope that the scenes get a midi trigger and follow actions too.
Cool, will try to find that function. Really interested to know what people are using it for if not sequencing clips.
it makes sense for multitrack live audio or midi recording to the host app
Live work I assumed. Just thought it would make more sense to sequence in the app rather than record to host.
The way I use it is similar to Ableton workflow, I sequence the clips with follow actions, use automation on tracks for sequencing volumes and other modulation etc and play the scenes (if we get midi triggerable scenes it will be enough to make a basic song mode), I record multitrack audio out to Ableton, either to session view or directly to arrangement view.
Would good if there was a global "follow action" option.
What do you set it to for sequencing clips?
@Ailerom Probably not what you are looking for, but after reading your question I went to try something.
2 tracks inside aum, 1 for playing clips with notes, 1 for automation.
From track 2 with 1 clip without notes, I send automation to change clips from track 2.
Set clip 1 from track 1 to midi cc1 in the properties (I chose Chan 16) and set clip 2 to midi cc2.
In track 2, set lk output to chan 16, then in the automation clip, add a modulation for midi cc1, and make a node at 127 close to the end of the clip (any length), then just before it add a node, and drag it right below the other node at value 0.
Next add a new modulation for cc 2, add a node just before whenever you want clip 2 to start at value 127, and again one right below it at value 0.
Set LK to receive midi from itself.
This is done inside aum.
This creates other problems, as you can’t for example play notes into the track anymore. But you can build songs with it.
Thanks @Frank303
I appreciate the time to provide that. I would probably only use LK if I could record what I play by selecting clips. I think at this point I would probably be most likely to record the midi out in Cubasis. I've been doing this and it works fine. I really hope an in app clip recording option is a possibility though.
Adding a new scene to a track resets the track midi output. So I have to add scene and reselect the output every time.