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.
Trying to set Sample Rate in AUM - error message
Trying to set the sample rate to 44 in AUM, but the error message is : "Could Not Set, Either Hardware does not support or another application is currently controlling it"
It is an iPad iOS 14.7.1
Could not find any other apps running, so I am assuming it is being controlled somewhere in the System, but I cannot locate where to change it in System settings.
Any ideas?
Thanks IA
PS: oh and there are no apps running in AUM - this is at app startup, nothing loaded.
Comments
If your iPad is any model after the 2018 iPad 6th Generation, then it's 48kHz only, if not using an external audio interface. You may be able to set it to 44.1kHz when using a 4-pole headset (not 3-pole headphones).
Wow! I did not know that...I wonder what boffin at Apple decided that??
Audio is set to an external device (Flow 8 Mixer).
What type of iPad do you have?
Try a headset with the headphone jack (or the Apple Lightning/USB-C Headphone Jack Adapter) and see if it lets you set apps to 44.1kHz. I believe it was Dendy here on the forum that discovered that with his Air 3/Mini 5.
I never tested it on the 2018 and later iPad Pros without the headphone jack. Still curious if it'll switch like the Air 3/Mini 5.
Thanks I'll try that. Its a 2021 model
EDIT: nope tried that same same
Seems I am like others (from research) that when I plug in an interface, I can run AUM at 44khz, plug in to the headphonce jack, ONLY 48khz. Its a pity with the Flow 8, even though it's using the lightning port, AUM will still only allow 48khz - Must be the FLow being fixed at that rate Ii guess, haven't checked but there's nothing in the apps to change it.
Looking at the Behringer Flow 8's manual, the USB audio recording is 48kHz, with no other sample rates shown.
Does AUM see all 10 of the Flow 8's inputs?
And just curious, why do you require 44.1kHz?
Since found out it IS fixed at 48khz. The way works is it presents two pairs of stereo audio ports, or four mono ones. They can be recorded discretely. You can route these to channels on the mixer or to the monitor sends for live work.
I am using AUM Mixer and on occasion Camelot Pro on the iPad, both of which will not allow the sample rate to be changed as it is "controlled" by the Flow 8 - higher sample rate means higher intensity for the CPU even with one AUv3 instrument loaded. I am seeing CPU loads of up over 70% , and while not alarming does also mean shorter battery life and increase the possibility of audio glitches. I am totally fine with 44kz, especially for live work...44khz will mean a reduced load on the CPU. It is an A12 Bionic chip btw.
It has been logged as a user request to Behringer (not by me) to provide both 44khz and 48khz options in a future update. Although I am not sure it can be achieved just by firmware, I suspect a hardware change would be needed as well.
@pax-eterna You'd need run a lot of synths/fx to load an A12 to 70%. What you're probably seeing is 70% load on its low-power cores. It won't invoke the high-power, high-performance cores until it needs to. This means that the monitored CPU load cannot always be relied on.
ahhh, ok thanks for that info. So that 70% I am reporting is not a real reflection on exactly what the processor is doing.
Very good to know!
Yeh, it's the percent of available CPU at the time. iOS allocates this dynamically, with priority on battery life and temperature. So, a higher percent can actually be indicating lower usage. You never know.
I doubt that the difference in CPU usage (and latency) between the two sample rates will be noticeable.
Enjoy your iPad and the Behringer Flow 8 and make some music!
Definitely, the difference is probably less than you might expect from the percentage diff in the sample rate. Much of the processing is vectorized, even auto-vectorized by the compilers, and that will take less of a hit due to the increased SR. Go with 48kHz when you can.
Thanks folks...Yep will just stick with 48k
What does "vectorized" mean in this context? And when you say it will result in less of a hit due to the increased sample rate, do you mean less of a hit than you'd expect compared to 44.1 (but still SOME hit), or do you mean it is actually MORE processor-efficient to run these apps at 48 than at 44.1? And is there a difference in this phenomenon that tends to fall along the lines of certain kinds of apps or usages?
My interest is strictly live performance... no DAW/recording, no inter-app audio processing, just simply MIDI comes in to the iPad from my keyboard, and audio from an app comes out (or perhaps from more than one app, if I'm splitting/layering multiple sounds). I use a combination of straight sample playback apps (for pianos, strings, brass, etc.) and some other sound generation (VA synthesis, clonewheel organ with rotary effect). At a live gig, no one is going to hear a sonic benefit of 48 over 44.1, and I figured the less processing overhead, the better chance I have of being able to set a lower latency without glitching, so I've always used 44.1 when possible. Is this not the best approach? Thanks!
The short answer is that it's complicated and the only way to know for sure is to test with your live rig. I'd still suggest going with 48kHz unless you run into problems.
To answer your first question, vectorized means that it runs on the SIMD unit on the CPU core. (These are often referred to as DSP or vector units too.) The SIMD name means Single Instruction Multiple Data. For lots of audio related processing the set of operations you do are the same for each sample, so you can process a chunk of data at a time on the SIMD unit and it takes far less time than having to go through each sample one at a time. The memory access also happens in chunks, so it can be more efficient too. Some vector operations require certain sizes of chunks and some don't. So, the differences between different sample rates aren't easy to predict without knowing the specific implementation. And just to make it even more complicated to figure out, the newest generations of compliers can auto-vectorize the code and move code to the SIMD unit that a dev didn't write to be there. This is controlled by compilation flags so you could turn it off, but they are really good at it and it is most likely going to be a good thing.
There's also some algorithm related things that go against the lower sample rate always being more efficient. As an example, the filters I use in my xTrem plugin need to run at a high sample rate to be stable at high cutoff frequency. In xTrem they run from ~20kHz down to something like 10Hz in a sweep do the lowpass gate effect. So, I need to run them above about an 80kHz sample rate. If the sample rate of the host is 88.2kHz or 96kHz, I can just go with that. If the input sample rate is 44.1 or 48kHz, then I need to upsample first and downsample on the way out. So, xTrem is more processor efficient at a 96kHz sample rate than it is at 44.1kHz.
Another thing that might come in is that iOS will sometimes need to do some sample rate conversion itself either on the input or the output to match the USB drivers or to match multiple running audio streams before it can combine them. Where this might occur isn't always obvious especially with multiple different audio apps running.