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.

Agonizer not saving preset ?

onerezonerez
in General App Discussion

Hey all…. Still around. Lurking. So can anyone confirm this? I never really played with Agonizer but I buy everything and yesterday came across this:

IPad Pro M1. IOS 16.1 — this happens in AUM or Cubasis, any preset that I load it will not save the name of it upon reopening. It appears to be the same settings and sound correct but not the name. I found this out as I was trying to recreate an AUM jam in Cubasis and then looked at preset and it always goes back to the “int”.

Cheers
Charlie

Comments

  • SamuSamu

    This is most likely because the 'Preset Name' is not an actual AUParameter and when hosts create a 'snapshot' for later recall they most often only store the actual AUParameters...

  • bygjohnbygjohn

    Hmm. Not entirely sure I’ve understood what you’re doing, but FWIW I’ve just tried creating a new preset using Agonizer in AUM, and it saved the name OK. I checked reloading the AUv3 and it was still there with the correct name. This is on an iPad 6 with 15.7.1, so I’m wondering if this is an iOS 16 issue?

  • SamuSamu

    @bygjohn said:
    Hmm. Not entirely sure I’ve understood what you’re doing, but FWIW I’ve just tried creating a new preset using Agonizer in AUM, and it saved the name OK. I checked reloading the AUv3 and it was still there with the correct name. This is on an iPad 6 with 15.7.1, so I’m wondering if this is an iOS 16 issue?

    Did you save the preset as 'AUM Preset' or using the Agonizers built-in preset-saving function?

  • bygjohnbygjohn

    @Samu said:

    @bygjohn said:
    Hmm. Not entirely sure I’ve understood what you’re doing, but FWIW I’ve just tried creating a new preset using Agonizer in AUM, and it saved the name OK. I checked reloading the AUv3 and it was still there with the correct name. This is on an iPad 6 with 15.7.1, so I’m wondering if this is an iOS 16 issue?

    Did you save the preset as 'AUM Preset' or using the Agonizers built-in preset-saving function?

    Using Agonizer’s built-in function. Maybe that’s the difference.

  • bygjohnbygjohn

    @bygjohn said:

    @Samu said:

    @bygjohn said:
    Hmm. Not entirely sure I’ve understood what you’re doing, but FWIW I’ve just tried creating a new preset using Agonizer in AUM, and it saved the name OK. I checked reloading the AUv3 and it was still there with the correct name. This is on an iPad 6 with 15.7.1, so I’m wondering if this is an iOS 16 issue?

    Did you save the preset as 'AUM Preset' or using the Agonizers built-in preset-saving function?

    Using Agonizer’s built-in function. Maybe that’s the difference.

    Oh, and I’ve just realised your response must have come it while I was typing mine!

  • onerezonerez

    @Samu try any DAW and the internal built in function does not work for me. I can load up a preset and then close out the project and even though the preset sound is correct it shows the INT patch.

  • SamuSamu

    @onerez said:
    @Samu try any DAW and the internal built in function does not work for me. I can load up a preset and then close out the project and even though the preset sound is correct it shows the INT patch.

    Then I'd suggest getting in touch with the developer so they can sort it out.
    I no longer have it installed for various reasons...

  • bygjohnbygjohn

    @Samu said:
    This is most likely because the 'Preset Name' is not an actual AUParameter and when hosts create a 'snapshot' for later recall they most often only store the actual AUParameters...

    ☝️This.

    I just tried loading a preset into an AUM project, saving the AUM project and then reloading it. This is exactly the behaviour. Sound is correct, but name is INIT. This happens with a lot of AUs.

    AUM has a notes function where you could note down the presets used, maybe Cubasis does, too - I don’t have it. A workaround, but useful for remembering what you used later on.

  • uncledaveuncledave

    @bygjohn said:

    @Samu said:
    This is most likely because the 'Preset Name' is not an actual AUParameter and when hosts create a 'snapshot' for later recall they most often only store the actual AUParameters...

    ☝️This.

    I just tried loading a preset into an AUM project, saving the AUM project and then reloading it. This is exactly the behaviour. Sound is correct, but name is INIT. This happens with a lot of AUs.

    AUM has a notes function where you could note down the presets used, maybe Cubasis does, too - I don’t have it. A workaround, but useful for remembering what you used later on.

    The logic for this behavior is as follows: yes, you loaded the preset, sometime before saving the session state. But nothing keeps track of any changes to the app since loading the preset. So it would not be correct for the app to indicate that you are still using the preset, unless the app also recorded a "modified" flag.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025