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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Mozaic - any way to save things?
I suspect this may be an AUv3 thing, but I can't see any way to manually save and restore things from within a Mozaic script ('serialisation', in the jargon). I get that variables are saved with the state, but the problem is they are wiped out if you reload the script. This means any trivial tweak to the script loses everything.
Is there any way around this?
Comments
No, all your variables can be saved inside the saved state. Check the manual for a complete explanation
There’s no saving to file.
So is this an AUv3 limitation? That there's just no way it could be implemented?
When you change the script and recompile, the data layout might change. Saving a preset or snapshot saves the entire current state of the module, effectively as a binary image. So it would be difficult or impossible to merge saved "data" values with an updated "script". It's not just an AUv3 limitation.
I don't know what you mean by 'module' but I get the gist if state saving is BLOB-based. Never mind, Bram has confirmed this is a hit you have to take while developing a script.