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
3 for Kicks/lowtoms, mid/hitoms, hats/cymbals I guess.
I regard the Ui as a bonus tbh. I just hit the randomizer until it sounds cool, maybe tweak it a little bit. I would have liked even more detailed randomization, but can't complain for the price.
The scope got disabled for this version to avoid crashes is what I've read somewhere in this forum.
Is it possible to save midi out templates to sequence Bram’s drum machines for example?
[Edit: the developer just replied on Discord that they will add a midi note out lock in the next update]
Does this mean I won't have to set MIDI out again for each node when I switch between presets? That would be great.
Thanks @wim. You have been very helpful.
Been having a blast with Axon 3, I set up an AUM project with 2 instances of Axon that I can „beat juggle“ between
Each instance uses 4 outputs, Main for kick, bass, low elements, bus 1 for snare and mid percussion, bus 2 for hats and high percussion and bus 3 for synth/melodic elements.
Each of the 8 busses has a few Turnados, Transits and other FX, then I mix and match elements between each of the Axon instances to create evolving beats on the fly and twiddle FX knobs to keep things interesting
The onboard synth sounds fantastic and the rhythms the sequencer makes are lovely and unique. Like someone above said, it‘s a welcome break from the euclidean stuff which can get a bit samey over time
Can you set up different patterns in some type of song mode or scene change?
Okay, this comment was basically my manual. Didn't need anything else to make sense of the app. Thanks for this super useful list.
As for the app itself, I've found it fun, but in half an hour I've spent with it so far neither me nor the randomizer could come up with anything I'd like to use in my tracks. I guess glitchy drums aren't my cup of tea. Still a great playground though. Just make sure it's something you're really looking for.
Nice pice, got it ,but the oscilloscope and midi out doesnt seem to work ?
Would be great if there was a way to save synth patches independently of the overall pattern, they're relatively quick to create but minor knob variations can vary the output so much that it's fiddly to get it "just right" when recreating patches
This isn’t ideal i know, but for those who are finding the UI scale a bit of a strain on the eyes, don’t forget about the iPad’s built in Zoom mode. Enable it in the Settings and then it’s just a three finger double tap to show/hide it.
I did make a screenshot but the effect of the zoom window doesn’t seem to show up in screenshots!
Is this really that different from Axon2 ? I never really found 2 super useful even tho i like the sounds it makes… you can’t switch the sequence or anything so it was kinda stuck on one loop and limited to i think 16 steps.
I really like the sounds but the ui is not really adapted to my eyesight and the size of my ipad 9, too bad it could have been great, in my opinion, it wouldn't take much to make it readable.
That's what I do and it works well enough.
What are you guys seeing that implies a 16-step limitation? It's not even a step sequencer! (Clearly I am misunderstanding something here.)
If all the probabilities are turned off, then I think the sequence should repeat itself eventually, although it might take a while for a complex patch to repeat. If probabilities are wiggled, then you'll get something continually evolving but based on that underlying pattern.
I found Axon 2 very interesting when it was released (a couple years ago?), but ultimately I found it too fiddly and I'd forget how to do anything if I hadn't used it in awhile. So, it languished unused.
Then I saw Axon 3 was in beta and joined. Mostly to see if it had improved enough to pay for it again. I set up both and played with them at the same time. I found Axon 3 somewhat easier, a little more intuitive, the randomization options welcome, it's synth sounded better to my ears, and the interface of Axon 3 is aesthetically more pleasing to my taste.
Could I make Axon 2 more or less perform basically the same as Axon 3? I could get very close, but I find Axon 3 more of a joy to use than Axon 2 and with the randomization features added, and it being easier to remember how it works if I don't use it for awhile... it's worth the $4 to me. I'm just calling it a reasonable upgrade fee for an interesting app that I liked when it came out, and like even more now.
Is it still kinda fiddly and sometimes frustrating to use? Yes... but for me, much less so now.
Really digging this. Lots more play time to come to get deeper with it. One question - can the midi out be routed in Logic for iPad to trigger other samples etc?
Not really.
Route the central node to node 2, set its threshold to 1. It will play every second step, basically creating a 2 step sequence.
Now route the central node to node 3, set its threshold to 2. It will play every third step, combined with the previous node it gives you a 6 step sequence.
Route central to 4, threshold to 4. It will play every 5th step, and you have a 30 step sequence now.
Next node, threshold 6. Your sequence is 210 steps long!
Add node six (threshold 10), and you've got a 2310 steps sequence. Node seven (threshold 12), and you're at 30030 steps. And you haven't even introduced probability yet.
. Haven't read that right...
It couldn’t hurt to give each sequence node a visual number in the sequencer itself as well as on the synth and the mixer part. I do find it often confusing which sound is what.
Is there a way to quickly switch Axon 3 to send MIDI instead of using the internal synth ? I can change the trigger mode of the individual neurons, but that’s pretty cumbersome if I have to repeat this for all neurons and every newly loaded preset.
Very useful, thanks!👍🏻
It's (relatively) simple. Each node counts the pulses it receives. If a node receives from more than one transmitting node, the number of pulses received is the sum of the pulses it is receiving. When the number of pulses received hits the threshold, the node fires.
It isn't helpful to think if this in terms of "sequences" unless you're intentionally trying to build predictable patterns. There are too many variables. Yes, you could work out mathematically how long a sequence will run before repeating, but there's little point. It's more useful to think of the relationship between nodes.
Let's say I get a steady four on the floor kick going, and add a steady snare that hits on the two and four. The center node transmits 16th note pulses to the kick. The kick threshold is four - basically every quarter note. I route the kick to node 2 (snare) with a threshold of 2. The kick transmits a pulse each time it fires. The snare fires every other kick.
I could make that a little more interesting by setting the threshold on the snare to three, or five, but it would still be repetitive. You could work out how repetitive with a little math, but there's little point to doing so IMO.
So let's think about what happens if you add the center node pulses to the snare. First, the pulses are coming a lot more rapidly, so the snare starts to fire more often. Whereas the kick is receiving four pulses per quarter, the snare will now be receiving five pulses per quarter (four from node 1 plus one from node 2). It still wouldn't be hard to calculate how long before it repeats.
The easiest next step would be to experiment with the threshold on the snare to reduce how often it hits. Now the math is getting more complicated.
The way to go with this thing is to throw the mathematical logic out the window and just start thinking about how nodes can influence each other in general ways. When you add a transmitter to a node, the receiver node fires more rapidly. When you increase threshold a node fires less rapidly. The math of working out how "long" a sequence is gets complicated real fast. It's just not worth thinking about.
What I do find useful is to have at least one node that is fairly predictable as an anchor, then to surround the predictable with less predictable. So it's useful to me to understand how to make those more steady beats. After that it's just creative experimentation with other nodes and sounds.
Oh, and the random buttons. I've probably gotten at least as much useful stuff from those as on my own. 😂
Just to clarify - it's not so much the "order" of nodes as the "sum" of the pulses. Routing is only ever from one node to another. But yeh, it would save a whole lot of tapping around and inadvertently adding and deleting connections if there was some kind of directional indicator.
That's an excellent idea. I'd love to see that or at least patterns like the Cem Olcay apps.
But honestly I don't expect they'll make changes like that. This is Axon 3 and it's still basically the same app concept. They've added features, but not significantly made it easier to understand or control. I don't think that's their aim. In a way that's good in that it helps force one out of traditional mindsets.
Sending the output through Fill Bud is one way to go. I was also thinking that making occasional parameter tweaks through cc automation from something like step bud would be useful. So far I've just been messing about with the app. I haven't actually tried to put it to any good use.
The Axon 3 (desktop) manual has a good blurb right near the beginning on the differences. The manual has a few walk-throughs that helped me a lot.
good ol' @gusgranite made a feature request for that and they said they'd do it in one of the next couple of releases. 😎
Just checking ... You mentioned reading the Axon 2 manual. Did you see that I linked the Axon 3 manual? There's a section in that one that specifically discusses the differences.
Another way to come at this is to realise that, mathematically, the firing pattern of the node network is 100% "deterministic" i.e. completely predictable, given the routing and the thresholds for each node. There is no randomness in how the node network operates. Each preset will produce an identical firing pattern each time it is run because the network operates on fixed rules.
Deterministic processes can still be complex and produce surprising results for the listener, but the surprise is only in the ear of the listener, but if we had the time and patience, we could predict the firing pattern of any network setup with 100% accuracy.
On the other hand, there is randomness in how likely a node is to produce a sound once triggered, via the Likelihood settings under "Trigger" and "Ratchet", but this completely independent of the firing pattern of the nodes.
Thanks @yellow_eyez for the "fill" idea!
I just started using multiple Axons for that (thanks to AUv3!) and I'm blown away by how great they add up in an ensemble 😃🥂
Bloody hell @wim, I’d amazingly managed to avoid buying this but now I’ve given in. The one time I resisted an app.
As I recall, I had plenty favorable opinions of this app… and gave you details that led to your purchase. So no… you aren’t the only one, but “enthralled” might be a stretch
Not sure that's right ... although the central node fires out 16 pulses per cycle, we're not constrained to make any other node conform to a 4 or 16 beat cycle. They can fire every 3 beats for example. It's all about the thresholds for each node. These can be multiples of 3 quite easily. Or 5 etc ...