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.

Module Pro doing magic in Drambo (lowers CPU)

mbncpmbncp
edited April 2021 in General App Discussion

This is Dramboing me a bit crazy

I'm on an Air 4, iPadOS 14.4.2 (I had somewhat the same problem a couple of month ago with an Air 2).

I have about 15 auv3 instruments in my project,512 samples, and for some reason I have a CPU spike (full red).
In Cubasis having about the same project I get 3% cpu and 50% DSP, 256 samples, with Multi-Core Off.

Anyway, as soon as I play some notes or just some CC in a track having Module Pro (Korg), the CPU bar in Drambo will go from 5 red dots(and sound shuttering) down to 3-4 green dots :)
So I added a track with an LFO -> CC Generator -> Midi Mixer -> Module Pro and this does the trick, but as soon as I disable the LFO the CPU jumps back to red light district.

Some pics:

In the second one you see that the generated CC is muted and CPU is high again

Weird, no ?

I tried the trick with other AU's, but no luck so far

Comments

  • GravitasGravitas

    I would suggest reporting this on the Beepstreet forum.
    Include a complete list of all the auv3 instruments
    and plugins that you’re using for this project.

  • uncledaveuncledave

    @mbncp You may just be switching between the "low power" cores and the normal cores. To save battery, iPadOS uses slower cores when possible, switching to faster ones when it needs to. So the CPU time required can drop when there is more work to do. Unfortunately, there is no app control over this, and the system doesn't respect the real-time needs of music production.

  • mbncpmbncp
    edited April 2021

    @uncledave said:
    @mbncp You may just be switching between the "low power" cores and the normal cores. To save battery, iPadOS uses slower cores when possible, switching to faster ones when it needs to. So the CPU time required can drop when there is more work to do. Unfortunately, there is no app control over this, and the system doesn't respect the real-time needs of music production.

    Yes, that’s the first thing that came to my mind, that’s when I added the 2 moog synths. But then it started really to max out, loosing audio buffers.

    I’m sure that on my air4 there is (at least) 2 hispeed cores. I think that CB3 is using one for GUI stuff and the other for dsp or more when multi-core is enabled, and I never had these kind of problems. IMO, I think that a host can decide which core to use, otherwise how cb3 would do it.
    I maxed out cb3 with 32 different instruments, but I think I had a 512 samples buffer

    Also does this mean that Module Pro uses a huge amount of cpu, just by receiving an unused cc every second ?
    Again I didn't see this on any other plug (3 factory, 2 aparillo, 2 synthmaster one, drum computer, egoist, model D, model 15)
    But it works(lowering the cpu) using any of the 3 module pro.

    Edit: just tried to add 2 model D to see if the cpu would warm up, lol, I ‘m now in avant-garde post neo contemporary music :)

Sign In or Register to comment.

© Vanilla Keystone Theme 2025