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
Another cool idea right here! Suddenly everyone loves empowering drummers. Who knew?
Suddenly everyone loves empowering drummers. Who knew?
Bout time! Makes up for decades of drummer jokes.
Nah. These scripts can all be fed by Rozeta. Rozeta don't drink and don't steal your girlfriend either.
😄
The interface is pretty full. There are no switches or pads left, without resorting to lots of interface complication. I can maybe see adding a knob for hold / reverse / random. But I wouldn't add it as another note-selectable thing as that would really messes with the existing note assignment code and design. I guess if I did add it, one could use another small script to convert selected notes to cc's for AU parameter mapping.
I'll think about it. I wasn't planning to re-open that script though. Of course, anyone is welcome to make modified versions.
I'm not too sure I understand your request. But at first glance it seems to me that putting a far simpler script that collapses all notes coming from drums to a single note, configurable by bar in front of The Cordulator, or other chord scripts or apps would be an easier approach.
For instance: drummer sends all kinds of notes in a bar, script translates those to C for a measure, 2nd script makes those into chords. Next measure the first script changes those to another note and the 2nd script makes those into another chord.
I think you could approach what you're thinking of modularly and accomplish what you describe with much less coding and with more flexibility.
I mention the Chordulator because it has options for leading tones and voices, all degrees of chords, etc. It also has the ability to compensate for a real drummer's incredible rock-solid precision by adding humanization and randomization. These things normally can only be achieved with prodigious amounts of alcohol and other adult substances. So, something like this could actually be a health benefit for drummers as well.
@McD Not sure I quite understand this either. This obviously can’t be “off the grid” since you would have to define a “bar” by tempo/length? Or would you make it for every “n” notes change the input note/chord? I have to admit it was the use of long strings of numbers that confused me in your previous scripts. I’m not good at theory and it really slowed up my workflow trying to conceptualize multiple rows of numbers. Others may find it fine and prefer your method. To each their own I guess.
Could you stack several instances of hypno sequence each with one step and playing it’s own note of the chord you want and then have other presets doing the same but with different chords and then switch between all the presets via the control channel?
Maybe I’m just not getting what you’re trying to accomplish.
Now that I think of it , I will try out an AUM project where I stack several hypno sequences all with multiple notes for chords but have each instance a different amount of steps. Instant random chords after the first pass.Hit reset to start from the beginning and back to safety. Could sound really cool or really terrible.
Some call it jazz.
After thinking about this one some, I decided to add it as the last feature addition. v1.20 includes a knob for sequence direction. thanks for the great suggestion. 👍🏼
Hopefully I didn't introduce any bugs. If so, then I'll fix 'em, but won't be adding any further features.
One strike.
Two Strikes.
Only one strike left so I'll have to take a swing at the ball and make something that
matches my idea and see if it's useful.
It would leverage the DAW's BPM and be "on the grid".
An example for Chord Progression vi-IV-I-V = 6 4 1 5 = A minor F C G
Bar one: every drum tap produces note(s) on the target synth taken from Chord A minor.
Bar two: notes are produced from F
Bar three: notes from C
Bar Four: Notes from G
It will probably sound a lot like a variable Arp function by pre-selecting notes along chord lines: A Drummer's Arp function.
This list of numbers is just the scale notes for a given chord
1,8,15 = Tonic
3,10,17 = 3rd
5,12,19 = 5th
2,9,16 = 2nd and 9th after 1 octave
1,3,5,8,10,12,10,8,5,3,5,3,2,1,2,3,8,5,10,8,12,15,17,12, etc.
If you tap through those notes you get an arpeggio. When the bar changes the
notes are shifted accordingly to match the chosen progression.
@McD I think I get it now. On grid/ scales not chords/changes automatically on the first beat of every bar. Is this right?
If so you could get the same end result performance wise by using the hypno seq and preprogramming all the scales you wanted into the preset slots and in a separate track in your DAW put a note on the first beat of the bar that matches the control channel in Mozaic and the note that corresponds to the preset(scale) you want. Different route but same destination. Would this work for you?
It could be written to use any time division: bars or some number of beats. Songs have
precise chord progression road maps so dialing up a script preset that matches a song could be useful to someone playing along with a band or pre-recorded tracks that follow a
chord map.
My concept is not to play a scale but to play chord notes in the context of a scale.
6-4-1-5 means Am F C G in a C major context.
6-4-1-5 means F Dm Em Am if A minor is the selected chord context.
Applying Arp patterns to these chords with a time reference is the basic idea.
Then the inputs are the progressions:
1-4-1-1-4-4-1-1-5-4-1-5 (12 bar blues)
6-2-5-1-6-2-5-1-6-2-5-1-2-5-1-1 (I got rhythm)
The most interesting chord progressions tend to not stay strictly within a single scale
since they use a lot of secondary dominants but that's another detail to consider after
the basic script exists. Scale steps could be defined in parallel with chord qualities in another indexed array.
You're current script uses defined sequences and I think you're thinking of them as scales.
They are really melodies and can be selected from any potential harmonic context: modes,
or chromatic 12-tone choices. As a result they would be locked into a fairly short potential chord progression unless the sequence was over a hundred notes long and then your
progress through the sequence is a function of how many notes you play per second...
play slow and it takes 20 seconds and play fast and it happens a 2-3 seconds. This doesn't
help a drummer coordinate with other musical sound sources in time.
I realize you play solo and this application has very little value for you but I suspect if it exists you might see value in a sequence that morphs over time even if that clocking is
not obvious to the audience... set the BPM to 20 and makes the chords change every 4 bars and the morphing between chords would happen every (4 x 16 x 60/20) seconds.
Anyway... such a script does not exist (yet). It's just a concept awaiting implementation.
I basically seeing if I can get someone the "whitewash the fence" just for the fun of the work. There are people that make scripts just for fun.
🙏🏻 Thanks!!!!
That’s too funny man...
@wim Are you going to make the UPDOWN direction the 1234321234 version or the123443211234 version (doubling the first and last note)? I think I prefer the former but am not sure if someone else might prefer the latter. What do you think?
I will really like the random setting for certain lead type melodies.
Hey guys- just thought with all these directional options now we could stack several of these with different settings/octaves and note values (using rests) and we could have a round robin version of Fugue Machine!
It's the former. I probably should have made both, but liked the idea of having just five modes so that 12:00 on the knob could be normal (forward) mode. I always like double-tap to get to a default setting if possible.
V1.20, with the direction modes is up on patch storage. You should probably keep the v1.11 script around in case I screwed anything up.
(P.S. "Hold" is a little unintuitive IMO. It holds the sequence on the next step, not the one just played. I kind of feel like it should hold on the previous step played, but making it work differently was more involved than I wanted to get into with the script.)
@wim 👍🏻
About the "Hold" would be great to hold the current note being played... its not much useful for me as is.... Its difficult to improvise and decide to keep something you still not hear....
Thanks wim!!!!
@wim HOLD is actually the one setting I probably wouldn’t use. If I wanted a single note repeated, I would just save a single step on another preset(s) of a note(s) I might want to repeat and select that via the control channel.
Yeh, sorry about that. No plans to change it though.
maybe ... if suddenly an idea how to easily do it pops in my head, I won't be able to resist cracking it open again. That's been known to happen. But not planned at this stage and probably won't be intentionally thought about.
@Synthi - flipping back to the advanced controls page to get to the sequence direction knob isn't the most convenient thing in the world either.
However, you can easily change the order of the knobs with a quick edit to the script. There's a section right at the top that lists the knob numbers. The four knobs on the pads page are numbered 0-3. All you need to do is to swap any of the numbers assigned to the knobs. For instance, to swap "Gate" for "Direction" you'd change
k_gate = 3tok_gate = 9andk_direction = 9tok_gate = 3.Press Upload to see the change, then be sure to save the script.
Thanks! I`m planning to use MIDI buttons for sending the CC commands to the script (same CC number, different values) , not using the screen.
About changing the way the HOLD works now, lets pray for a brilliant light in your head!!!
I had a feeling as soon as I said that the easy answer would come to me. Turned out to be three lines of code. v1.21 now holds on the last step played, not the next step.
Magic @wim !
I fixed a bug with the Gate knob not updating correctly when selecting pads. It doesn't affect behavior other than updating the knob correctly. v1.22 - hopefully the last.
Maybe I should post this in a Rozeta thread but it would be awesome if there was a master pattern changer that could change all the different rozeta instances at the same time. Maybe that could be done by Mozaic? @brambos
You shouldn't need Mozaic to do that. You just need to route anything that can send midi notes to all instances, then set them to "MIDI triggers patterns". This could be a keyboard, or even a Rozeta Cells instance set to a slow time division such as 1 bar. Atom is good for this too, since it can be set to slow time-scale.
@wim oh okay awesome! that seems pretty straight forward. thank you!