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
I've just tried with my AirPods it works just fine. Reboot your device and try again. Also, when hosted on AUM, sample rate, buffer size and beat time depends completely on AUM, so it shouldn't be LK's problem.
To clarify, I wasn’t saying that the sample rate and buffer were your problem, I was just pointing out that’s what happens in AUM with AirPods.
Anyhow, I tried restarting and no difference. The same project loaded in the same way with the previous LK was fine.
I am using AirPod pros and I’m on iPhone 11 Pro if that makes any difference?
Had the same consistent problem on iPhone in Drambo as a host. CPU overload happens around bars 35-40
We are currently beta testing version 1.9.1 (build 178) which should fix this problem.
This is the most complete LK tutorial so far. It covers all the aspects from A to Z (in russian) when used as AUv3 plugin inside AUM. English subtitles available:
re. Airpods I've encountered occasional audio buffering instability more recently - not sure why but it seems to get worse if I'm using the Apple Pen thing. So maybe it's an Apple Bluetooth bandwidth issue rather than an LK or AUM issue. Just guessing... Also there's the rumour that Apple are (as I understand it) now automatically updating the firmware on the Airpods transparently which is a bad turn of events (not withstanding that these are of course first world problems...).
@sinosoidal: Any chance of implementing slide over / split screen on LK at some point in the future?
Also it would be great to be able to assign set colours to individual pads/faders in the controller page...
I am still getting CPU spikes (even going over 100%) while recording in 1.9.1 (build 178), but I wouldn’t know about it if there was no CPU meter in AUM. The recording is smooth, only looking at the meter is a bit worrying.
I also noticed that quantization works much better. I’m not sure if the recording is now more precise or if the quantization itself was improved, but it works as expected now 👍
If you don’t hear any artifacts, those spikes might just be an indication of the OS bringing resources online and then deciding they aren’t needed..as the OS dynamically throttles and and brings cores online and changes priorities.
Hi! Any word on when LK will support Launchpad Mini MK3?
What's the buffer size you are using?
Recording midi clip with pre defined length has proved to be quite intensive graphically because it needs to paint all elements of the composer due to length cnages. We have improved the repainting behaviour to the necessary only. Many redundant calls were being made and are now avoided.
Recording has been dramatically improved on version 1.9.0 as we are now taking into account the sample position of the midi events. Recording from other midi generators via LK Input is now possible with accurate results. Maybe this is what you are feelling. We haven't made any changes regarding midi recording on version 1.9.1.
I think you’re right. I just did another test and I didn’t get CPU spikes. Must’ve been something else going on in the background on my iPad at the time of the first test.
Sorry, there is no ETA for that controller yet.
My buffer size is 256 samples.
I remember that with the previous build quantization gave some erratic results. Is it possible that in the previous build, due to the heavy cpu usage while recording, the recording was not precise which shifted recorded notes just enough to get unexpected quantization result?
Anyway, it looks like the CPU spikes I had with the latest build were not caused by LK as I can’t reproduce the problem.
Gotcha, thank you sir!
You are using a really tight buffer.
Bigger buffer sizes means less CPU usage but more latency when recording audio or notes. Small buffer sizes means more CPU stress but lower latency.
Most probably! It is a very plausible explanation.
Great! Thanks for your valuable feedback.
Anyone else getting this, blank after hitting clip properties?
What version? App Store or TestFlight?
@sinosoidal I’m still getting this problem. I can send you a little video that demonstrates the issue if that helps?
Seems it may be ‘one’ specific imported midi file that’s causing this... PMed..
What do you mean with this? Can you explain a little better the details and purpose?
Even more important than colors would be the ability to choose an individual channel and device for each control.
Even been focusing ourselves on the MATRIX. I guess that when the whishlist is empty for the MATRIX we can tweak many other things.
That dotted line around the icon normally means you have a midi loop. That’s probably the cause.
Strange though. I don’t see the orange dot on the “hamburger” menu, which usually means there’s nothing routed to it?
I’d check all the routing carefully. Something weird is going on.
@sinosoidal: Sure
I want to control parts of Drambo's operation - mutes, sequences via the LK Controller page. I appreciate I can use LK inside Drambo to control other aspects of Drambo's plugins, but not the sequencer track or mutes - this can only be done using LK outside of Drambo standalone. If I use Drambo inside AUM along with LK I can arrange both apps side by side which is great but of course Drambo reverts to not hosting auV3's. So the other option would be to use the ioS split screen feature so that I can see both apps at once.
I don't know what is necessary to comply with split screen on iOS apps. This is something I need to investigate.
AUM doesn't support split-screen> @sinosoidal said:
All apps that I know of that support split screen also have a portrait mode. To work with split screen requires adapting the UI to different aspect ratios.
Maybe that's the missing piece. I will need to run some tests. Thanks!
Somebody else experiencing midi bugs with LK in AUM as follows: When triggering LK external via Arturia Midilab mk II or inside AUM with Velocity KB it starts out fine. But after a short while Notes are latching followed by no midi response at all. No response lasts quite a while, then it works proper again for a short while, then crashes again and so on..
Yes, having same probs. They are already working on a fix
Does any one know how to assign a midi cc for the master track stop button ? Or is there some other way to make LK stop playing via midi (without resorting to stopping a playing a host (aum))
Master track needs properties just like the other tracks and include a STOP MIDI TRIGGER setting.
However, I can se now that it's possible to assign each track a unique note number for stopping individual tracks, and instead use a common CC value on all of them to make all tracks stop simultaneously. A little cumbersome but it should work.