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
That would be an excellent addition. I was thinking earlier after I posted this that it would only be guaranteed to work for non-MPE data as I'm guessing MPE generators want to be able to use all the channels for recording. I suppose you could still use PC for switching in that case (I don't think MPE uses that?).
Yes, PC is unused with MPE afaik as well. Clip launching and pattern switching with PC already works perfectly fine with MPE, so channel filtering for recording vs. triggering for notes and CCs would only be useful in environments where PC events are unavailable.
Here is the screen capture with Drambo + KB-1 + Atom2:
@clowm I've just tested again, and it works perfectly fine in AUM. If you can confirm that, then congratulations, you've found a bug in Drambo
Yep, in AUM it seems to work. Will report to beepstreet forum. Thanks
Thank you!
Probably already been mentioned, but it would be so cool for randomising stuff to have propability per note, and every time it hits the note, killer feature in many sequencers
+1...
or even more magical, conditional triggers (skip, jump, reset, etc. etc..), that would be something...😎
I am anticipating a feature like that eventually, care to share your thoughts @blueveek?
For probability and other 'randomization stuff' may I suggest Cality?
https://apps.apple.com/app/id1448694455
The beauty of modular apps is that you don't need one plugin to do 'everything'.
As @Samu suggests, feeding the output of Atom into Cality can work wonders. Hell, why not pipe the output of this MIDI chain back into another recording Atom.
When I'm noodling with Atom, I often feed chords from my Atom clips into other MIDI plugins or Mozaic scripts, and then capture the output into an empty Atom if I want to make things more permanent.
Hey @Samu sorry for the late reply. What you did in the video is pretty impressive.
Unfortunately Cubasis only goes upto 240BPM so no way to reproduce that.
have you been able to do something similar in Cubasis ? Mind sharing the results?
>
Nope, not using Atom 2 in Cubasis 3.3 since Cubasis doesn't seem to provide a stable pulse / clock signal to AUv3 plug-ins.
(Ie. timing in AUM with Atom 2 is rock solid while the same can not be said when hosting it in Cubasis).
Don't want to bash Cubasis but the team could honestly 'learn' a thing or two regarding iOS Midi implementation from Bram, Jonathan, Jim & Victor. (There's a few other 'sequencers' that suffer from poor timing as well but I won't mention them all).
I've got enough OCD issues with audio editing in Cubasis that ignores the audio event start & end markers when opening the audio/sample editor and adding this to the list would just make my brain explode with a WTF after WTF and yet another WTF.
For now If I need stable midi-sequencing I'll just use Atom 2 with AUM as the host...
Cheers!
Per note Probability is a different ballgame...
BTW.. IAP option for this... 😎
I see the randomize & probability as 'performance features' and it makes 'rendering/recording' a nightmare since you can never be 100% sure regarding what you'll get in the end...
When probability comes I'd love to see probability per 'step/grid division' (like on step-sequencers) affecting all notes on that 'step' with conditional jumps and things like that.
I'm well aware of per note probability, been using Renoise and SunVox for ages (Both have effects commands for it).
Cheers!
Really brilliant app and updates. AUM is closer than ever to being it's own daw. However, recording a whole song with two tracks (about 100 measures at once) my ipad pro 2018 started to get really hot and would sometimes crash all the auv3 plugins after a dsp spike. Rendering the notes to the piano roll suddenly become really delayed and take some time to render. Are all the processing cores available for audio?
That’s good for pure random chaos but many times you want finer-grained control of per event probability. Say, 100% for most of a phrase with one or two optional notes at 15%.
The things I’d love to see are
Cality is wonderful for randomisation. Don’t get me wrong, I luv atom, has owned both from day one.
Probability per note, that it will trig or not, would open up so much, to get controlled variation with shorter sequences on certain notes, cality does not give that control. One example is when sequencing drums, making a short sequence feel more live with extra hits playing seldom, or berlin like sequences. For me it doesn’t need to be complex, just on off. Like probability is now, but per note, and not stuck the same all the time.
Simple is beautiful:)
so i can’t remember, is cc editing coming to a future update? I don’t really know what to do with black box recording off cc’s. i’d rather be able to draw automation lines in. just curious
Well put, completely agree with this. To have a simple triad chord progression with 7th and ninth notes being added randomly/occasionally thru individual note probability would be amazing.
cc editing will be in a later update. this has been the plan all along.
perfect! thanks
HELP! I'm having trouble figuring something out regarding live performance. I want to start recording a clip partway through a song, during the second verse. I have a clip set up to 42 bars length, and I have Record mapped to a hardware controller (its an Arturia beatstep, not a launchpad).
My clip starts recording at some point through that clip's timeline, as the playhead seems to be advancing as soon as I hit Play in AUM. If I hit the Launch button the clip will start from the beginning, but not if I hit Record. I tried to map Launch and Record to the same pad but that was unsuccessful.
Do I have to map a separate Launch and Record command to different pads to do this, and hit them in quick succession?, or am I doing something wrong for this workflow?
thanks in advance.
I'd throw Alexander (Seven Systems) in there too!
@SimonSomeone
Based on my understanding of your needs...
Alternatively (and perhaps better)...
In both solutions, you probably don't need to configure your clip to be 42 bars long (which i presume is only that long because you are including the lead-in section to help keep the clip in sync with the track)
If all of your other auv3 plugins crashed but Atom didn't (which is what I'm understanding from your description, but correct me if I'm wrong), then it might be memory pressure that's causing the other plugins to fail. If Atom doesn't crash, it means that Atom isn't affected by the memory pressure in that case (and if it was, it should've crashed as well, along with everything else). My current benchmarks place memory usage at ~90-100mb per 512 instances, so I think there's plenty of headroom. Without any other information, it's hard for me to truly know what happened, so DM me an example project and I could have a look.
PS: AUM is already it's own "daw", it's just non-linear and nodal, which is slightly more exotic than what most people are mostly used to (without claiming that it's better or worse).
Yes, per-note probability editing would be a wonderful thing. Right now you're stuck with coarse-grained persistent per-note probability (the top-level "prob" slider), which isn't perfect for all situations. However, at the moment, I can't justify prioritizing this for the near future for a number of reasons. First, is that there's many other AUs out there that can get you remarkably close to what you want to achieve, and I don't want Atom to become a monolith that monopolizes all things MIDI – it's hard for me to maintain, and doesn't fit the modular ethos. Second, building a pleasant UI/UX around this (and automation editing in general) is no easy task, so it needs further careful planning and experimentation.
There's a few rules to keep in mind:
1. Arming record will also launch clips if they weren't already.
2. Un-launching will also disarm.
3. When arming a completely empty clip with no notes, 'gate mode launch' will override – I've found this leads to fewer out-of-quantum playing clips, a situation which often confuses beginners.
If I understand correctly, what you want is for arming not to 'gate mode launch', but instead launch from the beginning. I suggest just launching and then arming in that case. You don't need to be to fast or precise about it, anytime during the previous quantum (which defaults to 4 whole beats) is fine. If you want to make this longer, long press the Launch settings and change the "trigger beat" value.
I just love the LPPro3, tapping the dedicated REC button to enable/disable record in Atom 2 is really, really nice
Actually I think it's 38 bars, but that is the actual 'verse' pattern length. So what I was doing is ... first verse - play guitar, record it into Group the Loop. Then in the 3 last beats (3/4 song) of the pattern length I have to set Atom to record, then stop the guitar loop with a footswitch, and record my entire 38 bar keyboard part over the guitar loop. So it's not playing from the beginning. Then later in the song I;d play some other part over those 2.
So I think maybe your suggestions don't work for this? Actually maybe your first one does...
As in the reply above, it's a 3/4 song and I have to stop my guitar recording, then press launch and record and jump into the keyboard part. The clip is the full length of the song pattern. so it's 4 seconds or so I guess. A bit tight when I'm meant to be singing too, theoretically.
So I guess the upshot is I need to map launch and record to 2 pads. Which if they are adjacent is not too arduous. Or I could attempt a Mozaic script (which practically speaking means ask some kind clever person) which would send one immediate and one slightly delayed midi CC, and map that to one hardware controller.
Is there any advantage to using notes to achieve my goal? Instead of CCs? I see most of the advanced launch controls use notes.
...Or I could just keep it simple and record the audio into GTL instead of looping the midi.
Is there a way to get Atom to record open-ended? By which I mean, start recording and continue until stopped manually.
Even if I turn off looping, it only records to a set number of bars, unless I’m missing something obvious, which wouldn’t be the first time. The manual doesn’t mention this as an option, but mentions recording performances. Having to predetermine the length of an improvisation isn’t very helpful, especially as you can’t directly set a large number of bars because the + and - buttons don’t repeat when held down.
Use case here is recording an improvisation as MIDI so corrections can be made before committing to audio later.
The quick short answer is no, for now you need to specify the total number of bars.
But the workaround is very simple if you must have open-ended recording (see my addendum below for my personal thoughts on this). Here's a zip with 3 empty clip templates, one with 100 bars, one with 150 bars, and one with 200 bars. You can open them in every new instance via drag-and-drop from the Files app, or via "Open Clip" from the top-right menu. So if you want to create a track or open-ended improvisation canvas of 100 bars, it's quick: create a new instance, and drag and drop the "100bars.aprf" file over it.
A few tips:
Addendum: Generally, I'm not a fan of open-ended recording (this means I would never use it myself, not that it's a bad or inferior workflow). I would never be able to find that one good take in the haystack of lengthy noodling, and I'm honestly not sure how anyone manages to. What I do is just practice for a while until I figure something out, and then record it. Now, I agree it would be nice to save the most recent improvisation instead of playing it again to record it, but that's a different feature: it's called "Capture MIDI", or "record in the background and recall later", which is planned. Another approach would be to capture your takes in multiple patterns using the pattern-creating parameters.