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.

AUM AUs suddenly stop working when using modstep

Hi guys, I'm sequencing 8 instances of Ruismaker hosted in AUM with modstep. Each drum has it own channel.

Randomly all the AUs stop working in AUM. Each of them goes red and you have to reload.

This is not only annoying but a real workflow killer.

I've just brought a new iPad Pro, the small one. CPU meter in AUM is around 12%.

@brambos any idea what the problem is here.

Has anyone else experienced this issue?

Comments

  • edited January 2017

    I don't think the AU subsystem is entirely stable yet. From time to time it will go down in every AU compatible host I've tried.

  • I have noticed the same, in all hosts too. Further to that, I've also noticed that some apps need to be loaded in AB first, and routed to AUM, to work at all, whereas some others don't play nicely at all if I do that. This leads to a rather complicated start-up routine where I have to start things in "the perfect order". Even then, the AU-stopping-thing might happen.

  • I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

  • @brambos said:
    I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

    Because I want to use sends / effects. And use modstep to control the sends.

  • @brambos said:
    I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

    Do you know if you can control both Ruismaker and an effect on the same channel in modstep. Pretty sure the cc data only goes to the first AU on the channel

  • @Dchild said:

    @brambos said:
    I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

    Because I want to use sends / effects. And use modstep to control the sends.

    Panning is kinda nice to have too.

  • @wim said:

    @Dchild said:

    @brambos said:
    I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

    Because I want to use sends / effects. And use modstep to control the sends.

    Panning is kinda nice to have too.

    although if you own Zmors Eq you can just use it as au to add panning in modstep itself.

  • Yes, but annoying overhead. I got used to hosting everything outside of modstep back when it crashed all the time. Sure it's more stable now, but I still don't trust it all the way yet. Besides, there are lots of other reasons (AudioBus state save, app switching, AudioBus Remote, AUM routing and sub mixes, AUM's small, targeted built in FX, the ability to run ModStep on a separate low-powered device while doing the heavy lifting on another ...)

    But yeh, when messing around with ideas, just loading up into ModStep is a lot more streamlined.

  • @brambos said:
    I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

    Same experience in modstep. After a while all 8 instances stop working. Other AU's keep working.

    I'm using a iPad Pro. Latest OS.

    Let me try with Ruismaker fm.

  • @Dchild said:

    @brambos said:
    I have no idea.. I haven't seen a Ruismaker crash for months. But why not host directly in Modstep?

    Same experience in modstep. After a while all 8 instances stop working. Other AU's keep working.

    I'm using a iPad Pro. Latest OS.

    Let me try with Ruismaker fm.

    Looks like it's the buffer size. 256 it bombs out after a while. 512 is fine.

  • edited January 2017

    Ruismaker supports buffers up to 4096 frames, so I have no idea why that would cause an issue with the plugins.

    Is there an Audiobus session active when it happens?

    Any other hints to help reproduce the issue?

  • @brambos said:
    Ruismaker supports buffers up to 4096 frames, so I have no idea why that would cause an issue with the plugins.

    Is there an Audiobus session active when it happens?

    Any other hints to help reproduce the issue?

    No audiobus... just 8 instances of Ruismaker in modstep or AUM. Buffer size 256.

    It bombs out every 15 / 20 mins. All the other AU's are fine. They continue working.

  • @Dchild said:
    No audiobus... just 8 instances of Ruismaker in modstep or AUM. Buffer size 256.

    It bombs out every 15 / 20 mins. All the other AU's are fine. They continue working.

    Ok, I have Modstep session running now. Let's see what happens.
    Just did a similar 45 minute test in Cubasis without issues.

  • @brambos said:

    @Dchild said:
    No audiobus... just 8 instances of Ruismaker in modstep or AUM. Buffer size 256.

    It bombs out every 15 / 20 mins. All the other AU's are fine. They continue working.

    Ok, I have Modstep session running now. Let's see what happens.
    Just did a similar 45 minute test in Cubasis without issues.

    Are you modulating each instance? I have lots of cc data going on?

  • edited January 2017

    @Dchild said:

    @brambos said:

    @Dchild said:
    No audiobus... just 8 instances of Ruismaker in modstep or AUM. Buffer size 256.

    It bombs out every 15 / 20 mins. All the other AU's are fine. They continue working.

    Ok, I have Modstep session running now. Let's see what happens.
    Just did a similar 45 minute test in Cubasis without issues.

    Are you modulating each instance? I have lots of cc data going on?

    1+ hour, still chugging along nicely without crashing.

    No CC modulations going on in this particular test, but I see no signs of issues here with normal note triggering for longer periods of time, running many simultaneous instances.

    Are you using MIDI CC or AU Parameters for modulations? Are you also doing those kind of modulations on the other AUs? When hosting in AUM, are you sending the modulations from Modstep?

    Edit: I'm now continuing the test with MIDI CC modulations on some of the channels...

  • @brambos said:

    @Dchild said:

    @brambos said:

    @Dchild said:
    No audiobus... just 8 instances of Ruismaker in modstep or AUM. Buffer size 256.

    It bombs out every 15 / 20 mins. All the other AU's are fine. They continue working.

    Ok, I have Modstep session running now. Let's see what happens.
    Just did a similar 45 minute test in Cubasis without issues.

    Are you modulating each instance? I have lots of cc data going on?

    1+ hour, still chugging along nicely without crashing.

    No CC modulations going on in this particular test, but I see no signs of issues here with normal note triggering for longer periods of time, running many simultaneous instances.

    Are you using MIDI CC or AU Parameters for modulations? Are you also doing those kind of modulations on the other AUs? When hosting in AUM, are you sending the modulations from Modstep?

    I'm using CC data. No im only modulating the ruismaker instances. When hosting in AUM I'm sending modulation via modstep.

  • Now feeding a ton of CC messages into the plugins and changed to 128 frame buffers. Still no issues :/

    I wonder if there's a difference (bug) in the iOS AU system on Pro iPads versus regular 'Air' iPads?

  • @brambos said:
    Now feeding a ton of CC messages into the plugins and changed to 128 frame buffers. Still no issues :/

    I wonder if there's a difference (bug) in the iOS AU system on Pro iPads versus regular 'Air' iPads?

    Thanks for testing. I've moved over to modulating via AU rather than CC. Everything is working fine now. How weird!

  • edited January 2017

    @Dchild said:

    @brambos said:
    Now feeding a ton of CC messages into the plugins and changed to 128 frame buffers. Still no issues :/

    I wonder if there's a difference (bug) in the iOS AU system on Pro iPads versus regular 'Air' iPads?

    Thanks for testing. I've moved over to modulating via AU rather than CC. Everything is working fine now. How weird!

    That's good to know! And indeed very weird. I'll let it run for a bit and see if it hits something down the line.
    The nasty thing about these kinds of issues is that if I can't reproduce them, they're nigh impossible to fix... :/

Sign In or Register to comment.