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.
Clav app with low latency
I like Neo soul keys, but Latency.
Do you know one that sounds as good?
Mostly need it for Clav, what are the alternatives, and do you think they have less latency?
Comments
What's your buffer size setting?
The one in Korg Module is superb.
IMO much more playable than the one in NSKS2 plus it has a realistic interface including all tab settings and the mute slider.
I think it’s currently 50% off.
If you don’t already have Module Pro then you can still use the free version to get the IAP, although one of the pick-up tabs is disabled.
If you have a recent Korg controller eg micro key, nanokontrol, then connecting to this will unlock full functionality.
@rs2000 Hello my friend, I’m on an ipad 5 with 48khz and 64 Buffer size, I tried to max it. I hear Improvements in the Moog’s and the whatnots but some App’s stay behind(I think).
I was testing with a controller straight to the camera kit and headphone jack, and I’ve got to say, when I alternate the keys as fast as I can, I hear the other as I’m pressing the next.
It’s all about stabs for me so it’s time to move on. I love the FX section though
This sounds to me like if you have an issue with your setup because I am sensitive to latency also and never experienced something like this. Did you try to restart your iPad ?
Other than that, I found that Korg Module has always been very responsive.
Just remembered you may be able to try the one in Module for free for 7 days.
Roger that monsieur @TimRussell! Thank you for the tip!
@Paulo164 I was playing really fast to test it! I knew there was always something, It would only be noticed if playing really fast stabs(like funk), I never tried to alternate that quick. I bet its the difference of some miliseconds, amounting to a feeling. Imagine how fast neurons are shooting an impulse to touch a key, its no fun to be slowed down any amount.
House Mark 1 and moog model D definetly seemed faster. Back to learning Xequence 2 for me so I can bypass this stuff and plan out some tunes
Boink oink goes the drum machine
@BCKeys hei man, thanx for the follow up! Im on ios15. NSK must be like 7ms more latency, I imagine Im at 8-10ms with Model D and House Mk1. . Its more like a feel, but its a bad feel when i like to slap the keys around.
Im at the stage where in learning Xequemce 2 and think I might get more things done just switcing between that and AUM.
I wan’ted a Roli block to not get caught up in the sequencing with KSP, but they are not to be found and I don’t know if I trust the latency gods yet TBH
There are 2 kinds of latency: audio and midi.
Audio with an external interface gives fairly common results, regardless of brand.
Onboard audio always has a Apple‘s output processing in between, even if „processing“ is disabled, so fastest response is to be expected from an external interface.
The main parameter (buffer size) may be set by the host app (Audiobus, AUM etc) and that will rule the system then.
To get minimal latency with a standalone app, you may switch off the host app completely.
(probably unlikely with so many AUs today...)
You have to try out lowest settings for apps individually, as not all are created equal.
(settings may increase if (glichfree) recording is required)
You probably overlooked the midi aspect until now...
Latency depends on the controller itself, the processing of the receiving app and it‘s response.
Again, not all are created equal.
With your audio buffer set to 64 samples, a simple midi event may drift 1ms by clock alone, which in worst case could easily double your perceived latency (44 samples equal 1ms at 44.1k).
There‘s a huge variety in midi performance and it‘s quite an effort to record and analyse midi data to get a correct clue.
(just mentioning this, so you don‘t flog a dead horse by focussing on audio only)