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 have just uploaded a new build that provides support for Launchpad X, feedback is highly appreciated from those who have this controller. In the mean time we have released this video.
Awesome! I'm hoping to have fun with it this weekend.
Great video, too!
Is that just in the beta? I have a Launchpad X ready to go and a locked down weekend ahead so if you need testers please let me know.
Yes, are you in TestFlight?
Hooray. Yes I am.
@sinosoidal
Here is my list of possible improvements.
Thank’s lot for supporting the Launchpad X and to let me test your beta
For the Matrix-Area:
1. Stop clip when tapping on clip would be nice (in the the App and with Launchpad)
2. At the moment there are random colors for each new Clip. A option for just one color for a track would be great. So that all drums have the same color, all keys etc.
3. Now, If you want to record to a new clip you have to click first on the record button of the track. It would be fantastic if you just tab on a new clip and record is automatically starting.
4. Shift + Tap on multiple Clips to change Properties for Color, Length etc. for all of them would be a nice feature
5. To have the same color for clips in the app and on launchpad would be awesome
6. Shift Add Track/Scene is really hard to press on my iPhone 7 cause of the small, close by buttons. Without my iPad I would not have known where add Track/Scene is at all.
SO launchpad x is very problematic. How can LK still be receiving midi from it if I have disabled? I have midi set to none and in settings have it un ticked. I want to use the LPX as triggering Launchpad APP in AUM which it does but at same time it goes back to auto connect to LK. I have disabled all that I can see for it to connect.
Standalone or in a host? I don't see how it can auto-connect as an AU in a host.
In AUM. its soooooooo strange I dont get it.
Dedicated controllers in a AU plugin is something tricky.
It seems that the Audio Unit architecture allows multiple midi outputs but only a single midi input for an audio unit extension. We have LK Input as midi input for the Audio Unit, so... we had a problem:
How could we distinguish midi input from multiple controllers if there is a single entry point that has always the same name?
What we did was to talk directly with the operating system via Core Midi, just like we do in the standalone. This means that the Audio Unit is capable of knowing which midi devices have been plugged and trigger the necessary sequence of commands to reflect the state on the device.
I was already expecting something like the problem you are having. The solution is to have a panel somewhere in LK that says if we want or not to use a certain device for LK control, otherwise, if LK is open and the device is recognized, LK will always assume that device is a dedicated controller to be used.
How many of you have already tried LK with AKAI APC Mini, AKAI Apc Key 25, Novation Launchpad Mini and Novation Launchpad X? We would love to hear about your experience so far.
Thanks for your feedback, as always!
Please add a way to ignore hardware input and only listen to MIDI sent from the host. There are a number of apps that are rendered difficult to use because they listen to hardware you want them to ignore.
+1 - That's kind of critical IMO.
You'll still get people wanting to do both at the same time, but it'll just have to be explained to them that it has to be either / or.
I've been busy today and have only had a chance to give a very quick test. It's awesome that it just works, but I've honestly only lightly dabbled with LK so far, this makes it a lot more useful and interesting for me. I need to spend some time with the tutorials to wrap my head around LK usage. In my two minutes of testing I couldn't figure out how to record arm a clip and input MIDI notes from the Launchpad X.
Define "wanting to do both at the same time"
I'm just having great fun with APC key 25. Everything works!
Navigation, launching, arming, selecting, mutes, solos... Simply Awesome!
The only thing that I find confusing is that only the last directly launched clip (not via scene launch buttons) is green. Other clips turn yellow even if they play. That could be normal behavior though, I have no experience with how this works in Live.
Great!
This might be a bug. We need to investigate!
I was referring to wanting to use the controller for something else at the same time that it's in use as a dedicated controller for LK. @onerez wasn't saying that. He was saying that LK was grabbing the LPX even when he didn't want it to. But I expect that people will try to have something like the LPX working both with LK and with something else at the same time.
Maybe it's not relevant. Anyway, my main point was that it really does need to be an option to not have the controller automatically listen on the hardware input.
This doesn’t apply to note input, that works through AUM’s midi routing. The issue would be with the Launchpad’s session / control input. I’m not sure other than the Launchpad App itself this would affect many other Apps?
It’s clearly a problem for @onerez, but I’m happy dedicating the Launchpad X clip launching to LK.
All working well so far. One thing I’m missing is LK’s master record toggle on the launchpad X. Great having the solos, mutes, stops, record enables and triggers on the launchpad, but I still have to keep reaching for the iPad to toggle record once I’ve practised a part. @sinosoidal Can the ‘capture midi’ button be assigned to that?
One thing to note for potential hardware buyers, lightning iPad doesn’t provide enough power for the Launchpad X, you need a powered usb hub.
I hope that I did not come across the wrong way.... I was trying the Launchpad App in AUM really for the first time and I realized a lot of potential there..... I did not realize or I am too dense to have know that I can export my own loops into blocks wav and then into launchpad app. I liked that I could set the trigger to immediate so I could control when a vocal or FX or what ever came in. It was then I loaded up LK and whoooppps.
It could apply in lots of situations. For example, you might not want LK to listen directly to the controller because you plan to use a the controller with a number of apps and use a script or MIDI filter that sits between the launchpad controls and any apps/plugins to direct the controls where you want.
@espiegel123 @onerez And I’m using my Launchpad X for the first time with my iPad to try with LK. So pleased with how it’s working I hadn’t considered people might already be using the Launchpad control with other Apps (I bought mine recently on Atom’s clip launching promise, it’s been tied patiently to my desktop until now).
Mainly I wanted to clarify it didn’t apply to note input.
Sounds like an on/off in LK would address the conundrum... or more controllers for everybody
EDIT: I just tried the Launchpad X with a few other apps and I think Launchpad (the app) is the only one that makes the ‘Session’ control active. So I think @onerez was particularly unlucky to find the one app that LK’s launchpad clip launching clashes with. If you want to talk about hypothetical scripts for hypothetical apps then that’s your own thing.
It is clear that we need a way to release the controller from LK and keep the state of the decision preserved. I'm just think the best place to do that:
I dont know if you need another menu, if the toggle would be preserved then that would work.
thanks!
To expand on my APC key 25 experience, I found that the Play/Pause and Record buttons are not mapped.
I must also add that the new clip record method works wonderfully with this controller. The only thing staining the experience is the quality of the keys.
issues drawing automation 1/32. if start empty and draw full lenght it is obvious
So does the launchpad x use the session mode to launch clips in LK such as it does in ableton? Any plans to support pro mk3?
It does, and I did test that you don't get LPPm3 support "for free" with the LPX support. I'm really hoping for full LPPm3 support with a more "hands-on-controller" workflow. So far you can trigger clips and scenes, as well as record arm, but you can't use the controller for things like creating a new clip/scene, or copying.
The rapid pace of development is exciting, though. I can't wait to see where this goes.
I checked that before I posted lol. I was hoping. Thanks for the info.
Can you please make us a video demonstrating the problem? Thanks!
That's a good point. Let's do it on the next build. No this one, the next!