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
Oh! Thanks
I’m coming back to you @xglax and @sinosoidal with that old issue I’ve reported a long time ago:
LK midi thru is not working when loading a session in AUM at 32 buffers latency. Sometimes it takes one or two minutes and and midi thru works. If clearing session, setting 64 buffers then 32 buffers midi thru will work. See video. Some AUV3 midi controllers plays some AUV3 sound generators thru LK midi routing.
If this can be fixed, LK will be 2024 king of fixes!!!!
@Janosax Which LK version are you using? Just test it now and I was able to send midi to LK which let it pass through a synth. AUM buffer size at 32. Have you tried using a simple project? If you route the midi directly from the source to the target (bypassing LK), does the problem occurs? And if you have midi in clips inside LK, do they correctly send the midi to the targets when you start the session at 32?
@Jeezs regarding the following report
We need to understand if this is a bug that was introduced in version 1.13.0 with all the internal refactors that happened. Can anyone else confirm?
What do you mean my accurately? Are you talking about taking into account the clip position based on the transport position? Or do you mean to have follow actions being taken into account?
Well, this is a farfetched request and I would like to clarify if it is related with the previous paragraph. It is not easy to calculate upfront the scene and clip position which a song will be taking into account the host transport playback position, for several reasons:
I will not even consider this as a feature request at this stage. Right now our main focus is to ensure stability and consistent behaviour for the existing feature set.
Thanks!
Can't really tell you. I thought I use to work , but not sure at all.
No I mean just moving the playhead in the host move LK's playhead at the wrong place in the clip.:
I try with only one scene with with one clip in LK with (LK clip was 100 bar length ) if I move the host playhead to bar 30 , in LK the bar move to the bar 17.
Another sync problem is when the host has preroll set , and LK has a trigger quantization set in the preferences, LK doesn't start when the host reach the bar 0, it start with delay ( not sure it's 1 bar delay it seems to be a quarter of a bar )
OK I understand
Thanks!
Just a wish that does not allow me to use LK as the only one midi app is the way the faders respond to touch. They abruptly jump to the point of contact, which makes it impossible to smoothly change parameters. Please can you fix this?
I haven’t opened LK in a while, so I’ve just realized that neither the sidebar nor the top areas of LK are displaying on my iPhone 12. Is this the expected behaviour? Same with both the App Store and TestFlight versions.
Press the third button from the bottom-right, the green one, to get out of "full screen" mode. This button hides the side and top bars to give more room for the rest of the UI
I bought this app for Ableton a long time ago, but can it be used just within AUM to control other IOs apps or is it strictly for Ableton?
It can be used as a midi controller for other apps.
I’ve never used it for Live other than just to see it work once.
Yeah I was just messing with it! Pretty awesome.
Thanks, that was very helpful!
We've just release a new beta which fixes the faders behaviour. Now they have a relative behaviour instead of absolute.
If you're not in LK beta can you please PM your email so you can test out the faders?
If anyone wants to joint LK beta list please PM me. This beta has some fixes and requested updates like scene follow action probability, snap mode for the controller module parameters and multi touch for matrix clip triggering.
LK is one of the best apps I have on my iPad. It’s amazing to see that it’s in active development again.
In its current state, with some tweaks, it works well for my workflow.
I’ve compiled a list of features that I would like to have in LK and some issues that I’ve come across.
LK ver 1.13.2 - Live mode - UBRIDGE 1.7.2, Ableton 12, iPad 9
LK disables Network Midi in AUM
When LK is loaded as auv3 in AUM, it disables the Network Midi session. So every time I load or create a new LK session, I have to reactivate the Network Session in AUM settings. Everything works fine afterwards. It’s just a slight inconvenience, but it would be nice if LK wouldn’t do that
Main track’s - scene renaming - randomly stops working both in standalone and auv3 mode. It always correctly changes the name in Ableton, but it doesn’t update scene text labels in LK. If I toggle the “Song Model”, all labels are refreshed correctly, but it still won’t work for a new scene name changes.
“Arm track when selected” option doesn’t work in “SHIFT” mode. To get this functionality, I had to disable the “Arm track when selected“ option in the LK and create an Options.txt file with -EnableArmOnSelection. It works like this, but now it’s a global setting. It would be nice if we could enable this in preferences for the SHIFT mode as well. I mostly use LK in this mode, as it allows me to change instruments quickly and pre-select the clip to fire/delete with a foot switch.
Expose midi control to fire and delete selected clip in shift mode.
As I couldn’t find the option to launch selected clip natively in Ableton, I’ve added the following m4l patch on the main track and mapped footswitch buttons to FIRE and DELETE actions:
It works like this, but it would be nice to have this feature in LK.
Add visual feedback for a “fired” clip.
A clip that is triggered but has not yet started recording is blinking in Ableton, but there’s no visual feedback in LK. It would be really nice to have some visual feedback that would indicate when the clip will switch to the recording state. The active/playing clip has that nice progress bar that indicates the clip length. A triggered clip could have that same progress bar but going backwards, for example. (ok, I’ll stop dreaming now
Change Trigger Quantization - without menu diving
As I’m changing this parameter constantly, it’s just not convenient for me to enter the settings and change the listbox parameter. In LK Matrix Help, there’s trigger quantization and recording quantization available directly on the top frame (next to metronome, pitch...). I’m not sure if I have to do something to enable this feature or if it was removed. Anyway, I’ve created these buttons in Surface Builder, which is sitting below the LK window. Now I have quantization directly available. It would be nice to have these buttons show up on the right side, in the same area where pitch settings are displayed.
Thanks for reading, and keep up the good work! cheers
I’ve had a play with the free version but can’t seem to find out what the IAPs provide extra. Could anyone help please?
LK has a time limitation on each module. After that time, it will display a pop up and you will need to unlock in order to keep using the module.
Ah ok, thanks. Any idea how long the time limit is?
Between 3 and 5 minutes. After each lock you can continue for 3 times.
Thanks for the quick response, I appreciate it 😀👍
The question I come away with about the IAPs is whether the Keyboard, MIDI Controller, and MIDI Pads modules offer any advantages over hardware devices I already have, aside from the obvious portability all in one ipad unit and such. I much prefer the tactile nature of physical knobs, keys, dials. The Matrix Module seems like a must for tight Live integration. X/Y pad and chorder I cannot duplicate with hardware and they seem better suited to touchscreen.
One thing I would like to see is the ability to make the XY pad stick to a square shape in AUM without having to resize the plugin window. Then my thumb could cover the whole area of the pad one-handed.
Love LK, love Imaginando, and loving this sale. I already had all the iPhone compatible apps, and now I have all the IAPs to go with them.
Is there a way to use LK as a remote controller for Bitwig?
Not in an automatic way as with Abelton. But you could use LK in midi mode and manually map Bitwig parameters with LK so you can controll it just like ableton
I was hoping for something like Live mode because Bitwig being pretty compatible with Live.
That requires completely new control scripts on the Bitwig side. That would be a massive amount of work. Something that we can't do right now.
.
I feel like I’m missing out on something not getting LK but I can’t figure out what I’d use it for. I play soft and hardware synths into Logic, Loopy, or AUM, sometimes using a sequencer with the latter, but 95% of what I play comes from physical keys - everything except the drums. I don’t think I do anything with clips, but I’m not certain what a clip even is! A sample or recorded segment that you might want to trigger at a certain point? I can’t see myself wanting to do that. I know I’m missing something! Maybe it’s most useful for live performing?
It's just a different way of working. No biggie if it doesn't jibe with you.
If you get Loopy, then LK is no different except that the clips are MIDI, not audio.
A clip in LK is a sequence of MIDI notes that can be launched and looped ad-hoc. Take drums for instance. You might set up some variations of patterns in advance (or record them in on the fly), then as you're playing you can start and stop the different clips as the mood strikes you. Clips can be any midi content, so they could be bass lines, chord accompaniments, etc. You could think of different sets of clips as "Verse", "Chorus", "Bridge", etc, and trigger them as needed for a song.
The grid layout of LK can be handy for trying out different combinations of patterns. For instance, sometimes I'll start with just a basic drum beat, and then quickly lay down ideas as they come to me, not thinking about song structure at all. Then with all that captured, I try different combinations of patterns until a song structure starts to come about.
Really helpful @wim - thank you. Given me lots to think about.