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.
Using Atom 2 in different DAWs
(Going to start moving some of this to the wiki:
NS2 tutorial: https://wiki.audiob.us/doku.php?id=wiki:hosting_atom_2_in_ns2
)
I am going to spend some time working my way through my DAWs and seeing if/how Atom 2 adds value to each. I’ll update this post with what I find but do chip in if there is anything you would like to see explained in more detail or if you have already done some of this and have tips to share.
Here are the settings I am currently using, important parts underlined:
I’m not planning on going into any detail about setting up Atom itself in this post as I’m sure there is some excellent documentation on the way. I am also not going to suggest that this is a replacement for how anyone is currently working with their DAW. There are some obvious downsides, for example you lose the visual guide to what MIDI data is in each section on the timeline.
NS2
Moved to full tutorial at:
https://wiki.audiob.us/doku.php?id=wiki:hosting_atom_2_in_ns2
MultiTrack Studio
Atom should be added in the MIDI effect slot for the track. You only get one of these per track which is why the pattern change update makes this workflow viable.
The first thing I notice about MTS is that note velocity can start at zero so the mapping goes:
Vel 0 = Pattern 1
Vel 1 = Pattern 1
Vel 2 = Pattern 2
Vel 3 = Pattern 3 ..etc
Like NS2, MTS has the concept of a clip (called patterns) which can be modified and the content of the linked clips will automatically update:
One thing I hit after adding a second track is that you need to make sure that the “switch channel” matches the channel that the track it putting to, e.g.
The instrument, in this case the MTS internal instrument, has an assigned channel:
This channel typically is the same number as the track but can be changed. Whatever it is, you must set this in Atom to match it:
The interface for MTS has in the past made it difficult for me to use to arrange a song. Now that the song information is decoupled from the timeline, each track can be collapsed to show only the song patterns and so now I can arrange up to 4 tracks at the same time:
The MTS bar looping tool is easy to use, just double click and drag, so it is straightforward to highlight song parts to loop while you build them up. See the loop points between the first and second bars in the capture above. Note as well that you must extend the loop point before and after the part you want to play otherwise the triggering is not consistent. It is actually more consistent in MTS than NS2 but not perfect unless you do this.
NS2 shows much more information at once which is why I prefer it for arranging but MTS is capable in other areas which means I will not dismiss it out of hand for arranging in the future with this new workflow option available.
You have full access to the exposed parameters of Atom 2 in MTS and can control them from the automation editor:
Audio Evolution (temporarily abandoned)
Add Atom 2 into the AU MIDI slot on the second “page” of a MIDI instrument track.
Changing velocity using the edit menu in the piano roll is the easiest I have come across so far as the different velocity steps snap nicely into place without overshooting like most DAWs
Blocked on AEM, need to do some research on how to route MIDI around in this app as I’m randomly hearing Atom do its thing but I do not believe it is reacting to the change notes properly.
Going to move on now I think. Once this is all working then AEM would at least benefit from Atom’s alternative piano roll as I never really got on with the one in AEM. AEM does have clips but they are unfortunately not linkable so not as useful as in other DAWs.
ZenBeats
I stopped using ZB a while back so there could be some things I have missed in my setup. If you spot any then let me know.
I needed to look up how to add Atom to a track. You need to long press on the AU name after adding it and a menu will pop up with “+ MIDI Effect”.
ZB already has clip launching built in to it so I was keen to see how this would work in conjunction with Atom pattern launching.
(removed experiment with using note triggers, basically it does not work. It is likely that ZB has the same problem as Auria where simultaneous pattern switch and hold notes are not sent to Atom in the way it is expecting them.)
Velocity triggering seemed reliable, however here is the velocity controller:
No velocity values 
I found though that the dial is fairly forgiving if you use a pencil. What sort of worked was to have the transport playing with Atom 2 and the velocity control window open at the same time. This way I could adjust the velocity until the correct pattern was being triggered:
Using velocity as the pattern switcher and using the same trigger note for both velocity and hold allowed me to create a sequence of clips in the ZB clip launcher mode which seemed to play correctly. One oddity though is that some clips only worked going forwards, e.g. clip 1, 2, 3 played OK but if I then tried to manually trigger 1 then the first trigger would be missed. Odd.
Limited success with ZB then from a pattern changing point of view. On the positive side, Atom does respond to the clip controller notes which means you could go back to using one Atom per pattern as things were before the new update, assuming ZB lets you add enough MIDI plugins. It also means that Atom can be used as a piano roll replacement in ZB just by having it set to launch with the host.
ZB also lets you access the exposed Atom automation.
Auria Pro
I finally managed to get pattern triggering to work after experimenting with numerous options. The only reliable way of triggering patterns is via velocity. Using note triggers does not work if the pattern and hold triggers are sent at the same timestamp (like ZB). This method requires 3 tracks per actual track of music though so I’m hoping there is a way to consolidate some of these routings! Rather than try and describe it I will just post screencaps of my setup so they can be dissected later:
Comments
Sounds good.
In answer to your first question...
Atom2 adds value to 'every' host - since I don't know any host that has this level of control over hardware integration, scales, swing, quantise, exotic time signatures, and not to forget... dodecuplets
Also.... how the hell else are you gonna get perfect triplets in Drambo
This is a great idea for a thread, thanks.
Corrected
Just want to add that there is indeed a small bug in the current version where switching patterns with incoming velocity is offset by 1. Will be fixed in the next version.
That will do for this afternoon. Got blocked on AEM so will need to come back to that the next time around unless someone else more familiar with it is able to get it working.
Added ZenBeats
Impressed by your dedication.
Note - Although switching patterns by velocity is a great party trick and workaround for NS2 limitations (and allows for some mind-bending workflows) I also find it much easier to program pattern switches by MIDI note.
Thanks, it is a good way for me to refamiliarise myself with some of my less used DAWs and see if I can squeeze any more life out of them with Atom.
Yes, I think I will end up going the notes as triggers path too. I have considered adding StreamByter in the mix so that I could have it map velocities in ranges of say 1-10 to 1 and 11-20 to 2 etc. This way I would not need to be so accurate with setting them.
Edit: one observation is that most DAW makers do not test people entering note zero as it can be very difficult to do with scrollbars etc getting in the way!
i think atom moved to the forefront all those marginalized classes of notes!
let’s shout it together: WE WANT C-1! WE WANT C-1!
Updated with Auria Pro.
I think I'll add a switch value offset slider in the next version. Modulo works fine, but sometimes you just want to start at C4 you know?
That would certainly be welcome!
Updated NS2 section with a tip for selecting patterns.
I’ll update the post again when the next patch drops but for now I’m pretty settled with my NS2 workflow.
Added the use of Slate as a controller track which makes triggering patterns more user friendly.
Thank you immensely for documenting all of this @MisplacedDevelopment. I'll be forever grateful for you helping people set things up.
@blueveek No problem. I think I’ll split off the NS2 part at some point into its own guide as there are lots of little extras like saving MIDI FX chains with pre-configured Atoms which would be useful to go into in more detail.
Updated to take account of the velocity fix. Added idea for having second Atom instance per NS2 track for recording only. Managed to get basic Atom working with Auria Pro by using MIDI route which is good news. Will need to investigate further to see if triggering also works. Edit: it doesn’t
Added a full NS2 tutorial to the wiki:
https://wiki.audiob.us/doku.php?id=wiki:hosting_atom_2_in_ns2
I think I'm now also starting to even fully grasp what's so nice about this setup.
That's actually super cool.
What a great addition to the wiki! Thanks for your effort. I look forward to trying this out.
Very interesting. Lot of effort on this. Great job.
And NS2 has a tempo track which is also super cool in this context.
Cheers all! Do suggest any refinements as this is a work in progress so if there are further corners that can be cut then I’m all ears.
I think I managed to finally get Atom responding to pattern changes from Auria clips. I’ll check my working then update the guide if I’m correct. The key is to route MIDI using MIDI Route rather than the internal routing. This technique may also help with similar issues seen in other DAWs.
Edit: Auria section updated with working but convoluted setup. Interestingly this is the only DAW I have come across where looping works when the start of the loop coincides with a hold control note. I wonder if this has something to do with MIDI Route.
Spoke too soon, the control notes must have been overlapping in a certain way that made this work. A copy of the clip immediately following failed to correctly change patterns so this is still too unreliable.
Edit: using velocity as the pattern switch with the same note as the hold trigger seems reliable, as does moving the trigger and pattern such that they do not occur at the same timestamp (though that obviously messes up the timing of the pattern).
Wait a minute… can you also control the Atom 2 clip launching by a launchpad when running in another host than AUM?
yes, of course. Atom2 detects compatible Launchpad hardware and makes the auto-connection in any host.
Thank you!