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
If this means ‘no luck’ for those not on iCloud, would you please consider ‘disabled’ by default?
Tho it seems I’m alone with this, so please ignore
Speaking of loops the other day I was trying to build some phase looping (with two instances of Atom) but the tempo/speed multiplier doesn’t allow for subtle changes (x1, x1,1...) is apparently to big a lap.
I’m not asking for yet another feature request but has anybody tried this/ has any tips?
To specify: two loops at slightly different tempos will eventually sync out creating beautiful rhythm variations. With the speed settings actually present the effect is out of rhythm, ie not nice.
Yes. I usually jam, export to desktop, and 'snatch' the best takes in Maschine. usually with Xequence.
Can you record/export multi-channels in one instance?
Thanks..
Agreed.
I just did a test and I was able to fire up AUM, add a midi track, add an atom2 instance, and make it 36 bars long, all in less than 10 seconds. I’m not sure I need a ‘never ending’ piano roll really, it’s just a nice thought to be able to press record and not think about it.
You nailed it; astute per usual. There’s a great Ted talk about how productive groups use task/project conflict vs people conflict to their benefit.
The tempo multiplier goes in 0.01 increments. Tap the left/right arrows for small increments, or use a parameter to modify it externally for even finer control.
So you want animations for the OS, but not for certain particular apps, and you also have iCloud Drive turned off? Can we add dark mode for some apps but not others in the mix?
Honestly, I personally think that's reasonable, but can't help but be slightly amused how incredibly particular some of you can be with all possible permutations of how you want your iPads to behave, in ways which Apple would probably never allow if it was just up to them.
I often wonder about this almost pavlovian response to "multiple instances". I sometimes think that what we actually need is better hosts that have better clip organization for the clip launchers among you, or, alternatively, that treat individual MIDI AUs just as they would a single MIDI clip which can be linearly arranged on a track for the linear-minded producers among you.
The problem here is at which level you solve the "song mode" problem – and I think it should be at the host level, or at least a level higher than individual AUs. Otherwise, what's the point of using AUM or Drambo compared to the other linear DAWs? (honest question).
I'm sorry but I truly do not understand or agree with the tension you are presenting here in relation to this feature request. A "keep recording until stop" is not inherently a feature for linear minded folks. I personally am using Atom as a clip launcher as you are intending (with shorter clips), to make electronic music, but I still think this feature would be a more efficient workflow.
And especially I do not understand why this feature to you is the difference between Ableton Session and Arrangement views. The default behavior of Session view in Ableton is in fact "record until i press stop". And there are further options for the recording to stop, after pressing stop button, in sync with a certain number of bars or to stop immediately.
I really like the idea about Capture Midi / bookmarks using an infinite buffer behind the scenes so that the user can either capture the last X num bars, or capture all since the last bookmark/beginning, and auto advance to the next pattern. It honestly would be an extraordinary feature, that seems like it would keep focus on supporting the workflow you want to optimize for, while also supporting this record until stop feature (tho i still say that this feature is not in opposition to your focus on atom clip launching).
Yeah, it's what I'm gravitating towards. And would be the most elegant way of implementing this with minimal changes to Atom. I'll experiment some more though, maybe the auto-growing number of bars thing will start... growing on me
A simple way of implementing a non-limited recording would be to
Internally set an arbitrarily large number of measures (lets say 1000) and when the user presses stop recalculate the length based on what was recorded.
You could use a length of 0 to indicate unlimited length (maybe displaying an infinity sign).
It isn't just rock and metal people that sketch and improvise in not pre-known blocks. Jazz , classical, new age, genreless music.
I didn't realize Atom was intended to be focused only on clip launch-based composition.
It is surprising to me to be hearing people describing non-clip based recording as somehow being stuck in doing things old ways.
Clip-based sequencing is not new and has been available as long as there have been personal computers and sequencers.
It isn't some failure to take advantage of modernity that has many composers and instrumentalists sitting down to capture ideas (and sometimes performances) without knowing how long the recording will be ahead of time.
I’m just waiting to see the next phase of atom/drambo. 😎
Thanks for your thoughts; from a user's perspective, I agree this would be one of the most straightforward ways of surfacing this feature. And that's the best perspective to start from.
I should perhaps note that what I wrote was "Atom is most optimized for", not "focused only on" which is what you wrote. Supporting both workflows is an interesting exercise, and this thread continues to be a source of experiences and workflows to learn from.
Does Atom try to do one of those the best it can? Evidently yes. Does that mean it does either of those jobs perfectly? Evidently not. We've clearly identified a point of friction for some, and the good news is that it's not impossible to iron it out. So I'm happy that there's a discussion going that informs and steers things forward.
If these "people" include me, then I'm happy to rephrase my wording.
I wrote "it seems that more traditional linear workflows are better suited for older genres". That's not an absolute statement, or a qualitative statement about what's better, or a judgement statement about "old vs. new". It is an observation (albeit empirical) that most rock/metal (and as you've included: jazz, classical etc.) producers use linear DAWs. If that's not the case, and the majority of these professional producers are primarily using Ableton Sessions for this stuff, then I'd probably have a lot to learn from them.
If these "people" didn't include me, then I'm happy to have rephrased my wording in case it's misinterpreted
@blueveek : I am glad to hear you being open to bridging the gap. I think only minor changes are needed to accommodate longer form recording.
I don’t think the old vs new genres distinction is meaningful — as clips only want possible till the advent of sampling .. and has been with us since then.
Perhaps it wasn’t intended, but the language you are using seems to imply that non-clips workflows are for old people or people making music in decreasingly relevant genres. But that’s not true.
A lot of comtemporary electronic musicians don’t work strictly in clips (or in clips at all). The strictly clips workflow has become popular and is a lovely addition to linear approaches. But I think it is a mistake to make a qualitative distinction based on the modernity of style or anything.
clips-only workflows are certainly more common than in olden times for the simple reason that they didn’t exist but that doesn’t make the other workflows less relevant. I suspect that if one were to look at professional musicians few of them are clips only.
And as others have noted, the best clips-based workflows have generally had options for capturing ideas without knowing the limits in advance.
I hear you. The most common use case is probably snapping to bars.
My background is composing weird metal stuff, so I like to do unorthodox polyrhythms, in which which case snapping the loop brace to sub-bar divisions is a nice trick. But that should't be at the sacrifice of what I now think is the most common use-case.
Definitely agreed. I think @tk32 was also suggesting that the snap button should be a first-class citizen. Persisting the grid toolbar would be a sufficient step towards that I'd say.
this -^
as i've been saying, the advantages of capturing ideas without knowing the bar limits in advance applies equally to both linear and clip-based workflows. I'm enjoying the discussion on comparing the two workflows within atom though.
Sorry, I didn’t mean to sound unreasonable...
Personally, never cared about animations... even surprised to have preference now... but generally when making music, I’m trying to remove all the distractions, so my preference would be ’off’
Regarding iCloud, I understand the convenience side of it but am also surprised that it became acceptable or even desired minimum requirement for a music app
Not at all, I hope it was obvious from my reply that I do think it's reasonable, and that it's a permutation of preferences that I didn't anticipate.
The trouble here is allowing sharing of Atom 'extensions' (configs, styles, scripts), which can then also be imported as normal files, while also giving easy access to those files. There's a limitation in AUs with Apple where an audio unit can't know where the 'On my iPad' folder beforehand, or at least I couldn't find a future-proof workaround for this, otherwise I would have picked that instead. So if I want to offer access to these files in a reasonable manner (and remember, this includes scripting), I need to use the iCloud Drive folder.
A very good case could be made (and I'm making it right now) to make this stuff work even without iCloud Drive access. How many people care about importing or editing configurations, styles and scripts in a way that makes them easily accessible? From a technical standpoint, making this stuff work for people who don't care about that is possible. Perhaps the hard requirement is a bit too draconic and some settings should just be a part of the normal app settings (e.g. in the iOS settings view, or within the app itself).
It's interesting. I've come around to no longer caring about a feature where you don't need to set the number of bars before recording.
The way around it is so utterly simple that its not worthy of an app modification IMO. One can just set a practical number of bars and save/recall that as a preset. Sometimes we get so obsessed about things of such small significance. I'm pretty sure the lifetime cumulative time wasted due to this feature not being there is an order of magnitude less than the time anyone has taken posting or reading about it.
Y'all can carry on noodling over this one. I'll just go 'n have some fun making music.
✌🏼
You can do this in a few steps:
1. Long press loop brace to select all notes within it.
2. Clipboard > Copy Selected
3. Patterns > Add empty
4. Clipboard > Paste at start
5. Export
The upcoming 2.0.6 update will let you skip almost all of those steps:
1. Process > Crop to loop (or crop to notes, or crop to selection)
2. Export
But perhaps an "export" button for each snippet in the clipboard menu would also be nice?
I don’t think there will be a wave of ‘offline only, Atom hackers’
I’ll definitely check out the workflow of drag&dropping locally stored patchstorage content.
👍
What could be cool imo, instead of having long recordings, and instead of looping into current pattern, create a new one, and record in that new pattern. Could work as is with a script, not sure this could work, something like
onUpdate
if isRecording && isStopped{
duplicateActivePattern
clearActivePattern
keep recording
}
not obvious but I may give it a try.
And maybe a function or a CC to change pattern .. on playback
I'm frustrated. Searched through the manual and can't find how to edit velocity of individual notes in Atom 2. Please help somebody. Where is it hidden?
how’s the cc automation coming along?
At the bottom right tap on Process -> Velocity -> Velocity Offset.
This is my biggest priority too. Love the app but won't be able to use in any actual projects until it has the automation lane like Atom 1 did🙂
Bump! The same here
..
One little script question, I guess it's not possible to store some variables with current host project (song) ?
ok 2, are there any global variables, that another script could read/write ?
I was playing around with a matrix of Atom 2’s in AUM and started thinking about sequencing them with a master sequence. Then I thought that I’d like to include some Drum Computer pattern changes too. Then I realized that I’d quickly run into unintended midi messages going the wrong au’s if I tried to sequence it all from the same master atom.
Do I need one atom to sequence other atoms and then a second for dc and then a third for aum (just thinking ahead for when atom gets automation support)? Basically an entire lane for master timeline-level sequencers?
Each Atom can only output one selection of MIDI channels (a single channel, or multiple channels all sending the same notes). So, if what you want to control needs separate midi channels, then you will need separate Atom instances.
It really depends on how you design it. You can use a single instance if, for instance MIDI Note 0-23 controls atom, 24-35 control Drum Computer, and 36-59 control AUM. But not otherwise.
And if there are no unintended consequences of sending 0-23 to dc and aum. It’s what I figured once I thought about it. I’ve been cool with multiple instances for each clip/section section but had just assumed there would be just one master timeline instance to rule them all but, ok. At least layers can help.
Thank you, Polyphonix, for answering. I was sure "Process > Velocity" is some macro for batch processing and there should be a quicker way to edit individual notes on the spot. Are you sure this is the only way to edit note velocity? Maybe there are some gestures or something?