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.
Audiobus buffering overridden to 470 when using external interface at 48k/24
Has anyone seen this? Is there a fix other than reducing to 44.1k/16 on the interface? I appreciate that 44.1 / 48 * 512 = 470 - just surprised it's being overridden.
Comments
No takers on this one ? :-/
Well, iOS itself takes a parameter in seconds for the requested buffersize when the software configures it (not samples), so there is no guarantee of a power of 2 buffersize, although I would have expected it, as you did.
Where are you seeing that buffersize reported anyway?
I plugged in an iConnectivity device set at 48k/24 and that's when it showed up. Hadn't tried that before with Audiobus - have always used 44.1/16 until now with Audiobus.
It appears to work. However, I am getting some clicks. I think that's from resampling 44.1->48 and not an audio interface issue although it might be just a buffering issue with Audiobus being at 470.
It's not terrible - one click every few seconds - but it's not usable either. Running various synths standalone, and within an Auria session at 48k, I do not hear the same clicks.
So, I guess that negates using Audiobus chains at anything other than an audio interface setting of 44.1/16 - which is what I have done thus far anyway; I was just was checking on 48k/24. I was checking on whether I could run the interface at 48k/24 since all devices in an aggregate have to be the same sample rate / bit depth.
Worth some more investigation though in case I'm missing something perhaps. Anyone any other thoughts?
I repeated the tests yesterday in a more controlled fashion and it does appear that one cannot safely sample at 48/24 using an external interface with Audiobus running, although standalone apps do appear to not suffer from the clicks. I ran Animoog standalone and it was fine. I ran it - by itself - in Audiobus in the input slot and I reproduced the clicks. Running at 44.1/24 seemed OK however.