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.

OneShot - random corrupt slots with user defined presets

Has anyone else had problems creating your own kits (presets) in OneShot? I've put together a couple of them now, saved all slots, then saved the preset. It will work for a few openings and closings of OneShot, but every now and then, I'll open the preset and see the message:

Warning - The current plugin state contains corrupt slot(s).

Looking through will show 4-5 slots with a yellow warning on them. Since I've saved every slot, I can simply reload them and everything is fine, though I'll have to save the preset, as it always comes up after that. Since the saved slots load, it seems to have something to do with the preset file.

I have a message stream going with Klevgrand, though it's usually 2-3 days between responses. So far, they aren't sure what the issue is.

Anyone else have this problem and solve it?

Comments

  • @rad3d said:
    Has anyone else had problems creating your own kits (presets) in OneShot? I've put together a couple of them now, saved all slots, then saved the preset. It will work for a few openings and closings of OneShot, but every now and then, I'll open the preset and see the message:

    Warning - The current plugin state contains corrupt slot(s).

    Looking through will show 4-5 slots with a yellow warning on them. Since I've saved every slot, I can simply reload them and everything is fine, though I'll have to save the preset, as it always comes up after that. Since the saved slots load, it seems to have something to do with the preset file.

    I have a message stream going with Klevgrand, though it's usually 2-3 days between responses. So far, they aren't sure what the issue is.

    Anyone else have this problem and solve it?

    Does this issue happen in the stand-alone mode or in an AUV3 instance of the app?
    If you haven't tried it already, see if the error persists if you switch modes.

  • @GrnEgz_N_Hm said:

    Does this issue happen in the stand-alone mode or in an AUV3 instance of the app?
    If you haven't tried it already, see if the error persists if you switch modes.

    Thx for the response.

    Both standalone and AU. I always build the kits in standalone mode, but I've then had the kit work in both standalone and AU mode, and then eventually show the corrupt slot issue initially in either standalone or AU mode.

    For some reason, the 7th version of one of the kits is holding over about 4 days of use (using the exact same method of building the kit as I did before), but the other one is still intermittent.

    All samples are 44.1k stereo WAV files located on my iPad (not iCloud). I've used them many times in the past with other samplers.

    I've also now removed and reinstalled OneShot and loaded all back in. No different.
    Is no else seeing this issue?

  • edited November 2024

    @rad3d said:

    @GrnEgz_N_Hm said:

    Does this issue happen in the stand-alone mode or in an AUV3 instance of the app?
    If you haven't tried it already, see if the error persists if you switch modes.

    Thx for the response.

    Both standalone and AU. I always build the kits in standalone mode, but I've then had the kit work in both standalone and AU mode, and then eventually show the corrupt slot issue initially in either standalone or AU mode.

    For some reason, the 7th version of one of the kits is holding over about 4 days of use (using the exact same method of building the kit as I did before), but the other one is still intermittent.

    All samples are 44.1k stereo WAV files located on my iPad (not iCloud). I've used them many times in the past with other samplers.

    I've also now removed and reinstalled OneShot and loaded all back in. No different.
    Is no else seeing this issue?

    I have this issue sometimes with factory presets even, you're not alone.

    Unfortunately, I've simply ignored those triggers.

  • @Goldiblockz said:

    @rad3d said:

    @GrnEgz_N_Hm said:

    Does this issue happen in the stand-alone mode or in an AUV3 instance of the app?
    If you haven't tried it already, see if the error persists if you switch modes.

    Thx for the response.

    Both standalone and AU. I always build the kits in standalone mode, but I've then had the kit work in both standalone and AU mode, and then eventually show the corrupt slot issue initially in either standalone or AU mode.

    For some reason, the 7th version of one of the kits is holding over about 4 days of use (using the exact same method of building the kit as I did before), but the other one is still intermittent.

    All samples are 44.1k stereo WAV files located on my iPad (not iCloud). I've used them many times in the past with other samplers.

    I've also now removed and reinstalled OneShot and loaded all back in. No different.
    Is no else seeing this issue?

    I have this issue sometimes with factory presets even, you're not alone.

    Unfortunately, I've simply ignored those triggers.

    Make sure to let klevgrand now if you haven’t already.

Sign In or Register to comment.