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.
Impact of latency and buffer sizes in AUM if not worried about audio input latency?
When using AUM I tend to use a 256 buffer when plugging my guitars in to process or record. If I am not using any external audio inputs, what is the impact of high latency 1024 buffer sizes? Like, if I am just using lots of sequencers, synths, fx, but no guitar, what am I losing by bumping up to 1024 and not playing anything live? Is this just impacting latency between the AUM keyboard and a synth for example? MIDI controller latency? Bluetooth MIDI latency? Thanks! Trying to see how much I can squeeze out of my older devices now that I plug my guitars into recent iPads that I keep at 256 or lower in AUM.
Comments
It's pretty simple. The higher the buffer the longer it is between when you hit a key on a keyboard or tap the screen and when you hear the sound. Bluetooth MIDI latency and MIDI Controller latency are unaffected.
Theorizing about it isn't as useful as simply trying it out. People have different tolerances for latency. If you play notes and the lag until when they sound bothers you then the buffers are too high for that purpose.
You can always lower buffers when playing live and crank them up when just listening or tweaking / mixing. Lowering buffers may mean you need to idle some plugins while playing to keep the CPU from maxing out and causing crackles.
Yes, that's basically the only disadvantage of using higher buffer sizes.
Indeed it's a good idea to keep buffer sizes at higher values to give the older CPU a bit more time to process audio. Still, it can't do any magic, if you're using too many or too cpu heavy plugins then no audio buffer size will prevent clicks or dropouts from happening.
Thanks @wim and @rs2000! I knew you guys would give me the goods. No shade on other folks but I was pretty certain you two would respond, hah!
So with my more generative music sessions without external audio input this lqtency looks like a small impact since I'm not trying to do anything that needs razor sharp response. It's been my experience but I wanted to check my gut with you guys.
Interestingly enough, if my buffer is maxed at 2048, spacecraft stops working. Any idea why that is, and what other apps may not play well with such large buffers? Just curious.
With my older ipads, a synth, spacefields, and my guitar max the cpu when I'm at 256. Not that spacefields benefits from low latency playing anyhow....not convinced that my guitar sounds better than me reciting the alphabet into it. There's a ghost in that machine.
Some apps for whatever reason don’t work when the buffer is maxed out in which case it is worth contacting the developer.
Ah, so sounds like this shouldn't be a problem from a technical standpoint? I might reach out... Know @deltaVaudio is busy on spacecraft 2 but maybe he can take a look at how spacecraft in aum won't work with a 2058 buffer.
It's just a programming thing. The default maximum buffer size an app supports is below 2058. Unless a developer remembers to set this to something higher it will fail. It's just a somewhat commonly overlooked thing and should be a pretty easy fix.
@deltaVaudio seems like this could be a very quick fix if you don't mind looking at allowing spacecraft to use the max 2048 buffer!