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.
How To Remove Old Presets? [and - how to copy Mozaic scripts to PatchStorage)
Hi,
I’ve carefully crafted a mighty-fine grade AAA Mozaic script to generate a string pad, based on a single MIDI note.
In the process, I’ve created some old versions which I’ve saved as presets. I’m not really certain how to get rid of these presets.
I save all the presets in AUM rather than the ‘app’ or ‘plugin’ themselves, because there’s always some error that the App or Plugin doesn’t support it. I’m on iOS 14.x
SooOOOooO yeah…. how do get rid of these old presets or version in AUM?
Thanks
Oh yeah…… is there a video on how to upload a Mozaic script to Patchstorage? Can I simply copy the code and save it as text?

Comments
Swipe left on the preset name to expose the delete button.
After you've saved a script, use the button just to the right of the save button to export it. That'll prompt you for what to do with the file. Save it somewhere in the files app. Then when you're on patchstorage.com you can browse to that file to upload it. You don't want to post just the text of the script as people will need to jump through too many hoops to get the file into Mozaic.
Also, a really good practice is to always save and export clean projects. Mozaic saves all knob tweaks, variable values, etc. with the patch. Generally you want people to start with the raw, unmodified settings. So, 1) Use the Mozaic Upload button to get the initial state, then 2) immediately save the script, and then 3) export - all before making any changes or using the script for anything.
Oh, and another thing. It's always good to save the version number in the file, but not to use the version number in the name of the patch on patch storage. The URL gets taken from the name you give the app. You don't want the URL to change. But you also don't want to upload changed versions of the app using the same file name. Even though you have the opportunity to list the version of in a field on the form, this has nothing to do with the name of the file. So it's important that any new versions you upload have unique names.
It's a good idea to make it apparent in the UI somewhere what version someone has loaded as well.
And its also recommended to set the label above the knobs so that it‘s no longer the generic ‚knobs‘ but instead the name (plus version id) of the script.
Also to set the icon name so that it can be distinguised from other Moziaic scripts in the same session.
Both can be done in the OnLoad section
Perhaps add a description section, which will be shown on the first load of that script (and also when switching or using to Layout 4)
If you only need upto 4 knobs, its recommended to use Layout 4 which will show the description in addtion to 4 knobs and their knob main label - so users always can lookup the documentation.
Sometimes I wish there was another way to identify. Like being able to change the GUI color (and have the plugin icon mirror that color)
My eyesight is greeting pretty crappy to read that text
Same. But better having a shortname than using 5 instanzes of ‚MOZ’ in a session, where one has to remember the row/column position to find the correct one and if they all use standard layout with labeling, one would be lost completly
If the short names differ in lengths its easier to distinguish the various instances of Mozaic. The visual difference is why i sometimes used dots, dashes, stars etc in the shortname, ie
B.H.CorIO-ARPorT*C*B.It’s also possible to use color emoticons in the shortname, but since these internally count as several chars (unicode, up to 4 bytes per char), you no longer have 6 letters for the name. In my opionion they also look too different from the black and white of all the other icon labels.
At the rate you write scripts, I can imaging it's pretty difficult for you, cause I imagine your sessions are like 2-3 instruments and 20 Mozaic plugins
OK folks….. I completed and uploaded my first Mozaic Script to Patchstorage. It’s Christmas, and I want to put a string pad Script in their stocking.