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.
Higher latency on iPad?
![[Deleted User]](https://secure.gravatar.com/avatar/36d439eb701e99bd5d8d8e6482bb9ee1/?default=https%3A%2F%2Fvanillicon.com%2Fce330bfb1498774595298a44e6df3db5_200.png&rating=g&size=200)
When i compare f.e. ThumbJam on my iPad and iPhone 5 the latency on the iPad Air is more than 2X all with the same settings andviOS 7.0.4.
Comments
You mean the setting in Audiobus?
How are you measuring it, Galaxyexplorer? Is this with or without using Audiobus? In TJ if you go to Prefs->options what does buffer size say?
I tryed it without Audiobus. For example when i set it to 128 the output latency says on my iPhone 6.2ms (but before iOS 7 i had here 5.8). The same on my new iPad Air says 21ms. If this true and the case in general on music apps.... that's a bummer for my live records. Another thing i "explored" i can't set MultiTrackDAW to 24bit96khz.... it's still red like on my iPhone 5. As a newbie to iPads i wonder. I thought the iPads can handle 96khz?!? I hope this are just bugs or so..... otherwise it's a step back
Where does it say that? Which app is displaying it?
Also: every app needs to support the latency setting that you're choosing. Few apps actually support less than 256 samples buffer size and even fewer support 96Khz.
He may have got a reading from his tricorder
sonosaurus mentioned it above. With Audiobus it's the same. Now i wonder if there is in general a 2X latency output with all music apps on the iPad Air! I have the feeling it is
MultiTrackDAW supports normally 24bit 96khz (or i think so) but i can't enable it on my iPad Air, just 48khz. Does that mean now the iPad Air can't play/record 24bit96khz? The problem is there is no information to find from apple about such things. Perhaps i'm just doing something wrong. At the moment i have the feeling that beside the new cpu power all other things are a step back when it comes to music production. IOS 7 (7.0.4) is not really good on the iPad. All works better on my iPhone 5 with less than half of the power.
How are you reading the latency figures of 6.2ms and 21ms? What app shows you that information?
Can someone confirm if i can really (or not) record/play 24bit96khz audio in Auria on the iPad Air. Want to buy it but only if i can use this feature. I really can't get MTDAW to do this...... but normally it should work or?
@Sonicflux: ThumbJam - Prefs - Buffer Size - there you see an output latency - not sure here if it's really the true output here but how i said, the iPhone has here 6.2ms and the iPad Air more than 2X..... i hope that's not true. Perhaps sonosaurus can confirm it. I was just curious and would expect less latency on such a new powerful device.
Why should anyone answer your questions when you blatantly ignore other peoples'?
Ignore other people.....?
You can set Cubasis to record at 24/96 on ipad air.
Thank you! Good to know.
Good spot tho on the latency thing.
No one saw that one coming.
Could you actually hear the difference first and then investigated it or did you stumble across it,GE?
Yes, the repeated questions about where you get your latency readings...
@PaulB, I think he did address it, but I believe it was an edit to a post - GE said "ThumbJam - Prefs - Buffer Size - there you see an output latency - not sure here if it's really the true output here but how i said, the iPhone has here 6.2ms and the iPad Air more than 2X...."
I thought there was a comment earlier about what was possible in MTDaw but not seeing that post anymore.
It's tough when you get frustrated to listen to what anyone else is saying, or at least it is for me. Once I hit the "throw my ipad" stage, I'm not trying to listen to anyone. For better or worse, that's the way my simple brain is wired. (Not that you're even guilty of this GE, just saying how I am)
A bit of booth. I had the feeling that i'm going on the iPad more often out of key (i play 95% of my sounds live, i don't use midi editing normally). This could be also perhaps just of the big change from iPhone 5 to iPad Air.... but then i looked into ThumbJam and saw that there is also a big different there. How i said, i still hope really that it's just my fault.
And my bad english does the rest.
@PaulB: Patience is not your strong eh' It was answered before like boone51 said.... and yes i also did an edit. Sorry i'm slow digital writer. When i'm writing one post there are still 3 new after ianswerd the first
Yes, big edit to that post. Originally it was more of a "Is anyone going to answer my question or what?" post.
To be honest, if you reach the point of not listening, there's no point in asking questions, since you have to listen to hear the answers.
No problem.... i'm also still an social network newbie
But this is and air feature.
I'm running same ios on ipad 2 and air and my latency numbers are the same as GE.
Sorry for the Star Trek reference earlier..didn't help but i couldn't resist. .
@GE My patience wasn't really an issue. You had posted. Your post seemed impatient. At that point you hadn't answered a question that had been asked by 3 people, so I pointed out what you were doing. You then changed your post to make it look like it hadn't happened the way it did.
I'm cool, but I'm also a fan of the truth.
@commonstookie Your comment was the one redeeming feature of this thread.
@PaulB: Nope! It was even aswerd before your post. And the editing was made while you post your off topic comment. Very cool. I'm a bad liar, yes...if you feel better. So i go sleeping.... not that you say i ignore you the next hours.
Well if that's the case then I apologise for drawing the wrong conclusions. I responded to what I saw at the time.
@PaulB: No problem at all. I sometimes also sound a bit harsh. I unterstand why you did this.... it's O.K.
I also thought sonosaurus still gave the answer in the third post. My english..... However, all is fine.
Actually, GalaxyExplorer's edit appeared well after he posted "Ignore other people?" in response to PaulB's comment.
Not trying to start a flame war. That was the chain of events, though, because I was very curious to know where to find the latency data. It frustrated me too that GE hadn't answered the repeatedly asked question.
I don't understand half this thread. But I can record in MT DAW at 2.8ms/24bit/96khz settings on my Air, if that helps...
OK, for this kind of test you'll want to be sure all your apps are killed first. Then start only ThumbJam. Go to Prefs->Options, note what the buffer size reports, and then report the output latency, as you did. Then change to a different buffer size and report the output latency for each. The output latency figure is computed by asking CoreAudio Session for its CurrentHardwareOutputLatency property and adding that to the duration of the buffer size at the current sample rate. That property gives the additional amount of latency built-in to the particular audio interface being used (independent of buffer size).
For instance on my iPad3/iOS7.0.3 :
(So, the hardware latency beyond the buffer size here was 3.8ms for speaker, and 3.1ms for headphones/line out, for example)
And on my iPhone5/iOS6.1.4:
(and the extra hardware latency here was 4.4ms (sp), 3 ms (line)).
If you were to connect your bluetooth headset as the output, you would see these output latencies go way up. It is interesting to note that using the built-in speaker vs headphone/line out makes a small difference.
So, if people want to report their findings like I did above on the various new devices, that could be very interesting. Just be sure to kill all other apps beforehand (or a fresh reboot), just in case. Report device, iOS version and audio path (speaker, line out, external USB audio interface, etc). Note if you plug in headphones or other audio device, leave and come back to the Prefs->Options page for updated values. Since the buffer size part of the math is constant, you only really need to report your values for one choice.
Also, none of this accounts for the actual touchscreen event latency pathway when performing in a real world scenario. A measurement test of finger tap-to-audio output is the only real way to see how the new devices really perform, if that is what you are concerned about.
Thumbjam:
iOS 7.04 - Buffer size 128 - speaker output
iPad Air: 18.1 ms
iPad 2: 6.5 ms
iPhone 5: 6.2 ms
Same config with headphones plugged in:
iPad Air: 6.4ms
iPad 2: 5.8 ms
iPhone 5: 6.2 ms
+1 Chris.
@sonosaurus - you nailed it.
.