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
Yes I've created too many audio sessions where I'd wished I'd video'd them - now I can record directly to my MacBook I can do more (although the latency in audio is still bit off putting!)
I'm going to create some basic template projects - just haven't had time yet.... bug fixing comes first.
Not to argue or belabor the point but you will get those "happy accidents" of modes by emphasizing any other note than the root of a major scale anyway so why clutter the interface with redundancy? If you're moving the faders around and picking notes by ear you are probably already creating modes by happy accident anyway you just won't know which mode it is. I'm
There is already a description field on the Files window, I type notes there all the time. I'm not sure how many characters it will allow.
ok never used that will give it a try thanks
I appreciate your persistence in getting me to see the rashness of my request.
Yeah no worries from me, I'm happy feeling my way around anyway.
Is there a way to randomise the order of steps played? so that the stepper jumps around the sequence randomly.
This would be a great action to add to the list at some point if not.
Here's something which is unexpected for me:
Started a linked sequence with 2 racks sequences. first one plays through then starts sequence two.
Sequence 2 has 2 parts with actions to start part B at 100% as first action.
But it always goes back to the sequence 1 instead of going to next part of sequence2
Is there a setting I've missed so that it follows through the sequences and actions?
Thanks
randomise order is the loop type random. You can set it manually or with actions.
I'm guessing the action is interfering with Link. Link does this on its own:
Song mode = Link
S1 (selected)
S2 A=4 steps B=4 steps
Press play & its plays S1, S2A then S2B & repeats - you don't need an action in S2A to start S2B.
With an action it goes a little weird, sometimes works sometimes doesn't. Seems to play A twice if you start on S2A selected. Will add it to my list to investigate.
ok gotcha, it's in the loop types, nice. One thing which could be useful is a setting for how many steps the RND loop plays for, unless I'm missing that feature.
Yes without the action makes sense now in playing the parts. I can see that it might be useful if the part that is currently playing might be lit up a certain colour. Or there's a setting that makes the interface "follow" the parts which are currently playing too. but I've probably missed this and it's in there somewhere.
Great work though this is going to get a lot of use from me
Do check out the Brownian random playing, which is nice in a semi-random fashion. I also like the effect of 3 Forward 2 Back (3F 2B, I think it is called). A feature request would be to ask for more variations of these (2F 1B, 4F 3B ..., and variations of Brownian that go from subtle to large in how many steps are hopped).
For the setting of how many steps the RND; yes, that could be implemented. Or you could think of Quantum as a step instrument that you live noodle on, so you manually do these changes while the sequence is playing (as is demonstrated in one of the videos). But yeah, if you want to to it to many sequences at the same time then good luck with that!
now your getting into design - good!
I have also a new panel in the works that will allow you to set loop types better - so you can use rotaries to dial in the FxBy part. Fwd is actually F1B0 & Rev F0B1 in the version you have so I can easily update & keep your original banks working.
But I really liked F3B2 (which is from midibus seq I think) but plenty more will be fun.
Live noodling on it is a great way to use it I agree. But the way I'm setting up my main usage right now is to create a sequence which goes all the way through different parts, but with variations each time. Then I would spend the time live tweaking the synths and mixing/effects etc
So being able to predetermine randomised steps length would be nice so I could leave it and record the results etc
...
So you want to randomise the sequence length rather than the step notes? Sounds interesting - especially with poly mode (which modifies other sequence timing too!). Adding that to my list - but might just be set end step with a random option.
@midiSequencer Would it be possible to have Quantum be able to import scala files?
There are some apps such as the Wilsonic and ScaleGen which can be used to create scala files and others such as Gestrument or ThumbJam which can import scala files to be used to send out a MIDI stream of data based upon those scales.
I would imagine the vertical range of notes in terms of values set in the slider would need to have a practical limit in terms of the number of tones you can have in a scale and still have Quantum be functional. Being able to have a way to sequence these scales in Quantum would be great.
Here's a screenshot of ThumJam with a scale having a lot of tones:
Well that sounds great too, so would be interested in that.
But What I mean for example
using song LINK mode I have 3 parts in a sequence: Parts A plays out in the steps set to then Part B is set on RND it will continuously loop forever and not go to part C ever. but it would be nice if I could set how long the RND part plays for and then goes on to part C
I tried adding an action to part B (the one with RND) wait 16 steps and then start part C but it still looped on RND and never goes to part C.
So not sure if there's away yet to do this.
I was going to suggest that you set up parts, with a random part surrounded by non-random parts. But you are already there. That part B loops forever sounds to me like a bug? With playing set to ">", I would have expected part A to play normally first, then part B playing randomly, but moving to part C after having played the same number of steps as B is defined as. If this is the intended behaviour, then you could set an action to let part B repeat x number of times before moving on.
Looks interesting - but will have to research it. The fact that some iOS apps already support it helps. I'll add it to my list item that indicates midi micro-tuning..
Might be a problem with actions - especially with Link mode (Link might be conflicting) - but in theory yes.
There is no probability with Link, so try using the %probability - as actions can have a probability of being ignored too.
But for this to work you need actions to either a) stop & start a new part or seq on a random% or b) an ability to refer to a previous actions %roll (e.g. start Part B %x chance followed by stop %y should have an ability to say don't roll % again for the stop but use the last % result).
I will add these as additions to the actions to see how they work out.
Let me work on fixing this - it's complicated more than simple B follows A because there is a lot of logic to do with sync (which also makes parts start & restart).
ok, I've fixed a bug with any lower part being asked to play after a higher one and it misses a step. It was noticeable more with multiple sequences.
This makes Link mode & Parts using > or < better. Patch will be submitted tomorrow hopefully for this (and a few other things too like ios9.3)
I'm not sure how Korg does it, but in some of their apps they have a button for "Advanced Settings" in-app that takes you right to the settings app. Just a thought.
I will add it, but this setting requires a restart of the app, but will see if I can get around that.
Yeah, it's just the wording. Maybe "Set C3 to MIDI note 48 (default is MIDI note 60)"?
Ok, i'll have more of a play with the options. Are you saying in theory though Link mode isn't really supposed to go hand in hand with actions? Actions are more supposed to be played out independently of the song modes?
Because I always had probability for the action set on 100% but this still didn't change the looping action for the RND sequence earlier.
Anyway having a lot of fun with it so far and I've only scratched the surface
Is there a way to do legato with different tempo divisions? Seems like if you select legato you're stuck with 1/1. I could easily be missing something though.
When you talk about actions and Link mode, do you mean Ableton Link, or linking parts using ">" playing, or linking sequences using master/slave syncing? /confused
I see the interactive help for RND says that this mode never triggers a cycle event, so the forever looping part is by design and not a bug.
Maybe the new panel with knobs for setting FxBy could include a RNDn mode which triggers a cycle event after n steps? n could be set by a knob, and a value of infinite would be the same as today´s RND mode (or you could make this into two separate play modes).
I was talking about song mode Link bottom left not Ableton Link. Yes I think it could do with a different name to avoid confusion. A RNDn option sounds ideal.
At the moment loop type Rnd does not trigger a loop therefore never triggers loop actions. Sounds like I need a version of Red that triggers a loop when it touches the start or end say.
Legato is more about using gate interval (the gate%) to determine tempo.
With your steps defined as 80% gate, switching from 1/1 to Legato speeds it up, this is because the 20% gap is now gone and the next step plays immediately.
With your steps defined as 100% gate - switching 1/1 & legato do the same thing.
So try playing with gate% in legato mode to see what I mean. It's very useful for monophonic synths (as no overlap in midi notes). It also means you have no staccato notes (which naturally occur with gate%<100%).
yes that would be better - I count steps in a loop sequence anyway (for accent)
This would probably be more useful than a loop being triggered when a start or end note is randomly selected (although that could be cool in some cases too; if you set that start or end to a pivot tone/chord that you then resolve to with your next part/sequence...).
However, if you're using step time values, this step count method could also be hard to predict timing-wise as you could be counting a bunch of short or long notes.
I would also suggest having a random loop triggered as some multiple of Ableton Link phase value, so the randomness would happen for some musically relevant period of time.