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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

CPU usage Drambo vs AUM - is there difference?

[Deleted User][Deleted User]
edited December 2022 in General App Discussion

how to run max number of auv3 simultaneously with low latency (live playing), I mean is Drambo the same capable like AUM? iPad Pro 4-th iPadOS16

Now I discovered AUM multicore usage page and I know Cubasis3 have also support for multicore, but I have no M1 cpu, and until now I ignored multicore at all…. but maybe I missed something?

Comments

  • uncledaveuncledave

    I don't believe AUM actually uses multicore processing; it just detects which physical core the DSP thread was run on. Also, CB3 only uses multiple cores for background rendering, not for live playing. So, all the AUv3 hosts should be essentially equivalent for live playing.

  • [Deleted User][Deleted User]

    Thank you very much for response.👍

  • wimwim
    edited December 2022

    There's no way to measure that except by actual testing with the plugins you use. Each host should be loaded up with the same midi sequences and sample rate / buffer settings. Then each should be run and loaded with more and more plugins until it starts to fail.

    Just midi sequences may not give an accurate enough measurement. Changes to plugin parameters and automation are important factors too. Tests should be as close as possible to the performance scenario.

    iOS doesn't have any tools for performance measurement that are of any use in this scenario.

  • MisplacedDevelopmentMisplacedDevelopment

    I know nothing about the iOS scheduler or its APIs so what I say here is conjecture based on what I know about other systems. If the hardware uses multiple processing cores then a host or DAW needs to be coded to make use of those cores. Presumably there is some necessary use of multiple cores such as having the UI on one thread and the audio stuff on another but if you want to run plugin x on its own thread then I believe that the host needs to be coded to do this. I only know of Cubasis that does this on iOS, and with the limitation (which I was not aware of) mentioned by uncledave.

    Now, if you run two plugin hosts or DAWs at the same time, such as AudioBus and AUM, then in theory you might be able to squeeze a bit more out of your CPU, or at least give it more breathing space, by splitting plugins across hosts. This assumes that the extra base CPU and RAM overhead of running more than one host does not outweigh the gained ability to saturate the available CPU with extra plugins. Your iPad Pro is pretty recent so I would think that this would be worth trying. As these are separate hosts then, again in theory, the OS should run them in parallel on separate threads rather than forcing everything through the limited number available when using one host. It might even be the case that adding a third host, e.g. ApeMatrix would let you scale further.

    The problem with this is that it quickly becomes complicated to manage and synchronise unless you can logically group plugins to specific hosts and it adds quite a bit of extra risk, especially if playing live and the OS decides that too much RAM is in use and does something unfortunate to one of your running hosts. You are also competing with any background OS tasks which might be making good use of the ‘spare’ cores, for instance having wifi and bluetooth enabled is going to cause background processing which will eat up at least some CPU cycles.

    Hopefully someone with enough internal knowledge will be able to correct my view of this if it is wildly out of step with reality!

Sign In or Register to comment.