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.

iSEM AUv3 issue?

SpookyZooSpookyZoo
in General App Discussion

Hi Guys,

I’m finding that multiple instances of ISEM are not retaining their individual patches in AUM.

Say I have 4 iSEMS in separate AUM lanes each with a different patch and then save that project to file.

When I reload that file, ALL 4 iSEM instances have the same patch, the last one assigned.

If I do the above with something like Zeeon, they retain their individual patches.

Has anybody else had this? Found a workaround? Had feedback on the issue from the Dev?

Cheers.

Comments

  • AndyPlanktonAndyPlankton

    @SpookyZoo said:
    Hi Guys,

    I’m finding that multiple instances of ISEM are not retaining their individual patches in AUM.

    Say I have 4 iSEMS in separate AUM lanes each with a different patch and then save that project to file.

    When I reload that file, ALL 4 iSEM instances have the same patch, the last one assigned.

    If I do the above with something like Zeeon, they retain their individual patches.

    Has anybody else had this? Found a workaround? Had feedback on the issue from the Dev?

    Cheers.

    Is it definitely the same patch in each instance ? Just asking because there was an issue with AUv3's where they would load the saved state, but the name would be the same on each, either a default name or last one used or something like that.
    This sounds similar.

  • SpookyZooSpookyZoo

    @AndyPlankton said:

    @SpookyZoo said:
    Hi Guys,

    I’m finding that multiple instances of ISEM are not retaining their individual patches in AUM.

    Say I have 4 iSEMS in separate AUM lanes each with a different patch and then save that project to file.

    When I reload that file, ALL 4 iSEM instances have the same patch, the last one assigned.

    If I do the above with something like Zeeon, they retain their individual patches.

    Has anybody else had this? Found a workaround? Had feedback on the issue from the Dev?

    Cheers.

    Is it definitely the same patch in each instance ? Just asking because there was an issue with AUv3's where they would load the saved state, but the name would be the same on each, either a default name or last one used or something like that.
    This sounds similar.

    Interesting...

    I’ll double check with drastically different sounding patches and report back.

    Cheers

  • SpookyZooSpookyZoo

    @AndyPlankton said:

    Is it definitely the same patch in each instance ? Just asking because there was an issue with AUv3's where they would load the saved state, but the name would be the same on each, either a default name or last one used or something like that.
    This sounds similar.

    Yep! You’re right. Sounds remain individual but all instances show the same patch name.

    Is this an old bug?

    Only workaround I can think of is to name my AUM channels the name of the patch for clarity’s sake. :)

  • AndyPlanktonAndyPlankton

    @SpookyZoo said:

    @AndyPlankton said:

    Is it definitely the same patch in each instance ? Just asking because there was an issue with AUv3's where they would load the saved state, but the name would be the same on each, either a default name or last one used or something like that.
    This sounds similar.

    Yep! You’re right. Sounds remain individual but all instances show the same patch name.

    Is this an old bug?

    Only workaround I can think of is to name my AUM channels the name of the patch for clarity’s sake. :)

    It's been around for a while, I think it affects lots of AU, well it did anyway, perhaps iSem is one that hasn't been updated to sort it out.
    Yeah, naming the AUM channel would help, it would also mean that if you do start swapping patches, you know which one you started on so can get back to it, you'll just have to remember to rename them when you permanently swap patches.

  • j_liljedahlj_liljedahl

    This is a known bug in iSEM.

  • SpookyZooSpookyZoo

    @j_liljedahl said:
    This is a known bug in iSEM.

    Thanks for confirmation Jonatan.

  • kinkujinkinkujin

    ugh...everytime I see a post about iSem I'm ashamed I haven't bought it yet. HA!

Sign In or Register to comment.

© Vanilla Keystone Theme 2025