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.

AUv3 Plugin issues only in Loopy Pro?

sydneytdcsydneytdc
in Loopy Pro

A recent Loopy Pro adopter and loving its power and flexibility. Using it primarily as a bass guitar processor at present and will be adding in some rudimentary looping features in time.

I have found a few issues with some plugins that work fine in AUM.

  1. FAC Chorus:
    Works fine but when I change presets, either with Loopy’s User Presets, or the plugins own preset selector, I lose the Wet signal. Only recover is to delete the plugin and reload, or force quit Loopy and reboot.

  2. Mood ClusterFlux.
    No Wet signal at all. Setting plugin to fully wet results in silence. No apparent way to resolve this. Works fine as expected in AUM.

Both developers have responded to my mails saying to contact Loopy Devs for some input.

Loopy v2.0.5
iPadOS 26.1
RME UCX Interface

Comments

  • espiegel123espiegel123

    @sydneytdc said:
    A recent Loopy Pro adopter and loving its power and flexibility. Using it primarily as a bass guitar processor at present and will be adding in some rudimentary looping features in time.

    I have found a few issues with some plugins that work fine in AUM.

    1. FAC Chorus:
      Works fine but when I change presets, either with Loopy’s User Presets, or the plugins own preset selector, I lose the Wet signal. Only recover is to delete the plugin and reload, or force quit Loopy and reboot.

    2. Mood ClusterFlux.
      No Wet signal at all. Setting plugin to fully wet results in silence. No apparent way to resolve this. Works fine as expected in AUM.

    Both developers have responded to my mails saying to contact Loopy Devs for some input.

    Loopy v2.0.5
    iPadOS 26.1
    RME UCX Interface

    FAC Chorus is working fine for me. Can you screen record a d demonstration and show your Loopy Pro mixer in extended mode so that we can see the routing? Here is a video of my using it in AUM then in Loopy Pro so that you can see what I was doing. If there is an issue we’d like to get to the bottom of it.

    Do you know if the developers tried it in Loopy Pro?

  • wimwim

    FAC Chorus is working fine on iOS 26.1 iPhone 12 for me here both as an insert and an FX. I can't reproduce any of the behavior listed.

  • sydneytdcsydneytdc

    Thanks for the quick responses folks. I will try a new clean session, that has less routing and see how that goes. Shall report back

  • sydneytdcsydneytdc

    Update.

    1. FAC Chorus. Creating a new clean session based off the Default sees the FAC plugin working fine as expected. Back over to my pedalboard session, same bug persists - flicking presets, results in Wet signal stopping.

    2. Moog ClusterFlux: No change to behaviour in the new clean session - that is no wet signal at all.

    My session is simple in terms of Widgets, but does have a set of cascaded busses. The purpose is to aid adjustment and simplify the future changes.

  • espiegel123espiegel123

    @sydneytdc said:
    Update.

    1. FAC Chorus. Creating a new clean session based off the Default sees the FAC plugin working fine as expected. Back over to my pedalboard session, same bug persists - flicking presets, results in Wet signal stopping.

    2. Moog ClusterFlux: No change to behaviour in the new clean session - that is no wet signal at all.

    My session is simple in terms of Widgets, but does have a set of cascaded busses. The purpose is to aid adjustment and simplify the future changes.

    Can you try replacing the FAC Chorus clone instances with separate instances and see if the issue stops happening and let me know?

  • espiegel123espiegel123

    @sydneytdc : I was able to confirm that when using cloned FAC Chorus instances that changing presets has the problem you mentioned.

    I don’t have ClusterFlux to test with. Do you have the problem with just a single instance of it? Does the sample rate or buffer size make a difference?

  • sydneytdcsydneytdc

    @espiegel123 said:
    Can you try replacing the FAC Chorus clone instances with separate instances and see if the issue stops happening and let me know?

    My mistake for having a clone, I was building the vocal chain, should have been a new instance - not a clone.

    Have tried with making both instances unique and also removing the second instance (VOX channel), flicking through presets still results in the wet signal stopping.

  • sydneytdcsydneytdc

    Re Session configuration, I am running this at 96k, buffer 64 samples. (I was running AUM at the same settings for the tests)

  • sydneytdcsydneytdc

    Apologies for the slightly misleading behaviour report above, further testing shows that the behaviour is the same in my pedalboard session and a completely empty session with 1 input channel and 1 output buss.

    Instantiating 1 plugin results in the same buggy behaviour.

    1. FAC Chorus, flicking through presets still results in loosing the Wet. (note you have to move quickly)
    2. ClusterFlux: no wet signal at all.

    Session 96/24 64samples

  • espiegel123espiegel123

    @sydneytdc said:

    @espiegel123 said:
    Can you try replacing the FAC Chorus clone instances with separate instances and see if the issue stops happening and let me know?

    My mistake for having a clone, I was building the vocal chain, should have been a new instance - not a clone.

    Have tried with making both instances unique and also removing the second instance (VOX channel), flicking through presets still results in the wet signal stopping.

    I am not able to reproduce that. Can you create a new simple project with two new non-clone instances. If the problem happens, can you make a screen recording that demonstrates how to make the problem happen?

  • wimwim

    @sydneytdc said:

    @espiegel123 said:
    Can you try replacing the FAC Chorus clone instances with separate instances and see if the issue stops happening and let me know?

    My mistake for having a clone, I was building the vocal chain, should have been a new instance - not a clone.

    Have tried with making both instances unique and also removing the second instance (VOX channel), flicking through presets still results in the wet signal stopping.

    Have you saved and re-opened the session, preferably after exiting and re-entering Loopy Pro?
    I think I have run into at least one (non-reproducable) situation where removing clone instances didn't completely clear them out. Saving and force-quitting Loopy fixed the issue when re-entering.

Sign In or Register to comment.