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
@ChrisG, and if you plug in headphones? Either way, that is not promising!![:( :(](https://forum.loopypro.com/resources/emoji/frowning.png)
iOS 7.04 iPad 4 16GB
Thumbjam, speaker output:
128 -> 6.5 ms
256 -> 9.4 ms
512 -> 15.2 ms
Headphones:
128 -> 6.0
256 -> 8.9
512 -> 14.7
WTF!? Seriously? Wow, whats this all about?
@sonosauros I edited my post above to reflect the changes using the headphones plug. Drastically lowered the iPad Air latency..
@ChrisG, PHEW! They must doing some ridiculous compression/limiting on the speaker output on the iPad Air to introduce that kind of latency. That was a close call, folks. Stick with the headphone/line out on those things, as I'm sure you all are anyway![:) :)](https://forum.loopypro.com/resources/emoji/smile.png)
So how come the iPad 2 does so well?...
Uses warp speed..
.
If you have ever been sensitive to the time between when you touch a key (touchscreen or from a midi controller) and when sound comes out, especially when you are playing fast, then yes, a difference of 15ms can be noticeable. Not all people use their devices in a way where this kind of thing matters, but many do.
[Edit] also when using as an effects processor for a live guitar/etc input, this can become very noticeable. Looks like this issue is limited to speaker out on the Air, so it won't really be a problem anyway.
.
So is anyone else using an iPad Air and getting HUGE latency numbers when using the speaker?.......or is this an isolated incident?......or something else going on?
@Simon It's like @sonosaurus said it has to do with key response time. I'll exaggerate, but it will hopefully help...Imagine trying to play a song live, where each time you press a key, it takes half a second to hear a sound. You'd have terrible timing trying to play it live. Trying to get things to sync would be even worse. Of course, sequencing everything and not playing live would solve the problem, but most of us like to play live as well as sequence our music. This is why it is so important, and why Android sucks as an OS platform for musicians......or at least one reason why... ;-)
.
Ahhh....I'm interested in that too. :-)
Edit: I think with numbers as high as @ChrisG was seeing, it goes beyond academic interest, and becomes more of a question of is the number (along with its latency) accurate, or is the reporting wrong....Academic would be, "Hmmm....the latency seems higher on the Air than the iPad 2..." Real World is, "Holy Crap!!! I'm getting this huge amount of latency and I can't play anything, and this is on an Air!" or "Hey, I think I found a bug, because the Air is reporting a huge amount of latency, but everything seems fine!" It may just be my perspective, but for me, it has gone beyond "Hmmm...interesting!" to "Hey, what's going on here!" :-)
Someone please add rMini stats too if possible!
Trying to wrap my head around this latency computation... So the total output latency includes the hardware latency? Or do you have to add the hardware latency to that number? Say you were using an external USB sound card, does it calculate the latency for that too?
I only have DrumJam and am not finding this option. Only ThumbJam has it?
Yes, total output latency includes the hardware's latency. And yes, only ThumbJam has those controls and readouts, sorry! You might like it![;) ;)](https://forum.loopypro.com/resources/emoji/wink.png)
I was pretty skeptical when reading this, but in my own tests:
iPhone 5:
128: 7.3ms
256: 10.2ms
512: 16.0ms
iPad Air:
128: 38.4ms
256: 38.4ms
512: 38.4ms
Not promising. However that fact that all buffer sizes are reporting the same latency suggests something fishy is going on with the reporting on the iPad Air maybe?
I get it. You are subtracting the constants (128 = 2.9, 256 = 5.8, 512 = 11.6) from that total latency to get just the latency of the audio hardware. But, then the iPad 3 example should actually be 3.6ms sp and 2.9ms line for the audio hardware, correct? Having those calculations off made me think some other variable was also being measured or something. So iPad 3/4 are fastest (so far) in terms of hardware latency. Interesting.
@jammaestro - which OS?
So what I'm hearing is that @Galaxyexplorer is pretty much a Jedi.
@Ringleader:he wrote iPad air so i would assume it's at least 7.03
@Ringleader 7.0.3. With headphones in its 26.7ms - again all the same time regardless of the buffer chosen. Not sure why as other people with Airs are getting variation.
Ok thanks just wondering if it was partly due to 7.0.4 or not as that is the only option I have now if I want to explore BIAS. And not being able to try that one is getting to me.
.
Well that's just it. If it is simply displaying the latency incorrectly, then that's hardly an issue. Just ignore it. But if the latency really is in the 20's/30's ms then that is a major issue IMHO. You'd definitely notice that and would be a severe deal breaker for me.
@Simon:I'm also happy that i decided against an ipad air for now.iOS7 runs great on my iPad 4 besides some small known bugs.And yes,a latency from 12-15ms up is something you should notice when you play keyboard sounds with short attack or especially drumsounds.
Here, iPad Retina (4), iOS 7.0.4. Fresh restart
No variation in Airplane mode.
Almost match Sonosaurus report.
EDIT:
Exactly the same values in an iPad 2.
@JamMaestro, and that was making sure everything else was killed beforehand, right? Very fishy indeed. Try it right after a reset, if possible.
A very good question is does it actually feel like that latency?
There are other air owners reporting great results with BIAS, so there can't be a global air audio latency issue. I find it hard to believe that these guitarists who are used to playing dedicated processors (4-10 total ms range) would not notice 20+ ms of latency. This must be due to the 64 bit processor somehow mucking with the reported latency.
Thank you all guys. I didn't notice that... yep, with headphones plug in i get 6.4ms with 128 samples. Interesting. And thx sonosaurus for that feature
I was searching in other apps but you're the own who included this. Indeed iOS 7.0.4