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.
ATOM Piano Roll update is coming soon
This discussion has been closed.
Comments
Cheat code for the bassline:

Most likely as the only thing I would map would be velocity to transpose.
This way each instance that gets triggered would get their individual transpose value making it easy to re-use for example a bass-sequence by transposing it using the velocity value on the 'trigger events'.
Another option is naturally to add more controller sequences and use the note values to transpose the other sequences.
On thing I like about LK is that all the sequences can be kept in one instance and for me it makes it a lot easier to organize than having one instance per sequence.
I guess it's possible to edit the other Atom 2 instances from one window via some kind of pop-up to switch between what is shown. Honestly the screen gets very 'busy' and 'crowded' with multiple instance icons floating around.
Time will tell how it works in practice but somehow my gut says there's only need for one Atom 2 instance to sequence 16 midi-channels (each with their own pattern etc.) and that would cover most my needs already.
Cheers!
Woah, thanks man! Will definitely try this later 💪🏼
@blueveek I take it it’ll work seemlesly with an Aurturia Keystep pro?
@blueveek please test with ZenBeats before releasing. I purchased v1 but can't use in ZenBeats as it gets quarantined for some reason. LK doesn't so there's no inherent reason why it shouldn't work. Might be worth checking in with @MatthewAtZenbeats
OK.. Prayers have been answered.. 🙏 😁
@tk32 Thanks for that demo.. perfect.. 👍
@blueveek Thank you for this beautiful work of art.. 👏
Automation Panel? Heart.. be.. still..
Here’s another quick preview (silent this time)
For those of you who don’t own a Launchpad fear not... ChordPolyPad makes an excellent virtual launchpad...
Likewise LK and Mozaic
@tk32 Now that’s simply genius! 👍 I will be using that one..
I mean, Atom 2 is an audio unit> @tk32 said:
Fantastic, sir!
And I assume there’s an easy way to trigger an atom instance but have the clip not launch till the next bar (or beat or whatever)?
Most certainly. The launch-syncing options in this are sublime
“> @tk32 said:
Awesome.. Now this is next gen stuff here! I can’t wait!
Extending the idea of a virtual launchpad.. I now have a template that mimics Ableton/Push and includes 7 tracks with 7 Atoms each.
You can launch scenes, and the patterns choke as you would expect.
This will be given out free for everyone when Atom2 launches.
#AbletAUM
@blueveek @tk32 @winconway
I’m not sure what’s in place for capturing cc automation - I presume the usual editing options.
FR for the future:
There is always a disconnect in me when recording cc automation. Most AU instruments won’t transmit midi ccs, making you run circles in order to be able to record automation. Some midi editors come with a slider for each cc line enabling you to record automation in place.
@tk32 You are the man!!!! Despite what I hear on the street. 😂. 🤪
Will this be able to switch clips using the same instance in the new version?
I think this was (briefly) exposed as a parameter in version one but didn’t show in all hosts.
I’m currently spending my music time making atom 1 loops that I can arrange and trigger when atom 2 is out. Is there gonna be a straightforward way to get midi out of atom 1 into atom 2?
Presumably just stick atom 2 in an fx slot and press record?
All nice things.. but, how much longer > @gregsmith said:
I am doing the same... I asked if ATOM 1 Files will be read by ATOM 2... No Answer.. I may be wasting my time..
If you’re saving them as Atom1 presets in AUM for example and if Atom2 is a separate app then I don’t think they would be compatible - happy to be wrong on this though.
Maybe we can get an answer from the beta testers...
Sorry, I missed your question when you asked it. I'm trying to keep up: between my main job, my "second job" working on Atom 2 and this forum, some questions are likely to slip by
If Atom 2 is released as a separate app (which seems likely), then Atom 1 presets will be inherently incompatible with Atom 2. I have not coded in a way of importing them yet – that's not to say that it's completely impossible, it's just that I didn't get the time. Of course, the easiest workaround is routing Atom 1 into Atom 2 and recording. You should be able to do that all at once for all clips.
That’s definitely good enough. No need for anything more sophisticated imo.
Looks promising! The ChordPolyPad scenario shown here is certainly also possible with Tonality‘s very powerful AU Chord Pad module. It may not look as elegant but it also offers grids up to 12x12 customizable color coded pads and the advantage of connecting to patchstorage for easy exchange of many future templates to come.
Just bought a launchpad in the meantime. Can’t wait to try this.
Yeah, Win is buying up all the launchpads because he predicts demand will increase dramatically once people see how well they integrate with Atom2.
As a bonus, the are very well built and have fantastic integration with Ableton (natively), and Bitwig and Reaper (via DrivenByMoss scripts).
...and if all else fails, just plug them into a usb charger for a trippy night light.
That’s one expensive night light 😝
Maybe it’s me.. but.. this seems like overkill.. Maschine 2.1 introduced a slick solution of having one ‘long’ clip which can be divided into patterns along the looped timeline..One pad can reference a looped section of the file...
Edit.. the idea is you can have more control of your project.. without having so many instances of ATOM.