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
Xequence AU Pads seems like it would perfect for this. Flexible layout options, all keys on a single page, and no scripting needed to change notes assigned to pads.
Unfortunately it has a maximum of 8 pads per row, or you could easily make a qwerty layout.
@Stochastically As wim mentioned Xequence Pads can be setup to 8x8 pads. There is also Tonality’s Chord Pad plugin that can be setup to 12x12. Tonaility is currently 3$ (4$ off) and for your purpose you need to setup custom pads with single notes
In both AUv3 you can set pad labels and colors and have ‚empty‘ pads between the active ones.
Tonality Chard Pads. Good find! 👍
Another option might be running two instances of Mozaic, which would give you 32 pads. Not sure, but I imagine with careful use of global variables you could run pretty much the same script in both, at least identical or nearly identical in form. You could place them side by side or one above the other on screen. I'm not sure whether this would be simpler or more complex than trying to manage two banks of 16 pads in single instance of Mozaic where you can have only 16 at a time. The two-instance solution would have the advantage of giving you all 26 pads on screen at the same time.
After some thinking, i came to the conclusion that the main problem with the idea ‚text to music‘ isn’t the word input but the note mapping of chars to notes.
If you are going the type ‚pads to notes‘ way, i would recommend to do an intermediate step. Use simple assignment like A=0 (or even better the ASCII value which fits very well into 127 possible notes) and then record your words / texts into a Piano roll like Helium or Atom. So you only have to record your text once.
In a next step, use mfxConvert to assign new notes to the existing, recorded sequence. You probabbly need to change and update the note to note conversion quite often to get something musical.
.
Another hinderance is that the ABC consists of at least 26 letters, and if you are using a regular scale with up to 8 notes per octave as output, this will cover over 3 octaves - but ‚normal’ melodies span about a single octave (don‘t know the statistics, just my guts).
Maybe also map punctuation and spaces to ‚pauses‘.
.
I can also ithink about a different approach: Use Pythonista to read any selected text from the IOS clipboard and generate a midi file from the current text. Using Clipboard and midiutil_1_2_1 packages. Pythonista integrates into the ‚Share extension’ so this solution is available everywhere in IOS.
The conversion from ASCII to notes would be done in the python script by changing the contents of a simple output array. You wouldn‘t need to type any of the input texts and modifying the conversion is easy
I guess the python script is very short, the actual working code just loops over the chars of the clipboard text and outputs a note-on/-off/pause depending on the value set in the conversion array and updates the timebase.
Before the loop open clipboard and create the midifile and after the loop close the midi file. Done.
For easier editing of the conversion, spread the assignment over maybe 40 lines so that each char get an own line, in the comment of that line you could write the letter and also the letter frequency.
Maybe you even can come up with an even more mathematical approach and use the letter frequency as base (not the letters) and that assign offsets to the root to various characters. Ie more frequent letters get more harmonic offsets and the less common ones get odd offsets. I still would use punctuations and spaces as pauses. Notelength could also be assigned depending on the letter frequency - as mentioned above, due to the range it will be necessary to map several letters to the same note - so they could use different length.
Thanks to all for your thoughtful considerations. Tonality Chord Pads look, from your layout, to be exactly right. I did not know that type of custom layout could be done. This way I can at least try things out and see if it's worth pursuing.
Does a Patch for Mozaic like this exist? Allow me to explain in programmes likes Ableton Live you are able to force a midi file/pharse into a predesigned groove which effectvely forces/nudges the notes into a template/style say Rock Ska or something of that nature. Does such a patch exists? Or if not are there any Wizards out there that could design one? I would love to understand the mechanics of Mozaic but my deslexic head prevents me fro doing so. If no patch or wizards does anyone know of an existing app that could help? Cheers guys
@Toastedghost Have a look at the BeatGroove script which allows to setup a groove offset for each 1/16 of a bar and Joc Lady Delay script which steps through a list of 1-8 offsets with each note-on.
Ah thanks! I did manage to solve my problem by sending cc from helium. But I’m being pulled in the direction of mozaic as it does look very useful
Many thanks. They both work but in a fashion. I know I can use a groove template in Photon, but it is very intuative and a little long winded. I have vision for scripts, can even see their final outcomes just wish I could program that way others could see my vision. Cheers
@Toastedghost I only worked with groove templates in Reason 5 many, many years ago. There one could analyse an input midi file and ‚imprint‘ the groove of that file to the notes in the pianoroll.
There was a big list available grooves, but most of them were just variants of different swing settings. When analysing own midi files, the files needed to have notes with offsets in the different timing positions of a bar - otherwise nothing funky happened.
In Ableton you probabably also have a big list of available grooves that can be applied. Maybe there are even external midi file libraries with grooves available. But in Mozaic you can‘t read external files - only midi input or use manual input (like in the BeatGroove script) to specify the offsets.
Another thing that only works in piano-rolls is negative offsets, as with scripting one can only delay notes and not play them before they are issued.
.
I just had a look at the Ableton 10 manual. It uses AGR files for grooves, but i couldn’t find an open specification for the format. Samples from Mars offers a free ‚Grooves from Mars‘ library with classic drum maschine grooves in AGR and midi format. But i didn‘t find stuff like ‚SKA or Rock grooves‘, only different styles of commercial midi drum loops from GrooveMonkey.
.
With the given limitiations, i don‘t think its possible to do somethink like Abletons groove imprinting with Moazic.
If that is the case it is a shame because I think it could lead to numerous creative possibilities.
It would be great if Paul could incorparate this into Helium
Besides the AUv3 piano rolls Helium and Atom, groove imprinting could also be added to the piano rolls of DAWs like Cubasis, Auria Pro or BeatMaker 3.
As mentioned, a script can‘t pre-empt notes that aren‘t yet issued, only delay notes. Piano-roll based apps know all timings of their notes, so they can move them arround freely forwards and backwards in time.
I also suspect that several of the common grooves use negative time offsets to energize the beat.
What's the best script to use to do something like this: Send Mozaic eight notes to reflect which "scene" I'm currently on in a song by activating a button. Extra points if I can input some text into the UI for each button that gives a description that makes it easier to discern which part of the song I'm in. I don't believe I've seen anything like this on Patchstorage but perhaps I haven't found the right search string.
Let me see if I understand. Do you mean:
"Some sequencer or controller would send one of eight notes to Mozaic for when your song starts playing a scene. Upon receiving that note. Upon receiving this note, Mozaic will light up a corresponding pad and darken the rest to indicate the scene that is playing. Would like to be able to input some text on each pad to name the scenes."
If so, I don't know of any existing scripts that are a good fit offhand. But such a script would be trivial to make, except for the part about inputting text to name the pads. That would need to be done by editing the script each time1. The script would be much simpler if using pre-defined notes per pad than if you need to be able to change the notes used.
With a large amount of additional code, predefined names could be selected for each pad, I suppose, but it would be clunky. ↩︎
Is there a way to make the midi cc-randomizer script, basically exactly the same but with like 5 pages, or more. This way I can fit all of a synths parameters into one instance of Mozaic. I’ve set up a couple patch randomizer scripts for a specific synth and saved a template in AUM. However most synths take at least 2/3/4 instances of Mozaic to randomize all the parameters. It be so much easier if I could map a synth to one instance of Mozaic and cover all parameters. I know there are GUI limitations but is it possible to set up a midi cc randomizer script with 5 pages, map all pages to the parameters of one synth, on 1 channel, hit the randomize button and it randomizes all 5 Mozaic pages, thus randomizing the synth? If not, even 1 random button per page, quickly flip through, hit the button on each page and have a fully randomized synth patch would be great. If it is possible, Having all those Randomized CC knobs in one instance of Mozaic would be super helpful and make this task a lot easier. Thanks.
Just a suggestion but Maybe any talk of money for the exchange of services should be done via DM. And be a proper offer.
Yup tonality might be helpful.
@lukesleepwalker - if my understanding of your question is correct, then the script below is a basic implementation.
Are you referring to the MIDI Randomizer and Scenes v2.01 script?
I have the name listed as midi cc randomizer, not sure if I got it from the wiki or patchstorage or this forum.
Hold up that’s the wrong one. Lol. My bad 1 minute.
I had the name correct but image was an older version of the script. Here is version 2.01
OK, that one I wrote.
I'll think about it. I'm not a huge fan of the idea, but it wouldn't be too hard to do. Compensation isn't something I'd accept if I do decide to do it. ✌🏼
If anyone else feels like forking it to do this, knock yourself out!
Whoa, oops, I just realized when you hit shift you get a pad bank with ability to store presets… Missed that. I guess this can be used to save a bunch of presets, that way one instance can cover all the possible synth parameters, correct?
I don't think so. I think the preset only stores the value, not the CC number if I remember correctly. Adding the ability to store the preset number might be a way to go though.
@Poppadocrock - Why not simply midi learn the same note or cc to the knob 0 parameter of as many instances as you need? That seems like a more reasonable and scalable approach to me.
Ok didn’t know that about the presets, thanks.
Yea I made one for Mononoke, and I added the correct cc values inside the Mozaic script, and uploaded it, but I needed to use 2 instances of Mozaic to cover all the possible parameters. A lot of synths have even more things to be mapped then Mononoke, so I was hoping for a way to be able to map every synth parameter to one Mozaic, hit 1 button, and everything is randomized.
You can do that? Good idea. But I’m a little Confused.… are you saying still use multiple instances of Mozaic, with the midi cc randomizer loaded up, midi learn the first knob of each to the same note or cc value, so all 3 randomize at the same time? I’ll still need multiple instances but one note or cc will randomize all 3, Correct? That will definitely help.
You don’t have to do the script, I was just throwing it out there. Actually since this is something I would do in a separate AUM template, not in the middle of a session, I’m not as concerned about cpu usage. I was just hoping to have an all in one solution to basically create random patches on any app. Midi learn or map every possible parameter a synth has and create a random patch, with the press of one button. I know a lot have that feature but some don’t. OBXD, Tal, etc… if you do no rush, thanks for the help.
It’s a hardware controller so same eight notes every time. I also don’t mind editing the script.
Edit: saw your second post; will give it a try. Thanks for getting it rolling!
@lukesleepwalker Not sure if this will help https://patchstorage.com/scene-master/
You can send CH16 notes 0-15 to trigger the visible pads on the screen. So in scenes mode you would send Ch16 Notes 0-7 to change scene.
It also sends a cc message 109-116 on scene change so if you turn off quantization then you can use it to switch patterns in Drambo or the like.