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.

Cubasis/Addictive Pro state saving bug - Can anyone verify?

So I’m on an iPad Pro (4th gen) on 16.7. I ran into an issue in Cubasis where i had 3 different tracks of Addictive Pro setup in a session and upon reopening lost my patches. Even trying to load the patches that were saved within Addictive Pro while using it in standalone won’t load properly in the session.

I can probably resurrect it by starting a new session and loading the presets I have created again but just wondering if anyone has experienced this?

Comments

  • i going to check later

  • I just tried with three tracks of Addictive Pro and loaded different factory patches to each. All came back as I left them after closing Cubasis. I then made some changes, but didn't save the patch. Again, everything came back just as I left it, including the changes.

    However, then I saved the patch with a different name. When I came back to Cubasis, the patch name was the original I loaded, but all the actual changes were there. I then loaded the saved/renamed patch then closed and reopened Cubasis. Again, the patch was loaded as I left it, but the name was from the original factory patch that I had loaded.

    So: It looks to me like the actual patch is being loaded properly but the name isn't being reported to Cubasis in the way it expects. Not the first time I've seen that happen for an app in a host. It's confusing for naming, but the sound should be the same according to my tests.

    Side note: if you find and load the patch from Cubasis' patch browser rather than Addictive Pro's internal patch browser, the name seems to stick.

Sign In or Register to comment.