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.
Clip/Pattern control in Atom 2
I've hit a wall in trying to get this to work. Experimented using the settings as described in the manual, and not getting anywhere. Hopefully someone can see what I'm doing wrong.
The problem:
In a test setup to explore this, I have:
Three instances of Atom 2 running in AUM. Two instances in a single MIDI channel with clips that are in turn output via a piano app on an Audio channel. Those instances each have a clip, let's call them Clip "A" and Clip "B". Each clip in turn has two patterns each, call them Pattern 1 and Pattern 2. So we have A:1, A:2, B:1 and B:2
The third Atom 2 instance is running in a second MIDI channel as a "song sequencer" sending notes to the first two instances with the song clips.
The goal:
For the "song sequencer" to send MIDI notes to instance A and instance B to launch and play the two clips and four patterns in order, launching first Clip "A", playing pattern 1, then repeating Clip "A" playing pattern 2, then launching Clip "B", and playing first pattern one, then again playing pattern 2.
Pretty simple really. I have Clip "A" launched by note C-1 and Clip "B" launched by note C#-1. Within Clip "A", pattern 1 is associated with note C0, pattern 2 with C#0. in Clip "B", pattern 1 is associated with D0 and pattern 2 with D#0.
If I adjust the loop in the "Song sequencer" clip, to only launch Pattern "A", playing first pattern 1 and then pattern 2, it works perfectly. If I shift the loop to the section that controls Clip "B", it launches Clip "B", first with Pattern 1 then shifts to Pattern 2 exactly as I want. In both cases the clips play once and stop.
The problem:
When I enable the entirety of the "Song Sequencer" clip, things go off the rails.
Clip "A" launches, pattern 1 plays, then pattern 2 plays. So far, so good. But then Clip "B" launches just fine, but always starts playing pattern 2, not pattern 1, and when the note gets sent to play pattern 2, it continues playing pattern 2. The clips stop when the "Song sequencer" clip ends (looping is disabled in the Atom clip for the song sequencing)
What is interesting is that if I open the piano roll for both Clip "A" and Clip "B" and watch them, I note that Clip "A" is showing a little pop-up every time a pattern change note is received, showing "Playing pattern 1" and "Playing pattern 2", even when that clip is NOT "listening" to those particular pattern-change notes.
I have the launch controls set to the "hold" style in which the clip remains launched until a note off is received. I have played with the various other settings to try to see if any of them.
So, after spending several days trying to solve this, I'm coming here hat in hand hoping someone has a suggestion as to what I can do to fix this.
Thanks!
Comments
Is there any chance you could post the session here? This one could take a month to unravel through question and answer posts without something to look at.
I assume you mean the AUM session? Brand new here. Let me see…
Ok, the session file isn’t allowed here, but compressed as a zip file we’re good. All clips/patterns are just 4-bar arpeggios.
I poked around in your file and managed to get it to work how you want.
I just switched the notes you used to trigger the clips vs. the patterns, meaning…
I used notes starting from C-1 to trigger the patterns, removing the note offsets you set in the Patterns pop up in Atom.
I used notes starting from C0 to trigger the clips.
Not sure if it’s a bug related to the note offset, but I suggest leaving the note offset alone for pattern triggering. Each individual clip can have up to 128 patterns, trigger able by the entire midi note range, if you leave the note offset alone. This seems to be the intended use scenario.
As a side-note:
You can also use the same 2 notes to trigger the patterns in either of your clips. Only the patterns in the launched (playing) clips will trigger. If the clip is currently stopped, the patterns won’t trigger. So, you don’t need a unique note per pattern for all clips. But for each individual clip, you do.
Use LK instead, it's a lot easier than wrestling with multiple instances of Atom 2 and you can get things like clip/follow actions and midi cc automation.
Thanks - yeah, that fixes it!! Weird. I'll follow your advice and avoid the note offset when controlling patterns. It was literally the last thing I would have tried, so your efforts are much appreciated.
I was thinking that should be the case, but was trying to play it safe by using a unique set of notes for each pattern. When I tried your solution, I did indeed use the same triggers for patterns in both clips, and that seems to work fine.
Thanks again for finding a solution to this. I think I'll see if I can't forward this to Victor to look at, as it does seem like it might be a bug given what worked around it.
Thanks for the suggestion. However, I really resist the temptation to head off and invest in another app when I encounter a problem in the app I'm using. LK does appear to have certain advantages over Atom 2, but Atom 2 is really well-suited to the work I'm doing right now. LK is definitely on my radar so if I start feeling like I'm being limited by Atom 2, I'll give it a look.
What are your thoughts on the clip launcher in Drambo?
I love it. LK and Drambo both have incredible features for clip launching.
LK has a few advantages so far: support for external controllers while Drambo requires midi mapping for clips. LK also has clip and follow actions like Ableton while Drambo has repeat counts per scene to use as a song mode.
Drambo is a bit faster since it uses a step sequencer for entering notes but LK has a built in melody and chord pattern generator.