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
Since you’re probably recording a take inside an empty pattern just use “clear notes” in the pattern.
@Fryer99 you can also use the “fit” button to zoom all the way out to make global navigation a bit easier.
Unfortunately, this is only the case if the sequence is short enough (I think the limit is something like 30 bars. If the sequence is longer fit only shows the last 20-something bars -- at least on my 9.7 inch screen.
Some shortcut for getting back to the beginning would be handy.
Thanks!
thank you!
Good workaround, thanks! is there any limit to the length a pattern can be? 64 bars, 128 bars etc?
Sure would be, for me at least, something good to see in a future update
There isn't a limit (at least not in that range). I have presets with 32, 64, 128 bars -- and I pick based on what I think I need.
a quick follow up... thanks to all who commented and helped steer me in the right direction. played and worked with Atom2 a lot last night, it's really quite brilliant, combining traditional MIDI sequencing with what makes iPad so great. Wonderful application, looking forward to continuing to learn, and for the CC editing to be implemented!
I recommend trying it with Apple Pencil for fast toggling (thanks to the author for adding my request for this) by double tapping the pencil
Nice follow up! 👍
Hi all, im sure its in here somewhere, but how do I use one instance of Atom to send different midi clips out to different synths.
for example, if I load something from Songen and it exports as 4 different midi Clips, is there a way to load that into one instance of atom and have the 4 different clips play 4 different synths/drum machines through 4 different channels??
I would like to have to just open atom once, and not open 4 different instances and have to load and reload the midi each time.
You can do it, but it's not really how Atom is geared to work. The name "Atom" says a lot. It's not really meant to be monolithic, but a one-purpose per instance tool. That said, it's possible to do what you want.
You would need to import the clip, which will place each channel in a separate pattern in the instance. Then, set up an empty pattern to be the main one. Then, one channel at a time, copy a pattern notes to the clipboard, hide all but the channel you want to send those notes to in the main pattern, and then paste the notes.
Atom probably isn't the best tool for you then. LK or Helium might be a better choice.
@wim thanks for the reply. I think i get it, will give it a shot a bit later. I have LK, but i really like Atom for its probability, velocity chaos, swing etc,,, Ill try out Helium as well.
You can have one pattern with multiple channels playing simultaneously in Atom. Just switch to “filter mode.” Honestly though, Atom shines when you use multiple instances, all playing their own clips.
Here’s a quick example of importing 4 clips all recorded on channel 1, converting them to their correct channels, then merging into a single pattern. If Songen exports into the correct midi channel importing would be easier but basically the same. Hope it helps.
If you mean can you have multiple channels of MIDI, you can have Atom send MIDI to different MIDI instruments from one instance -- but you can't change those instruments' clips independently. If you want each instrument to have independent clips that can be triggered independently, you will want to go with the multiple instances of Atom setup that wim mentioned -- which was the original vision of the dev -- and which works quite well. When used that way think of each Atom instance as a cell in LK.
For multiple instances to really work well, host apps need to catch up on better control-ability via things like launchpad. It’s nowhere near as easy as Push 2 for instance to duplicate clips, update settings across clips, or open a clip for editing.
I set up a TouchOSC template to make a pattern launcher for atom. I can launch and fire off patterns using PC 0 for the first bank of 8 patterns . If I setup a second instance of atom on the same midi channel and switch the PC offset to 8 it will fire off the patterns of the second instance but it also triggers the first instance of atom. I’ve double checked my setup with MIDISpy to make sure I didn’t miss anything. The template is configured correctly and outputting where it should.
I can switch everything up to Midi CC or Note info but I’d like to use PC as im already running a bunch of custom patches for other controllers on CC and note info. I’d like to be able to have the vast majority on one midi channel. Maybe there is something with Midi PC data I’m unaware of. I generally just use CC and Note data.
Any ideas?
To use the same midi channel, use different CCs for your different instances.
Yes. Using the offset for patterns does that for Atom, but my issue with PC and not CC (I know, shouldn’t matter which) is that regardless the 2nd bank triggers the 1st bank as well. There are no overlapping values set for the launcher I created.
Maybe I will just reformat to use CC and not PC and see if the problem persists.
I just tried something that I think matches your setup, two atom’s listening to pc messages, one 0-7 and the other 8-15. Instead of touchosc I used the keyboard and a streambyter note-to-pc script. Everything seems to work as expected. Did I get your setup right?
Yeah. That’s pretty much it. It’s just a weird problem, as it’s a super straightforward setup. That’s why it’s been a strange issue.
Thanks for taking the time to post a video!
It may be (I think that it does this for notes) that it use MODULO math for the PC numbers -- which I think is what it does (or used to do) for note numbers -- so that values wrap. I could be wrong but my memory is that is how it used to work.
@Shiloh hmm what, exactly do you mean by “trigger the first instance?’ Is it changing patterns or something else?
I realized that I only have it double trigger when the AUM transport is running. Does anything different occur when you have the transport running on your example?
The patterns wrap with PC as well. I’ve made sure to load 8 patters per instance to correspond with the launcher I made.
I mean that if I set up 1 instance it all works as expected. If I setup another Atom and set the PC offset accordingly with an offset of 8 (as per how my layout is set up) the second instance when it is triggered to change patterns will also change patterns on the first Atom. This only happens when the transport in AUM is running.
Are both Atom instances receiving the PC's you intend for only instance 2?
Ah yes. atom is changing behavior when transport is running. It is wrapping. PC 0-7 is triggering the first, 8-15 is triggering the first and second, 16-23 the first and second. ( @tk32 is this expected? )
As a workaround I created some streambyter filters before each of the atom’s that only allow the desired messages.
Ah! Okay, I’m not losing it. Haha. Thanks for taking the time to play around with this. I can always change this TouchOSC layout to CC’s but was hoping to use PC’s to keep most my simple controller data on 1 channel.
Thanks @Shiloh @xor and @espiegel123 ,
You guys are trailblazing here, and this setup is not something that was extensively tested during the beta.
I shall have to leave it to Blueveek to explain precisely what is going on under the hood with PC messages, as this is beyond my area of knowledge. It may well be a bug.
However, would it not be easier to simply put each Atom instance on its own MIDI track in AUM? Forgive me if there is a compelling reason not to do this, but I couldn't see one based on your original description.