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
.
Latency is a weird thing, especially for live use. Some people are really sensitive to it (pocket players) and others don't seem to care until it gets really bad (strummers). So it's kinda hard to gauge from other's opinions. You almost have to try it for yourself and decide if it is tolerable. But latency is also additive so by adding more converters/DSP monitors/etc. it can creep up on you and what was once tolerable can become a distraction.
I just restarted (didnt before) and its now providing what looks like more reliable results. Now I've got:
iPad Air speakers:
128: 18.1ms
256: 21.0ms
512: 26.8ms
1024: 38.4ms
With headphones in:
128: 6.4ms
256: 9.3ms
512: 15.1ms
1024: 26.7ms
personally I haven't noticed any noticable lag via speakers.
I ask me if the old (and new mini) have the same). If i understand it right it's the speaker output. The Air and mini have stereo speakers while the iPhones and iPads have/had mono speakers. Mmhhhh, must go work. I have to do some test at the weekend.
My results are exactly what JamMaestro got. After reboot.
@AlleycatLA: ditto here on my Air 7.0.3. My iPhone 5 6.1.2 is showing 7.3ms through its speaker and is noticeably more responsive. Playing a simple drum groove on the Air is much more difficult- so yes, I for one can definitely feel the difference.
I'm a little disappointed that this is the case in Apple's latest and greatest machine, but then again I usually prefer working with headphones or speakers anyway. Would love to know exactly what's going on here...
I would like to repeat the question:
Is anyone actually experiencing this lag when playing? This is the stuff that rumours are made from.
.
@Sebastian: yes without a doubt, see my last post.
.
This is just playing the Drums preset in ThumbJam.
.
Just had TJ running after a reboot.
FWIW I have experience with latency, using my bass to control synths in a Roland GR55 (which has significant latency on thicker strings). Try playing syncopated lines with alternating measures of real bass sounds (no latency) and synth bass (probably 20-30ms latency depending on string played). You're forced to get a feel for it real fast
Mike made a video about how to test latency. It would be nice if you guys could try to reproduce this potential latency issue this way:
That's really fascinating, Sebastian. How could I make this work with ThumbJam's internal sounds instead of the external (clicking) sound?
Could the latency algorithm or reporting to the Air speaker output be impacted as its the first stereo speaker ipad? Just a random thought...
The original iPad Mini had stereo speakers. Can anyone with the device confirm or deny?
"yesterday we didn't have a problem with the Air" / Simon
Umm? There are so many problems with the Air and iOS 7 right now it's not even funny.
About the latency, if I'm doodling around on the iPad or iPhone, I don't really notice the latency. At least not as long as the buffer sizes for everything is 512 or lower (whatever the latency in ms might be). Playing on a keyboard and things could be different depending on how/what your doin
.
If the issue is limited to the internal speaker output only, as it appears, I am not too worried about it. None of us here seriously uses that for anything important, I hope.
It would be nice to get some measured audio latencies for external clicks, as in the video or on separate channels. It should also be possible to capture a midi in using 96khz sample rate, at least enough to see a note on begin and end. I would expect variation with the app there. Would be very interesting to quantify. I used to do a lot of that with oscilloscopes but don't have my old gear
A really interesting experiential way to check through latency on headphones is to route an original signal in one ear and the output signal on the other. Best if you have a switch to alternate between original and output on that side. With levels balanced, what you'll find is that as little as 0.1ms will make the apparent pan shift dramatically to the undelayed side. Learned this trick as a test tech on early digital delay lines.
The burning question in my mind... How can this thread exist on such a technical level (for latency) when the problem seems to only show up in an entirely non-technical use ( playing music thru the crappy iPad speaker)?
I'm so confused, but also intrigued, because of the geek factor
@Yendor: I mentioned it above too.... perhaps it's because of stereo speakers. I don't know.
I think i'm just to dumb for this and it's still all new. So i will not start again a thread or question. Sorry again, maybe i'm wrong in such forums with my questions. Yes, i got more help from others then i could gave back. I apologize for this too. I really appreciate all this answers. My bad english and all the others things......yep, time to leave 
@Sebastian: Yes, with headphones it's good, but i thought i could record something just with the internal speaker if my ears get tired.... then i feel a bit of latency. Of course just with very short attack sounds.
@sonosaurus: Yes, it's not the most important thing but it would just be cool if i could record some things just while listening to the speakers with the same low latency.
To all others here: Uhhh sorry, i didn't thought that i open such a large thread. I apologize for my many dumb questions which seems to be confusing some people too. I think i know when it's time to leave
Sorry, regards.
Galaxyexplorer
No don't leave! This is part of the fun of iOS music, discovering its limitations and quirks. I've found this thread both helpful and entertaining, even if a bit superfluous in the end. ;-)
Edit: and true, there are times where it is useful to just play with the iPad speaker to avoid headphone fatigue. So, sorry if I made it seem like it is not a useful issue to explore.
@Galaxyexplorer I would take it all with a pinch of salt.
Written communication especially forums can be interpreted in an almost endless variation of ways causing confusion and misconception with skewed context to boot.
I am using a Samsung 49 midi keyboard and the latency is barely noticeable to me irrespective of any facts or figures.
It's probably one of the many odd IOS 7 bugs yet to be exterminated.
Edit:Samson !
Your questions are not dumb.
The thread is long because what you asked is of interest to us all and you were the only one who spotted that.
@Galaxyexplorer - you're wrong! Your contributions with your music have been very valuable! You've given back to the forum in a significant way, and I hope you stay with us.
If you are not an actual live musician who actually knows how to play a traditional instrument acoustically, I don't see how you could notice a problem with latency because you would have no expectations to compare it to. Those who can will notice, and it can be a problem for them.
My spider senses have been tingling about the ipad air and mini air ever since they were announced. Now that displaymate has crushed the IGZO displays and now latency issues are effecting the device (which has been the scourge of Android devices up to this point and a rich source of criticism), they better seriously wow me with some quality control on the ipad pro or I'll be hanging with the apparently extraordinarily capable ipad 4.
@Galaxyexplorer Don't go! Please continue to post stuff like this when you find it! I think it is important to examine these things and know our hardware and software inside out. The more we know, the better! For example, one thing that I'm beginning to realize with all of these different bugs we've seen lately, is that each hardware version of the iPad & mini seem to require something slightly different code-wise. Developers can't always just write and have something work on all devices--adjustments in code needs to be made for compatibility with various devices it seems..... Lots of things, like this thread help our understanding! :-)