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.

Strange IOS cpu allocation?

When I run a guitar preset in AUM composed by a nembrini amp+ delay+ roughrider+zeroverb, I get a dsp 103% and clicks and pops.
However I have for example other preset where I havea preset with 6 AUM channels (sampletank+Noise+layr+mobile pod+pure synth+zeroverb) and AUM shows a dsp of 51%! even while Im running in the background Midiguitar which is running inside +- the same previous AUM preset (nembrini amp+ delay+ roughrider+zeroverb) with midi out playing all the AUM mentioned synths and 0 clicks.
How It can be possible?
Obviously IOS is doing some weird things while assign tasks to the different cores, but its very frustanting when I want to use the preset mentioned at the beginning in AUM and get clicks when its clear that my Iphone can have enough cpu for much more than this.
There is a solution for this?

Comments

  • Try taking one app out at a time until you see the CPU problem go away.

    Probably RoughRider. But there’s only one way to find out.

  • @wim said:
    Try taking one app out at a time until you see the CPU problem go away.

    Yes. AUM is the testbed for CPU performance. You can keep adding instances of
    one app or combinations of many and keep an eye on the CPU/DSP numbers.
    When you hit 100% consistently then see if one of the apps is the primary contributor to
    that status. That's an app you want to use carefully.

    And I must admit I have gone crazy and purchased 2-5 instances of most FX functions and
    have so many synths and sampled-instrument choices I can usually find a better fit.

    Sometimes I realize I really can't hear a difference in a mix when one of the apps is in or out.
    When that's the case I toss it out.

    I recently installed an AUM project from @echoopera that just killed by 2018 iPad... he probably has an iPad Pro with more cores and RAM. So, I started pulling apps out of the project and was able to get a stable project and since the style was random ambient I can't tell a difference.

    But "slide to the left" on any app will quickly expose the real CPU/DSP culprit. FX'es will continue to process and generators/instruments will shut down that track.

  • edited August 2020

    Not sure if I have explained it correctly, I dont think its an actual plugin problem, because I use exactly the same plugins (included roughrider because its the only compressor I have) in Midiguitar AND a lot more synths in AUM and I dont have any click and the cpu reads much much less.
    I think its a IOS problem and I suspect it allocates a slow core sometimes, instead of assigning one of the highest performing cores, is not that possible?
    Either that or that it uses several cores at the same time (multi process), which has already been discussed several times that it is not possible in audio applications until we see if it is implemented in IOS14 and is used by developers.

  • Buffer size?

  • edited August 2020

    @espiegel123 said:
    Buffer size?

    128 all the times. I play in realtime with my guitar so I need a low buffer, 128 is very playable to me.
    As a curious fact, Midiguitar works with a fixed buffer of 256, which cannot be changed. But if I start AUM to 128 first MG uses that buffer and it doesn't give any problem (and plays with less latency).

  • edited August 2020

    @jassy said:

    @espiegel123 said:
    Buffer size?

    128 all the times. I play in realtime with my guitar so I need a low buffer, 128 is very playable to me.
    As a curious fact, Midiguitar works with a fixed buffer of 256, which cannot be changed. But if I start AUM to 128 first MG uses that buffer and it doesn't give any problem (and plays with less latency).

    All those examples are with an Iphone XR.
    sometimes it seems to have as much realtime power as my i7 laptop to play all those plugins and synths without messing up, except when he chokes with a preset like the one described in AUM

  • Have you power-cycled your iPhone? What OS version are you running?

  • @espiegel123 said:
    Have you power-cycled your iPhone? What OS version are you running?

    IOS 13.4
    No power cycle, dont think its the culprit here, to make an fair comparison I do all the tests in the same session.

  • @jassy Is this about processing live audio from your guitar and audio interface vs processing synth sounds (possibly controlled by MG)? The live waveform may be more challenging to process. Still, as @wim suggested, you could try to track down the problem component, and maybe find a more compatible one. Also, is the sample rate the same in all cases?

  • @jassy said:

    @espiegel123 said:
    Have you power-cycled your iPhone? What OS version are you running?

    IOS 13.4
    No power cycle, dont think its the culprit here, to make an fair comparison I do all the tests in the same session.

    While it might not make a difference, the behavior is unusual enough that a power-cycle is in order. It might be worth noting that 13.4 has issues solved in later OS releases.

  • Is the difference that in the first case you have the UI for MIDI Guitar in the foreground and in the second case it is AUM?

    I know that some of my apps will cause spluttering and belches when I have stacked up some synth and FX chains if I have their windows open doing some heavy graphical rendering. Even AUM sometimes if I try scrolling while a song is playing.

  • @jassy said:
    Not sure if I have explained it correctly, I dont think its an actual plugin problem, because I use exactly the same plugins (included roughrider because its the only compressor I have) in Midiguitar AND a lot more synths in AUM and I dont have any click and the cpu reads much much less.
    I think its a IOS problem and I suspect it allocates a slow core sometimes, instead of assigning one of the highest performing cores, is not that possible?
    Either that or that it uses several cores at the same time (multi process), which has already been discussed several times that it is not possible in audio applications until we see if it is implemented in IOS14 and is used by developers.

    I've had the same issue before in AUM. My guess was that it's graphics/AU window related in AUM.

  • @uncledave said:
    @jassy Is this about processing live audio from your guitar and audio interface vs processing synth sounds (possibly controlled by MG)? The live waveform may be more challenging to process. Still, as @wim suggested, you could try to track down the problem component, and maybe find a more compatible one. Also, is the sample rate the same in all cases?

    To me All is live and realtime processing, all is controlled by my guitar signal.
    MidiGuitar works also as a auv3 host, in case someone doesn't know how it works, It has two signal paths, on the one hand it converts the guitar signal into midi and controls an internal synthesizer or AUv3 plugin or external by sending the midi to another application.
    On the other, it processes the guitar signal with AUv3 effects. This part of the route is where I use the same effects as in AUM.

  • @Jocphone said:
    Is the difference that in the first case you have the UI for MIDI Guitar in the foreground and in the second case it is AUM?

    I know that some of my apps will cause spluttering and belches when I have stacked up some synth and FX chains if I have their windows open doing some heavy graphical rendering. Even AUM sometimes if I try scrolling while a song is playing.

    I have read about problems while the UI is in foreground but No seems to be that the problem, it behaves the same with the UI open or closed

  • @jassy said:

    @Jocphone said:
    Is the difference that in the first case you have the UI for MIDI Guitar in the foreground and in the second case it is AUM?

    I know that some of my apps will cause spluttering and belches when I have stacked up some synth and FX chains if I have their windows open doing some heavy graphical rendering. Even AUM sometimes if I try scrolling while a song is playing.

    I have read about problems while the UI is in foreground but No seems to be that the problem, it behaves the same with the UI open or closed

    OK, was just a thought based on when mine has problems. Next step would be to follow the advice of @wim and strip it back to where it stops behaving like this to discover what may be causing the spike.

  • I'm not gonna be too big of a help here, but I'll just say that MIDI guitar is FUNKY ever since it's latest big update.

Sign In or Register to comment.