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
Here's an old video showing how to get it running (not with Atom, but the process is the same regardless of which MIDI AU you use):
This would be pretty nice when used in tandem with the slice tool in Atom orchestrators, to force notes to sound at the start of a loop. However, a nice feature would also be to force that to happen, even if the notes start before the loop start point.
First time I'm hearing about it. If you have some steps to reproduce, let me know.
Does this video help? I am trying to find a pattern to this bug but not successful so far.
I think that's the same video you uploaded above. If you find some steps to reproduce, let me know.
Right now what I find is, whenever I am enabling/disabling the loop with legato mode or loop with latch mode for the first time after creating the clip I can reproduce the problem i.e after a few plays the notes don’t sound. Also, the playhead becomes a ghost playhead. This gets fixed with an unlaunch and a launch. However, same thing happens after a while. Also, point to note: this doesn’t occur when the clip is already playing. Only happens when I am pausing, resetting and hitting the play button in AUM.
Ah. I think I have reproduced it. Disregard my above comment. The issue occurs when I am disabling loop in the clip. Playhead turns into ghost in subsequent plays.
@blueveek Do let me know if you can make it out from this video.
Right, thanks for looking into this. It looks like you're rewinding playback in the host before the clip has a chance to unlaunch, when loop mode is off. If you just let it play until the end of the quantum for 3 more beats, the clip will unlaunch as expected (at least it does in the current beta, I seem to recall there used to be a bug around this at some point in the past). This behavior is intentional, but I can see how it could be confusing. I hope to revamp the loop settings at some point in the future.
In-app dark mode toggle coming in 2.0.9:
...also for reduced motion:
Many thanks! But only one remark: Earlier(I may be wrong?) when looping was disabled or Stop at Clip End was enabled the clip would show that it unlaunched itself after playing one round. But now it doesn’t get displayed that the clip has unlaunched itself! Still remains launched visually.
Yes, I’m hoping to release 2.0.9 soon which addresses this.
Thanks! Another thing that seems unintuitive to me and also cannot remember if it used to be like this in the earlier versions. See video below where I have disabled Loop, enabled Stop At Clip End and am recording notes from my midi keyboard. But the issue is: Ideally I would want the recording too to stop at the clip end given my settings. However, although the clip stops at the end (without visual feedback as already discussed) the recording doesn’t and keeps looping without any playhead to be found. In all probability, it may not be a bug and am happy to be provided a different perspective on this!
@noniman93 This is the same issue again
Thanks for bringing it to my attention, and I hope to release 2.0.9 soon.
Oh my bad! Many thanks for your attention as always. 🙂
In case you are still wondering, I’ve just updated the Atom+NS2 guide in the wiki with how to record the output of Atom. See the Advanced Topics -> Recording MIDI section - https://wiki.audiob.us/doku.php?id=wiki:hosting_atom_2_in_ns2
Excuse me if I overlooked something in this thread, but I can‘t get automation working on some AUs hosted in AUM, specifically Phasemaker and Zeeon. It bugs me, because it works in Nanostudio and Cubasis 3. I want to use the fader knobs of my Nanokey Studio to automate filter cutoff, for example. Interestingly, sustain and pitchbend automation is working regardless of the used AU, so I think I routed everything correctly inside AUM, because some CC messages seem to be sent. Also, I can automate every parameter in Ruismaker FM and in every IAA instance, where MIDI learn is available. Can anybody help me here, please?
A couple of things on the checklist:
1. Make sure that MIDI learned parameters (knobs/sliders), either learned through the AU itself, or through the host's MIDI learn functionality, have the desired effect of modulating those parameters.
2. Make sure that you've routed your parameter modulation source (external keyboard etc.) into Atom, then Atom into your instrument.
3. Make sure Atom is recording. If you're recording multi-channel data, make sure it's in MPE mode.
Atom will record all MIDI exactly as sent, on the exact sample its received. Let me know if anything on the above checklist helps you.
Update 2.0.9 is out
16 channels in one instance
Tips:
More automation and multi-take recording features
Other new features and tweaks
addEmptyActivePattern,armScene,getAllFocusedClips,hasFocusedClips,getAllRecordingTracks,hasRecordingTracksmethods to the scripting sandbox.my personal favourite
Sorry I cant find this workflow…. Cant seem to find it in the manual. There is a way to have multiple channels playing different parts from one instance of Atom 2 correct? I for the life of me cant figure it out. Can someone point me to where Tom or Victor showed us this…. Just for example I would like to have a single atom playing both a drum sequence and a synth sequence on different channels. 😬
I seem to remember you're using AUM, so the details below are for that host.
To record using AUM's builtin keyboard:
1. Create an Atom instance, route it to your instrument, filter MIDI channel 1.
2. Tap the wrench on the bottom right in AUM, select channel 1, route it into Atom.
3. Record.
Easy. Now, to add a new "track":
1. Add a new instrument, route Atom to it, filter MIDI channel 2.
2. Tap the wrench on the bottom right in AUM, select channel 2.
3. Record.
Pretty simple? Now, some advanced stuff:
1. Open the "Channels" panel in from the top left toolbar inside Atom. See how you can hide/show lock/unlock channels there. See how you can edit multiple channels at the same time, or lock them like you would lock Photoshop layers.
2. Manually draw some notes. These notes will respect the first targeted channel.
3. Select notes, move things around. Operations will respect the targeted channels (visible + unlocked).
long press on add to choose channels
press channel to see options
Jesus. That was too simple. Your programming is too good….. I kept looking for to assign the track in atom to different midi channel.. but boom its fairly automatic. I am sorry for bothering you. Thanks!!!
I double-checked the learned parameters and ensured that they functioned as expected in the respective AU. When I also checked the routing matrix in AUM I realized that I have not connected the Atom instance to AUMs built-in MIDI control. Now it's all working fine. Thank you for your support and your great work with Atom (2)!
Thank ya for the update!
Another feature packed release! @blueveek Thanks so much for all of these amazing new improvements that you keep adding.
Patterns with easy editing of multiple channels allows for the Helium “song mode” workflow in Atom which I know clicked with some people and will be great to have as an option in Atom for quickly testing ideas or building out songs from self-contained patterns.
I also like the new double-tap functionality, it is one of those small things that I’m going to wonder how I lived without and works reliably so far.
Thank you
My philosophy is to stay in harmony with the host or the OS as much as possible. If it can be done outside of Atom, then it's a "standard", and Atom should respect it, rather than reinvent it. In this particular case, it's actually less code and less work for me, so it's a win-win.
Glad you got it working! This kind of granular control over MIDI routing trips me up as well sometimes. Anything that's "low level" has more ways of failing, but also more ways of being used creatively
When multiple patterns are being triggered from a clip, how is the timeline maintained in the case of unequal loop lengths across patterns? I ask this because there is no concept of sync quantum(or is there?) in between patterns as there are in between clips!
I remember life before atom 1 and all we wanted was an auv3 piano roll that had just a couple editable parameters like velocity, and now we have atom 2 which exceeds the expectations and brings in lots of fun ways to build tracks.
Really loving this app and the progression is outstanding
Amazing work, @blueveek
Please take a break! 🙏
Amazing guy!
@blueveek - do you ever sleep?
It’s a smile on my face every time I running Atom2 together with AUM - supergreat combo!