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.
Comments
I think it’s amazing.
If a big part of your music is repeating patterns (in terms of the same notes or similar notes repeating) but the actual patch sound morphing and shifting in interesting ways - then this script is invaluable.
It really brings synths to life being able to shift slowly (or rhythmically) between numerous parameters in a really controlled way... with just one finger.
Heh. I’ll have to try it some day. 😂😂
Alchemy for everything!
Exactly!
Have found a bug I think.
Just so far have tried morphing between pad 1 and pad 2.
The problem is something to do with the first and last cc knobs. Changing the last (19th) knob on pad2 has the effect of also changing and saving the first knob on pad 1 to the same value. And I believe changing the first knob on pad 1 and resaving changes the last knob on pad 2 to the same value.
Anyway there’s something odd going on between knob 1 and knob 19!
Thanks, I’ll check it out.
Here’s something that might be useful. It’s an ADSR for midi cc values. Set the time for each stage and the level for the attack and sustain. Then send any midi note. Cc values will be sent following the ADSR curve. You can also set it to scale the envelope velocity based on the velocity of the triggering note. This can be used to trigger volume swells and ducking, to augment synth’s with limited envelopes, etc.
This is a simplified version of another project that will allow a bank of up to 128 multi-stage envelopes, to come at some point.
MIDI ADSR: https://patchstorage.com/midi-adsr/
MIDI ADSR
Send ADSR controlled MIDI CC values via notes.
Set the time for the attack, decay, sustain, and release stages of the envelope. Set the level for the attack and sustain stages. Then send any note to the plugin. CC values will be output following the envelope's shape.
If the note is held down, the envelope will stay in the sustain stage until it is released. Retriggering a note before the end of the envelope will interrupt the envelope and restart from the beginning.
You can also enable velocity sensitivity, which scales the envelope according to the velocity of the note received.
@wim Great stuff you been pushing out. Been using the Cordulator today into Pure Synth fab stuff. Getting stuck notes now and again Hower. Do you plan on taking this script any further refining etc it is my number one script on Mozaic using it daily.
Yeh, fixing that one up is next on the list. The last Mozaic update added some super-handy features to make that job far easier than it was going to be.
Great will look out for the update thanks again for this great script.
OK, I think that one should be fixed with version 1.2, along with morph not working from the X and Y knobs. Please let me know if not!
Thanks will check.
It was definitely the last knob of pad 1 conflicting with the first knob of pad 2!
But I’ll check out v1.2 later.
Mmmm. Doesn’t appear to have fixed it.
But then again I can’t see a way to confirm I’ve correctly loaded and am I’m running v1.2 rather than the old version. Is there a version number in the code somewhere?
It should say v1.2 right next to the app name in the description that comes up when you load it.
One thing I noticed, even when you Load a new app in Mozaic, sometimes you have to Upload the code using the upload button before it actually takes. I don’t remember that happening before, so maybe it’s a newly introduced bug.
I'll see if I can reproduce this somehow
Me too. It’s happened twice, but don’t remember what led to it.
Have got the latest version now thanks. In the end I worked out that I had to delete the old version from ‘user presets’ and then install the new version. Overwriting didn’t seem to work.
Seems to be fixed now I think. I did get some weirdness (pads sounding different when I returned back to them after assigning new pads) but I can’t replicate. Certainly the first 10 knobs seem to be A-ok across pads. Will let you know if I find any other issues or anything specific.
It’s great fun anyway. And 19 knobs is most certainly enough! In fact for most Gadget synths it seems like about 10 or so parameters is optimum for morphing without it becoming too crazy.
I'm not sure if this is a Mozaic bug or a script bug... but I was playing with the latest Minimalism Wizard script last night. It seems like the midi channels are off by one. Meaning, if I have channel 1 selected for output, it's actually going to channel 2 instead. I tried with various channel selections to confirm. I believe that's @rrc2soft script but I'm not certain.
I made the script so that if you haven’t moved a knob yet, no cc value is sent on the XY changes. So, if you only use 10 of the cc’s only those will be morphed or sent. But once you move a knob it is fully involved.
That's my fault - a script bug
. Will upload a fix soon.
Making progress I think, but it’s a tough challenge and I’m still at least a few days out from having an update ready. I think I’ve figured out how to avoid stuck notes in normal operation, but still need to build in a safe way to handle parameter changes while notes are playing. Changing the scale, or midi channels, etc. while notes are playing could still throw it off. I have some ideas though.
Updated the infinity sequencer last night. https://patchstorage.com/infinity/. Added pad labels and a few little features.
Loving the update, but I seem to have unstable MIDI timing now. Notes sometimes group together instead of playing out at a fixed rate.
I haven't investigated yet if the old version of my script suffers from this, so I'm not sure if it's something I broke or the Mozaic update.. but I didn't change the core metronome/sequencer code so I suspect the issue might be with the Mozaic update.
Ah.. MIDI output timing didn't change in the update, so I'd be surprised if the update broke that particular aspect of your script. I did make the Metronome timing more stable at high resolutions, so if your script made assumptions about a degree of sloppiness in the Metronome @ PPQN > 150 then that could be a cause of different behavior.
PPQN never gets set higher than 8.
OK I have a tiny script that reproduces the issue. It might still be my fault, I think the issue occurs when you play the same MIDI note repeatedly (like in a sequence), and are enqueuing delayed MIDI note offs to be later than the subsequent MIDI note ON for the same note.
At 120 BPM if you play this script and press play on the host, eventually the notes will play unevenly like a chord instead of just a steady 1/16th pulse.
@brambos Any chance for a UI that:
a) has 22 sliders (instead of knobs)
b) can "draw" over the sliders to set their values instead of setting one-by-one
This would be incredibly useful for drawing out pseudo-waveforms; in a performance context; etc.! Thanks!
Trove of script, app etc ideas here: https://docs.google.com/document/d/e/2PACX-1vRngItA2PEDOI3yKraeBt_kh1DLwNDeAvOL2SslmXdDBdZupjcizvszVlGvaXJcgvWMpQh4NF_boY15/pub
Issue confirmed, thanks for this helpful script. I think I have it fixed. Will test some more tomorrow and I'll issue a priority fix.
Beautiful, thank you!
Ah. T> @wim said:
Ah. Thanks. That would explain what I was getting then.
(I was pretty happy with pad 1 with just a few knob changes. Moved to set up pad 2 which required changes to additional knobs. Then used the X-Y pad to return to pad 1 and it didn’t sound the same as when I’d left it. Presumably because when I set pad 1 it only registered a couple of ccs or certainly not everything I was hearing.)
Anyway, now I know I’ll just make sure to tweak all the knobs I’m likely to use.
It sounds like I confused you. No, this wouldn’t have anything to do with what you may have seen. All I was saying is you don’t need to be concerned about knobs you haven’t touched yet sending cc’s. You should not need to concern yourself with touching knobs until you need them.
If you see the oddness you mentioned again, please let me know if you can reproduce it, since that would be a bug.