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
.
Playing around with it … for a bar length that is not a multiple of 4 e.g. 3 beats, make sure that SEQ RESET is set to NEVER or ON PLAY otherwise the sequence will have a shorter bar every so often. Mathematically:
If B = bar length (no of beats per bar eg.. 3)
Then if 16 mod B is not = 0, then the sequence will be floor(16/B) bars of B beats followed by 1 bar of 16 mod B beats. Since the central node (which is the source of all triggering) works on a 16 pulse cycle, if bar length is 3, the sequence will be 5 bars of 3 beats followed by 1 bar of 1 beat.
But if SEQ RESET is set to NEVER/ON PLAY, this problem will not occur.
Also, a bit confusingly, to be triggered every 3 pulses, a node’s THRESHOLD has to be set to 2 (i.e. to play every n pulses, THRESHOLD has to be n-1)
Try the attached preset for a simple 3 beats per bar demo.
Surprised more people are not complaining about how difficult it is to dial in accurate values on these knobs. For melodic hits it is very important that the pitch is right, but I sometimes find myself having to endlessly fiddle to get things in tune. This is an absolute joy killer, imo. I never understand how devs let apps out the gate with problems like this. It either needs a complete rework—at least on important knobs like Freq—of how the knobs can be fine tuned quickly and accurately, or it needs a way to enter an exact frequency value via numerical input. Preferably the former. Price is great, concept is cool, but ability to dial things in quickly and accurately are essential, and when apps lack them it contributes to the wider perception that iOS is not a serious music-makers’ platform. I do know of course that the keyboard icon quantises to note, but the fact remains that it does have fine tune options, and that fast fine tuning by ear should be possible.
I've only been using it for drum / percussion sounds. I haven't tried anything with melodic content. I suspect there are others like me that aren't struggling with the frequency knobs for this reason.
For sure
Worth pointing out though that for drum sounds pitch is also important, for higher sounds in particular which don't have much noise masking the tones
Thanks ; I am going to try to figure this out with your tips. I thought at one point I had a 6/8 rhythm going on but I’ll explore and try more - nothing else like this sequencer I ever saw
And Gavin I use it simply as a drum machine. That’s what it is really. They included melodic stuff but it’s not really for it in my opinion. Drums in the other hand made it a very satisfying purchase (thx to skip hunt)
Great sound designer.
Yes yes, but even drums need to be tuned! The fine tuning knobs should work better than they do. Those who don't need or want to use them are fine, but it's still important to point out flaws in apps. Devs benefit from this too, in the long run, even if they don't like hearing it. Constructive criticism is important. Hence I raise the issue here.
Absolutely. Your right
One way might be to connect a node N1 to the central node. Set N1 to Threshold 5. Maybe connect a second node N2 to central node with Threshold 6 and OFFSET 3 so it plays on the backbeat. Set SEQ RESET to ON PLAY or NEVER.
The Central node could provide the hihat or other line that plays every beat, but it couldn't offer something to fit the 6/8 time signature e.g. every 3 or 6 beats as it is fixed onto a 16 pulse loop which can't divide into 3 or 6 evenly.
May I ask, How do you have such great control over the sequencer ? And also do you take advantage of the awesome midi out features and combine them with other drums? Id you prefer to dm me so it doesn’t derail please lmk or just hmu! Thanks (please link me on how to use offset correctly tutorial )
FYI: I’m also reading these exchanges with interest, and I don’t think they are derailing. The thread is about Axon 3 being se, so totally relevant.
Thank you. I thought I was beating a dead horse , so it’s good to know that I’m not overdoing it.
The offset has me stumped (unless it’s because I’m waiting for it to restate the pattern sequence from the beginning whcih it would do according to what I’ve set with your recommendations ) and curate
I have not read the entire manual for this, so may be error on my part. But here is my setup: every neuron is set as ‘midi note to synth’ and trigger mode for every neuron is also set to ‘synth’.
The manual says: ‘ Use the SYNTH option if you want to use Axon as a tone generator, bypassing its internal sequencer altogether.’
But - here I am not sending any midi in (yet), and nevertheless Axon is still producing sound when the AUM transport is running. Shouldn’t it be ignoring its internal sequencer altogether and only responding to midi in? It is indeed responding to midi in, but the problem is that I can’t get it to stop listening to its own sequencer too.
If anyone can enlighten me, great!
Only 'work around' I've found if midi-only triggering is desired (ie. use external sequencer) is to disable host sync, stop the transport (in the plug-in) and set threshold to 0 and likelihood to 100 for all nodes.
This way the host can be running but Axon 3 will only produce output when it gets incoming midi-notes.
Thanks Samu - that seems very strange to have to do all that, no? Do you think it was designed like that? If so, why?! After all, the manual does clearly state, as mentioned, ‘ Use the SYNTH option if you want to use Axon as a tone generator, bypassing its internal sequencer altogether’ 🤷
“Likelihood” for the “trigger” should be zero, the same as the "threshold".
That makes more sense than likelihood set to 100, yes, and that does work. I don't think threshold value is important is it? As long as likelihood is set to 0 there will be no sound, surely. But it’s really bizarre how much work is involved in modifying a patch to get it to be just triggered externally. That feels like really bad UX to me. As does the design of the neural network - not being able to see at a glance whether a neuron is connected to the center neuron or the one opposite it. Having to go in and click on neurons in Route mode and see the colour of the arrows there to see which is a sender and which is a receiver seems convoluted.
Here is the patch for the Synth Init, if you want to use Axon3 only as a synth.
I agree with you, it was confusing for me too, but hey, it’s about AudioDamage.
Chris has been very responsive, at least to bug reports and questions about the app, on the Discord server. You might get eyes on your issues over there.
https://discord.gg/audiodamage
Thank you, that’s good to hear!
Quick heads up that my hour-long walkthrough on Axon 3 will be up on YT tomorrow (and is actually up on my Patreon already). Apart from a few gripes, I really love this drum machine!
That was always my beef with Axon 2--very difficult to tune due to the dial response.
Woke up this morning ready to watch only to find I had a few more hours to go!
Looking forward to this, and I’m so glad you did a tutorial for this
This app deserves it
Cheers Chris! The first one I made ended up being one and a half hours long lol. The 65 minute version was a later take. Tried to make it as short as possible. There's a lot to talk about with this app 😂 👍
Yeah, this is an issue, and is similar to what I experience when I try to use the Noises pitch knob to dial in precise semitones since there are no notches. @Gavinski has raised this issue of knob precision/behavior being a real obstacle in the past and I hope more devs think about it. In this case, I've been throwing a scale quantize in between the app and instrument to just avoid dealing with the challenge.
Another example of challenging knob behavior that comes to mind for me is the Fmqt synth... It has some great ideas like the automation recording but it's so hard to dial in precise (or small) changes. On an FM synth, where tiny parameter changes can make huge sound differences, I precise knobs can really dampen the party.
As about tiny knobs:
Have you tried to reduce the AUv3 window height until the view changes to fewer controls and more pages?
That was the first thing I had to do.
On my 12.9 ipad the app sized small doesn't have bigger knobs than when it's opened full screen, unfortunately
Hmm, but Axon3 has its own built in scale quantizer. Maybe I'm misunderstanding. The issue I'm describing is related to when the quantizer is turned off and you're tuning the knobs freely by ear. I can't see how using a scale quantizer like Rozeta would help this? The problem is simply that the knobs are not capable of fast fine tuning. An example of an app that is good for that would be Combustor, where horizontal movements allow for very fine changes and vertical is for coarser changes.
.