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
Hmm, i don‘t like the SHIFT pad plus knob operation for configuring a channel‘s setting - seems over complicated.
Maybe it‘s more convenient to distinguish between short tap and holding a pad. Short tap toggles the mute setting as before. Holding a pad will bring up the transpose and volume knob and an additional mute knob to manuall configure all tree settings - but it won‘t toggle the mute by itself.
One less button (SHIFT) to hold, maybe i also find something to get rid of the SHIFT for saving a config.
Hmm, there are two unused pads in the upper row. One could label the right one „Save config“. Tap that pad and the lower pad row changes color to indicate save mode. Then tap one of these 8 pads to store the config. Tapping any other pad in save mode (like the Save pad itself) would cancel the store operation.
Or use the same metholody as with the channel pads: One needs to hold the ‚Save‘ pad and press the destination config to interact ? Thats like the SHIFT pad idea, but with a named pad. Perhaps both interactions are possible (tap+tap or hold + tap) with the same code.
PS: First dev hour already spent by imagining what it‘s like to operate the script and what features may be usefull
@_ki I owe you that coffee/beer/ice cream many times over as I have enjoyed the fruits of your scripts more times than I can count. Related to your inquiries into @erol use case, I've been using your scripts with my own journey using an acoustic guitar and MIDI Guitar 2 in AUM. It brings me such joy to experiment with a beautiful acoustic instrument, MIDI scripts and interesting sounds. This past weekend I was using your Multi-Divisi script with very interesting results. I set the Wait and the Suppl as high as they could go to get the most out of arpeggiated guitar chords and it does produce interesting results. The per string suggestions that have recently been described are of interest to me because I can see some applications that sit somewhere between Multi-Divisi and MIDI filters/ranges. I doubt I would configure my set-up by string, though, because the ranges of notes that I want to clump usually span multiple strings. My dream is to be able to identify, for instance, specific notes--or ranges of notes--to send out as bass notes on Channel 1, a set of notes or range of notes to send out on Channel 2, etc--but also to randomize the notes that are generated in some cases. In other words, a Guitar Accompanist that is configurable using the Mozaic UI. But enough of that, you should name your preferred object of desire (coffee, beer, whisky, ice cream, comic books, etc) so that we can properly advance gestures of gratitude. @wim and @McD too!
Hey, @lukesleepwalker it sounds as though @erol is using a midi guitar that sends on different channels for each string.
I don't think Mozaic could help if the channel for each string isn't being sent. I guess you could, say, assume a string if you limited the number of semitones selected to five or something. For instance, assume E,F,F#,G,G# of the right octave were played on the low E string, A,A#,B,C,C# were on the A string, etc, But that wouldn't accurately reflect which string was being played unless the notes were only played from the lowest position on the fretboard.
Or, does MIDI Guitar do something like this already and allow you to split output by channel based on its guess at the string being played?
Beyond guitar specific use, a script that lets you play around with the channel used by range of notes sounds interesting. 👍🏼
@erol Got some more questions:
Should the mute happen immediately when pressing a channel pad (like in MF&T) or wouldn‘t it be better if one could sustain a note, press the mute without ending the note and the next note on that channel will be muted ? This would free the player of pressing the mute at the correct time or when no note is played. The transpose and volume change also act on the next played note and not modify the current note.
Just having written down the previous sentence i had a new idea - wouldn’t it be cool if configuring transpose would act immediately ? IE if one plays a sustained guitar chord and holds a channel pad, turning the transpose knob would end the active note of that channel and change to the new transpose setting. In that way, tuning in a different chord would be super easy. Way better than having to replay the chord for each knob turn to check if the correct offset is found. But i have to check if that behavior is possible or if to many notes are ended/started while turning the knob. Maybe a throttle needs to be implemented, update the transpose only 10 times a sec or so - done in a timer. But in fact it could sound weird, as the other notes of the chord are sustained, but the changed one re-starts with its attack/decay phase.
Hmm, could volume also be updated immediately ? I suspect that one would need to retrigger the whole chordset with all active notes to get an impression if the current volume balance between the strings fits.
Again regarding the number of available configs. Its easy to expand from 8 to 16 or 32 using a bank knob. But i have no clue how many different tunings/volume settings or mutes makes the most sense. If you only need two or four, having 32 is way too many.
No, MIDI guitar doesn't send out separate MIDI channels per string so you are correct that it would be weird for anyone who plays guitar normally (as you describe above). So, yeah, I think I'm interested in a script that lets you play around with the channel based on a range of notes.
What would be cool is that if there were options for various use cases that an "accompanist" might need. I'm just brainstorming a bit here but this is based on my recent experiments with live guitar and MIDI guitar accompaniments. For instance, for a certain range of "root notes" that start a bar I might want to hold the gate open for that note for the entire bar so that I could play an arp accompaniment (eg a simple bass motif via StepPolyArp or Riffer). One could also get a little percussion riff going using something similar. I can already achieve some cool evolving note clusters via something like Cality, but I suppose a sophisticated script could give you these options "all in one place" in Mozaic. In general, I don't think a guitarist would use more than about 3--maybe 4--different zones. I see the bass notes as one zone (channel 1), the mid-range where you often get the third or fourth note in an arpeggio, and the top strings where you ring out the later notes in an arpeggio. And finally, the fourth could be further up the neck for melodies/solos. Again, just kind spitballing here.
Granted, he uses a MIDI guitar with different channels for each string, but the Streambyter creator wrote posted a video somewhere of some really cool scripts that he wrote to change patches on his guitar effects in response to his playing. Even without being able to make use of the string (channel) info, there are some cool possibilities to cause your guitar's effects to auto-switch based on certain sequences of notes -- or using the lowest notes (or highest notes) as switches.
I'll have to go look for that. Thanks for the tip.
Just typical modular stuff, with clocks and apps running at different but related tempos.
Is there a reverse arpeggiator? I mean an app that collects the notes of an incoming arpeggio and sustains them as a chord until the end of a bar, or two bars, or however long you set the interval to be.
It’s called a sustain pedal...
Not sure when I wrote the message quoted above, but it must have been some time ago. It was incorrect.
Mozaic does handle midi clock messages. And there is a clock divider script of sorts. I wrote it. https://patchstorage.com/midi-clock-tool/
Good point. One could use the infinite setting on Eos reverb to accumulate the notes, sending it two consecutive gates every bar or two to reset.
Just to clarify though: This cannot work to divide clock for audio units within AUM. It can only work for external hardware and apps. There is absolutely no way to divide host clock internally other than if the host provides it.
Muchas gracias. I should probably stick to miRack for this kind of thing.
Atom and Atom 2 are also good for this, at least as far as sequencing goes. It's no good for other clock dividing needs such as tempo synced delays, etc.
Love and hate Drum computer. Mostly the remix slider.
Any chance it’s Mozaicable?
Doesn't have to be. It's exposed as an AU parameter so can be controlled by MIDI just like any other.
Interesting. I wouldn’t use DC as a sequencer.
My idea was to have a Mozaic script that does the same as Remix to an incoming midi.
Oh, I see. I guess that would be some kind of script that fires off a bunch of MIDI CC's with semi-random values, that you would then need to map to AU Parameters. MIDI CC Randomizer and Scenes could be used for this, but you'd have to do all the AU Parameter mapping first to make it work.
... hummmm
Or not. Sorry, spoke too soon. That would alter the whole settings permanently and wouldn't have any way of returning to the original values.
Have you tried throwing an external sequence at DC, then futzing with the remix slider? Does that do what you want? I don't recall if the remix thingy messes with just knob settings or if it does something to the DC sequencing itself. If it's only knob settings then my original idea of using the Remix AU parameter should work.
What I had in mind is more of an effect of juggling around midi notes.
“ Remix
The Remix Feature is a one touch fill maker. Activate the Remix control temporarily to mutate the current pattern. 16 remix figures are available: 1-8 creates small rolls over 2-3 drum sounds, each figure addressing another group of engines.
9-14 will assign existing patterns to different engines.
15&16 creates pure 16th rolls and fires these across the engines.
Additionally, random pitch bends, send fx- and filter sweeps will be generated.”
Ahh, so it's a combination of notes and midi CC's that it would have to send. The notes wouldn't be a problem, but it would come off the rails with the CC's. Without a bullet-proof way of knowing where any controls you affected were when you sent the fills, you'd have no way of getting back to where you were after the fill.
So midi notes would be enough for now.
But if I want the cc change I would use Drambo.
Any similar (and simpler) Mozaic script like Ki Mutator?
Hi,
Is it possible to create a script that will take a midi note and send out a cc with value. So
c3 —> cc10,1
C#3 —> cc10,2
Etc
Req: Beatstep Pro Drum Sound Selector Script
Hi.
I wondered if someone was able to write a script that would allow me to audition and change drum sounds on the fly, directly on the beatstep pro. The script would map each drum sequencer note to its own midi channel, and an encoder would be used to transpose the note. Each pad would be mapped to its own instance of audiolayer with its own bank of samples.
The beatstep pro would be configured so that the pad mapping in control mode is the same as drum mode, this way the sounds could be auditioned by playing the respective pad, or changed/auditioned by turning the encoder when switched to control mode.
Beatstep setup
Drum mode:
Chromatic drum map ( notes #36-#51)
Midi Channel 10
Control mode:
Encoders 1-16 set to cc# 11-26 midi channels 1-16
Pads 1-16 mapped chromatically notes #36-#51 channel 10
Desired operation
Drum mode:
Pad 1 triggers note #36
Pad 2 triggers note #37
Control mode:
Pad 1 triggers note #36
Pad 2 triggers note #37
Encoder 1 transposes note #36 between note #0-#127 output on midi channel 1
Encoder 1 plays note message as new value is selected
Encoder 2 transposes note #37 between note #0-#127 output on midi channel 2
Encoder 2 plays note message as new value is selected
Etc.
I hope this make sense, please don’t hesitate to ask if you need anymore info. If anyone is able to do this or propose another method that would be great. Thanks in advance for any help.
Cheers
Yes that's easy to do. There are different ways to do it, depending on whether you want the midi notes to play or not,
and other things. Try something like this to intercept midi notes 60 and 61 and send cc's instead:
You don't need to resort to scripting for this. mfxConvert is an easy to use utility that can do this and more without scripting.
If you do want to go with Mozaic, here's a ready made script with GUI controls so you don't have to do any programming. https://patchstorage.com/key-to-cc/
I’m thinking of a kind of musical game based on the alphabet. So I’d like to have 26 pads that each send a certain midi note. I’ve been trying to set this up with KB-1 by using a drum pad layout but that seems to have a 16 pad, two octave limit. Mosaic would be better anyway because it would be easier to share.
I’ve been researching ideas for musical alphabets and my first thought was to make C = C, A = A, etc. but after some thought I have a map in mind that’s based on statistical letter usage. For example the most frequently used letter is E.
For those with the know-how this must be an easy script. I looked briefly at mosaic code and like any sort of coding it gives me an immediate headache.
Any help would be much appreciated.
There are only 16 pads in Mozaic. So you'd have to have some way of switching between "banks" of pads. Have you considered that in your conceptualization? Maybe two sets of 13 pads with one pad for switching between banks? Or, 13 pads that alternate values based on whether SHIFT is pressed?
Aside from the interface, is there a lot of game logic that would need to be scripted into this thing? If not and it's only important to map pads to notes, Xequence AU Pads could be a good choice. Or Midi Designer Pro 2 or Lemur if AUv3 isn't critical.
Yes, 13 pads with shift would be okay. Actually “game” was used loosely. There wouldn’t be any game logic inside Mosaic. I just want to use it as a kind of musical typewriter to make musical phrases from words or sentences. The game would be to see what music might be made with using only those notes. That would be the simple rule.
It’s been well documented now by analyzing texts how letters can be ranked by usage. My main idea then is to map notes to a root such as C. The letters that are most used would be mapped to the more ‘harmonious’ intervals and the lesser used letters mapped to more dissonant and spread over two octaves. There are so many combinations of letters, e.g. words, that it would have to come up with a lot of variety but not just completely random.
The other apps you mentioned would work but Mosaic is more accessible. And AUv3 would be necessary because I want to step record into Helium or Atom. Duration and phrasing would have to be tweaked later.
I’ve tried doing this already but a musical typewriter would be helpful.
Anyhoo, thanks for the input.