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
I like the new graphics. The visual link between the highlighted current step and the step detail window is much clearer now, making the <> buttons more intuitive when navigating in that detail window.
I think there is much potential for using Quantum to CC modulate many parameters. Thanks for the Model 15 map - video tutorial people should perhaps take the opportunity to demonstrate how to use this!
Anyway, making the CC even more useful, I would suggest the following:
Btw, the faders had some drawing lag when I tried to modify CC values. That seemed to be more pronounced for CC than for note, gate, length and such. Strange?
Is this Model 15 map available for download?
Am I the only one that prefers the old GUI? Buttons are way more obvious.
Very excited for the update! Now I just need some free time... can you add that into the app?
This would be fantastic. I adore Quantum, but I've been hit by timing anomalies when switching apps. It should be noted that this isn't with an old CPU on iOS 11, it's a 9.7" iPad Pro (A9X) with iOS 10.3.3.
One thing I've noticed: when switching to some other apps (e.g. Fugue Machine) when the iPad is under a bit of a load, those apps will prioritize the timing of the MIDI (or audio) and have a delay (sometimes significant) in updating their graphics. Perhaps this strategy could be employed with Quantum?
Anyway, thanks again for the continued development!
@midiSequencer I like the new skin much better. Haven't used Quantum in a good while and was completely lost again at first. Had to go back to the manual and skim a demo video again, but most of it came back to me fairly quickly.
You mention that Quantum has it's own automation built-in. Where is this in the interface? And, where is the section about Quantum's automation within it's manual?
Thanks for the update!
You mean something like...
1) Press some notes in a keyboard (like D# minor)
2) Quantum will arpeggiate that?
what do you want to learn? At its core you pick a scale, draw notes, press play & tweak.
To get under the hood though think of whats important about pressing a single key repeatedly on a piano & how you could add variation to the playing (e.g. ratchets = playing twice as fast say, step triggers are playing then skipping after a count, midi fx is modifying the note - echo=multiples, filter = quietening or blocking, cycle mode = save it all up then play it really quickly at the end).
So keep in mind everything is built around that step and you need to therefore interact/improvise with a playing sequence.
A good place to start is with a simple 4 note sequence - and build in variation - e.g. you can modify faders for velocity, note length(gate%), step length (time) and even a lot more variation with humanise (100% on one step then use pitch & velocity variations).
Like a sequence you have created? Save as a version so you can load it back during playback.
For me composition is normally three stage:
1) create pleasing sequences that work well (counterpoint say), save them as variations
2) pick sounds from your synth that work with sequenced note (not too much release or long a note - something percussive always works well)
3) run the sequences loading variations, mixing, altering on the fly to get variation.
I tend to also add a lot of delays - not just midi fx delay, but audio apps like Kosmonaut - these bring out surprising syncopations!
Another cool feature is midi driving an app with its own arp (model D say), that again can make complex sequencing with just a simple sequence.
Let me know if you need more help?
yeah will check that out - there is an option in Settings app to have instant fader movement, but I will check this out for those who want animated movement.
I don't tend to use CCs now - reason being that I setup the RT panel to map directly to learnt controls. With that in mind you can name your own controls and not have to switch over to an app thats heavy on your gpu (however nice it looks!)
I think the CCs need an overhaul really - I was working on drawable LFOs tempo sync'd to the song which would be better served especially as you could unlink it from a step with odd tempo divisions (or free running).
Yes I could allow naming like I do on RT controls - if nothing entered use cc1(cc57).
button press to pop-up list is indeed too slow(after all its Apple code!) - swiping would be good.
probably yes now
But at least you have the choice
I usually just use 23 = filter, 24=resonance etc and work around the app on things that I want to control. Model D for example is easier to setup this way as most control is on the rhs side.
This video (
) shows how I use this on Model D.
I can get rock solid midi if I use an Audio Unit to drive this, but its limited in the tempo.
Have you noticed how Fugue plays the midi at the end of the step - thats effectively a step delay? I'm guessing many other apps use midi timestamp delays to ease any jitter.
I've some more work to do on slower devices - when thats good our faster ones will be great!
Automation is via midi CCs (Learnable controls you map ccs to) and NRPN.
Think of NRPN as two midi CCs together - they give you more than the 127 controls. I have these mapped as follows:
Note: NRPNs are absolute values only - no Scaling or Relative (these only work on Learnt CCs)
0,1,c PlayControls where c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.
0,2,c Transpose x where x= c-64. So valid input range is 40..88 to represent -24..24 range in Quantum. Outside this range will be clamped
0,3,c,d Tempo x bpm where x = c+d*128 - so 14bit but clamped to range 1..240.
0,4,c Song mode c where c= 0=All,1=Link,2=Solo,3=Pick,4=Free,5=Poly. All other values ignore.
0,5,c,d Time Signature c/d where c=1..16 and d=2,4,8,16,32,64. All other values ignored(so both c & d must be valid).
0,6,c Song Volume c where c=0%..100%. All other values ignored
0,7,c Metronome where c is 0=off, 1+=on
0,8,c Link Fader control where c=off, 1+=on
0,9,c Midi Out where c is 0=off, 1+=on
0,10,c Cycle where c is 0=off, 1+=on
0,11,c Record In where c is 0=off, 1=chords, 2=steps
0,12,c Audition where c is 0=off, 1+=on
0,13,c Song Mute where c is 0=off, 1+=on
0,14 Song Solo (will act like solo button press)
0,15,c Shift sequence Left/Right c steps where c>0 for shift right, c<0 for shift left. Only c = -1,0 & 1 considered. Works best on Rel mode. Cycle mode will delay shift until next loop
0,16,c,d Main Screen faders - where c = fader 1..fader 16. d=value 0..127 (but may be altered - e.g. notes in a scale)
0,17,c Mixer Panel page 0=1..12, 1+=13..24 - only if currently visible
0,18,c,d Mixer Panel fader c=1..24 for consequetive sequence part, d=0..100 (for 0..100% volume) - only applied if valid seq part
So if Seq1 has 3 parts, Seq 2 has 2 values for c are (1=S1P1,2=S1P2,3=S1P3,4=S2P1,5=S2P2 all other values ignored)
0,19,c Tempo x bpm where x = c - so 7bit but clamped to range 1..127.
0,20,c Select Range c where c is 0(1..16),1=(17..32),2=(18..48),3=(49..64) - if valid (i.e. has to be a sequence of that length)
----- Sequence/Part parameters
x,y,c,d Sequence a Part b where x=a4+b (so 5=Seq1A,6=Seq1B..8=Seq1D,5=Seq2A, etc.. 28=Seq6D)
x,0 Seq/Part x Part Select (ABCD buttons of sequence a)
x,1,c Seq/Part x Tempo Division, where c=Tempo division (1=1/1 etc)
x,2,c Seq/Part x Start Step, where c=step 1..64 only. If >end step, will clamp to endStep.
x,3,c Seq/Part x End Step, where c=step 1..64 only. If seq length will clamp to that(e.g. 16)
x,4,c Seq/Part x loop type (0=FWD,1=F+1,2=F+2,3=F+3,4=F+4,5=F+5,6=F+6,7=F+7,8=REV,9=BNC,10=BN,11=RND,12=RND,12=BWN,13=F1,14=STP)
x,5,c Seq/Part x play/stop c is 0=stop, 1=play, 2=pause, 3=reset. All other values ignore.
x,6,c Seq/Part x transpose c where c= c-64. So valid input range is 40..88 to represent -24..24 range in Quantum. Outside this range will be clamped
x,7,c Seq/Part x volume c where c=0%..100%. All other values ignored
x,8,c Seq/Part x invert c where c=0 for OFF, 1+=ON
x,9,c,d Seq/Part x reflect + key c where c=0 for OFF, 1+ for ON. and the key d=0..127 for note c-2 to g8
x,10,c Seq/Part x override channel where c=0(use step), 1..16 (override to this value for all steps)
x,11,c Seq/Part x Timewarp navigator where c=0(OFF), 1+(ON)
x,12,c,d Seq/Part x Accent Beat where c=0(OFF),1+(ON) and d=value (if on)0..100
x,13,d,e Seq/Part x Time Signature d+e where d=1..16, e=2,4,8,16,32,64
x,14,c,d Seq/Part x Step Mute where step = c (1..64) where d=0 is off, 1=on
x,15,c,d Seq/Part x Step note where step = c (1..64) and d=note value (0..127)
x,16,c,d Seq/Part x Step vel where step = c (1..64) and d=velocity value (0..127)
x,17,c,d Seq/Part x Step gate% where step = c (1..64) and d=gate% value (0..127)
x,18,c,d Seq/Part x Step swing% where step = c (1..64) and d=swing% value (0..50)
x,19,c,d Seq/Part x Step probability% where step = c (1..64) and d=probability% value (0..100)
x,20,c,d Seq/Part x Step humanise% where step = c (1..64) and d=humanise% value (0..100)
x,21,c,d Seq/Part x Step humanise Note where step = c (1..64) and d=note value (0..127)
x,22,c,d Seq/Part x Step humanise velocity where step = c (1..64) and d=velocity value (0..127)
x,23,c,d Seq/Part x Step time division where step = c (1..64) and d=time division value (0..127)
Happy to explain all this, but you could for example program notes on an particular step or a sequencer part.
Best way to try these out is with MidiSequencer!
In Record mode you can play chords & have them arpeggiate into steps.
In Playback you can set NoteIn mode (in Options Master/Slave button) and have a single note play a single step.So press C it plays step1, press C again it plays step2 - steps of course can be chords.
Its not really designed as a midi arpeggiator (reads a midi in chord and loops those notes). I'm sure those apps exist already?
Can you programme different note lengths in this sequencer- like 1/16ths, 1/4, whole etc- or is pretty much one type with adjustable lenghths.
Also- is there any control on gate time?
Thanks
Yes and yes.
Under the sliders there are a bunch of buttons that let you change what the sliders are showing /modifiying. "Time" and the one with the % sign are the pages you're looking for.
All of this. Ignore 85% of the app to start with. Make a short four note sequence and explore all the things you can do with just those four steps by messing with the slider types (top right), sequence bar (just below the step indicators) and step options (tap a step). Save versions as you.
Then, get lost in the rest of the app.
@JohnnyGoodyear just remembered this mini tut: https://forum.audiob.us/discussion/21646/quantum-parts-as-fugue-machine-mini-tut
Parts might be a little much to grok if you're just getting into it but...
Ok thanks- I think I may be getting this one.
Thank you Professor. And thank you @midiSequencer also. A very generous response which I have saved and will revisit. Like the idea of the four notes.... Thanks again.
Not just more convenient. Not sure about anybody else, but my music making sessions tend to be short and are usually interrupted by real life. If the power management in IOS were good enough to be able to put a device in your pocket with bunch of music apps running, and then pull it out half an hour later without it having run the battery flat it might be a different story, but with the current situation having to spend five minutes initialising the setup means most sessions involving more than one app (and I'm not including AUV3s within other host apps here) end before any actual music gets made.
The time button is one of my favorite Quantum features. It basically allows you all of the timing flexibility normally associated with a piano roll. In a step sequencer. Madness.
I'm getting this problem which I've had variations of throughout my history with quantum. If I switch over to any of the pages from the Note page everything goes silent and my synth (right now external Digitone) doesn't produce sound until I reload the patch. It's really annoying. Weird bug? @midiSequencer
I will message you - it might be you have Learn Out enabled - this transmits midi cc for the faders when you switch pages - this is used for automation mixers like Yamaha mixers that can move faders.
I can't believe how long it took me before I put it in, but yes it relates to drawing longer horizontal notes on a piano roll.
You don't really need to explore parts early on- they are quite an advanced feature for complex sequences(eg you can reuse steps or have individual loop action lists per part). You can do the same with individual sequences
And with those 4 notes you can try this:
Extend to 8 steps, use Select button, copy the first four, paste to steps 5-8 then add variation(e.g. modify step 7 note).
that way you can build up longer sequences quicker using cells or group of notes.
You can copy/paste steps between sequences too.
Worth mentioning that the Model 15 map is included inside Quantum, no extra download necessary. I found it in the Setup page. There were a few other maps you could cycle through as well.