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
At least the IAA transport panel can be moved.
Next update (v1.7) submitted to beta testers - this one fixes two of my longest technical issues
Updated Internal clock that no longer glitches when you use the home button - this is an IOS 10 & 11 bug thats annoyed me for ages. Mostly an issue on older devices.
IAA transport panel to get you to AUM, BM3 etc host app.
Other fixes/enhancements include option to move the Audiobus mini control, etc
Tie notes ?
🤞🏻
I forgot to just say: that was probably the best reply I could have dreamt of. I seriously am so psyched! Definitely gonna be sequencing like never before. Cheers! I guess I am gonna want to think of polyphony now, I've only thought of it when playing live as in : how many fingers do i need to play at once. Thanks again.
Not yet..... but I need to understand what you want here..
I would consider this making a step tied to previous step?
This would require extending the previous step length & effectively muting the tied step?
Is this what you want? Let me know if you have a particular implementation in mind?
yes think counterpoint (like fugue say) but up to 24 parts, so start simple with just two similar sequences (just like bass guitar & rhythm guitar).
Humm ... What if you just delayed sending all note-off messages until the end of the last tied note? Or, maybe deferred sending the note-off for the previous note until the end ( or the middle?) of the note after it? Or ... yeah, I see what you mean. It could be done lotsa ways.
It seems to me that just delaying the note-off for the first note until sometime after the next note-on should be enough for a tie - at least in a purely music notation sense. Different synths and presets would interpret that differently, which is analogous to differences between the behavior of different instruments. Just my opinion though.
Or maybe I’m using the wrong term. Is a tie between two notes of the same pitch, effectively making them one? And a slur when notes of different pitches are played legato?
Rambling ... sorry.
So to be clear here:
Tie = two steps sounding as one(so one midi on, one midi off). So the first uses the time of the 2nd to extend its length. A tie is for notes of the same pitch. Its most used in music notation for notes not fitting into an exact beat (e.g. run over a beat or bar)
Slur = two steps like tied, but different pitches. So again one midi note on & off, but you'd need portamento cc or pitchbend to achieve this. The pitches are usually microtonal.
Glissando = like Slur but with scale notes in between - each with a distinct midi note on/off. This is like an arpeggio.
You also need to consider that unlike a normal music score, Quantum can leap (play reverse or jump into/out of overlapping note groups). So what should F3B2 do with a tie?
Any equivalence in other iOS apps?
Trying to understand what people expect before I code something
IMO for a slur you would still send the note-on for all notes, but defer the note-off for the first note until the end of the next note (or at least until some time after the note-on of the next note). It’s up to the target synth how that’s interpreted. For instance, Troublemaker would play that as a smooth slide. Another app might play it as two notes, but with the first overlapping the second. I don’t think the sending app should be trying to accomplish that via pitch bend. A trombone would play a slide between notes. A guitar can’t do the same but can try to sound as legato as possible. A piano can sustain the first note but still has to sound the second. A violin plays two distinct notes but all in the same bow stroke. A poly synth overlaps the notes. A mono synth might glide ... etc. IMO all the sequencer needs to do is overlap the notes in some way.
IMO reverse should be the same. Whatever note plays first has its note-off delayed.
Glissando ... to me that’s just like a bunch of slurred notes. No difference, just more notes.
yes slur should just be overlapped notes. But you can do this now - just make first note longer than 100% gate. Same for glissando....
which just leaves tied notes - so same pitch notes but just one note on/off to cover note 1 step length+step2 gate time. Notice I said step length & not gate length for first step.
I was just referring to a post you made..
I am in the back seat enjoying this ride.. whatever you bring to the table I’m pretty sure it will be great..
Can’t you get tied notes now by extending the gate on a step past 100% and muting the next step or two so the first note hangs on longer?
Maybe I’m missing something here.
I thought tied notes wasn’t just length of note, but glide up and down through the following tied notes like the old 303 (Rozeta Bassline style)?
I’m talking about tied notes in the music notation sense which does have to do with length. It sounds like what people are asking for is portamento which is a slide between notes where you don’t hear the attack of the second note.
Edit: and you don’t hear the notes in between which is glissando (as mentioned above).
@yowza right. I’m just assuming everyone wants to use Quantum to make acid bass lines like me
I have now exposed the extent of my music theory knowledge and will sheepishly slink away
What’s an acid bass line? I think I know but showing my own ignorance here.😉
so yes, we already have tied notes(steps with gate>100% and muted next step) & slurs(steps with gate>100% - where 100% is the legato mode). These are limited to 400% (4 steps) max.
I don't have portamento or pitchbend between steps - which would involve additional midi events between the steps.
I'm still looking to provide gated patterns (where you can define steps as early or late - similar to swing but those are only late - and this is a pattern - e.g. 4 step pattern would apply 4 times across a 16 step sequence.
I don’t actually have a dog in this hunt. I was just musing about the meaning of tie vs. slur and how one might implement that in terms of note-on / note-off messages. I would already just overlap notes using the gate time if I wanted to do either. Like I mentioned I don’t think it should be the sequencer’s job to interpret what happens when there’s a tie or slur. That should be the target app.
If people are looking for portamento slides using pitch bend when they say tied notes, then that’s a whole nother ball of wax.
The acid bassline thing is all about the synth. Overlap the notes in Quantum (see gate above) and set up your synth to react the way you want. Envelope retrig or not. Portamento speed. All that stuff is the synth, not the seq.
If you just want longer notes you have a couple of options.
For up to 4x the default clock, you can just use gate as described above and mute the next 1-3 steps. If you set it to 200%, mute the next step. 300%, mute the next two steps...
The other option is to tap the super magic TIME button under the sliders. With this view you can set any step to be any length you want. So if you want to "tie" a given step to be twice as long as the other steps, or 8 times as long, adjust the step's timing here. Think you can get a step to be up to 16x the default length with this screen. And then another 4x that length by adjusting the gate screen. Gate is always a percentage of step length so 400% of a 1/16 is a quarter note and 400% of 16/1 is 4 bars. or something.
With gate times longer than 100%, and the TIME button, it's possible to create more flexible rhythm in melodies. As far as I can tell, the limits appear to be that max gate time is 400% (a quarter note,) the TIME button is also limited to 4X the length of the step, and the TIME button will throw sequences out of sync with each other unless they're carefully adjusted.
This may not work with the coding scheme of Quantum, but as an end user, I'd like a tie to work like conventional notation, at least in the forward direction. If you tie two successive 16ths (sliders/clocks) together, they become a single 8th-note step or block. The two sliders lock to the same note. Three tied (locked) sliders (three 16th notes) would become one dotted eighth step or block. If you tie all 16 sliders together, they become one whole note (one bar of 4/4) step or block. In any case, 16 sliders still add up to 4 quarter notes, and sequences with the same number of sliders stay in sync no matter how many ties are used.
It gets more complicated with fancier looping and reverse modes. I would...
In reverse direction from previous step, honor full tie when landing on last clock (slider) in a tied block of steps. In forward motion from previous step, honor full tie only if landing on the first clock of the block. If a jump lands in the middle of a tied block, honor tie from that point on in the prevailing forward or reverse direction. Basic forward and reverse, or sequences with the same looping scheme should stay in sync.
You could also consider tied notes as a single multi-step step, and honor the full tie no matter what clock beat within the block gets landed on. 4/4 or set timing will be lost.
The advantage of tied steps is that melodies can be created with more normal flexibility, and in simple forward and reverse motion, sequences can easily be kept in sync. I would probably not use fancier looping when using ties, but it could be done.
Based on this, it seems like just skipping the note-off and note-on messages between tied notes of the same pitch would do it.
Good stuff. It can definitely be a little weird in a step sequencer when steps with a longer time length are used because as you said, things can get out of sync, visually.
Not disagreeing with anything you suggested but just want to note that there's nothing stop us from inserting N rests after a longer timed step so things remain visually in sync.
Also, a sequence can be set to a slower clock division and most notes set to a higher division (like 2x) so that you (one, not you specifically!) can create longer notes.
I think it's worthwhile to make sure we're all speaking the same language. For instance, I forgot in my earlier post that step time can only go 4x, not 16x. And to be honest, the step multiplier X gate length was from a working assumption so that also might not be true! Either way, it sounds like there's a use case for longer steps (possibly via "ties"). That request is, in my mind anyway, different than the sort of "ties" from something like the TB 303 used for making acid style baselines.
As far as I know, Quantum has everything one needs to trigger that sort of bassline. Presuming the target synth can do its part.
Longer than currently possible note lengths or a better, more humane way to create longer notes within a sequence is a different thing.
Thanks. Good thoughts. I can see that the fundamental unit and focus of Quantum is the single step, and then the app gives us a large number of functions to compose contrapuntal lines within its particular framework. From that point of view, tied steps may not fit the model, and we should accept whatever boundaries or complications that dictates.
I haven't tried anywhere near the possibilities, but it seems melodies made up of longer notes -- whole and half notes, dotted half and quarter notes... and also within the same sequence, shorter notes -- 16ths, eighths, etc. are possible to create with slower clock divisions and the TIME button, and then kept in sync with other sequences. It's not nearly as easy or intuitive a process for me as using ties, so I'd like to see ties incorporated.
I think this thread has fried my brain.
Mine too! I was just thinking about ways to make longer notes (via step length or ties) work so that they're easy to enter and it's somehow visually communicated to the user and then... total melt. If Quantum only allowed for forward playback, things would be a lot easier.
One thought for 'easy to enter' got me kind of excited. You'd just tap and hold, say, the step 3 button and then tap, say, step 7. Then, the note triggered at step 3 would be 4 steps long (or is it 5 steps
). Quantum could mute the interstitial steps so that you see it. Pretty good.... unless the sequence is running in pretty much any direction other than forward—in which case the visual part is just a huge lie.
Not like I've actually thought all the way through it all but I think the multitude of playback directions means that the only way ties could really work, reliably for a step, is actually the existing TIME sliders. Then, no matter what playback direction is in use, if step 4 is set to 2X time, it'll play back at 2X time when triggered. And if you want step 4 to overlap the next note (ala 303 'ties'), regardless of playback direction, the GATE sliders are the way.
And what happens when a RND sequence lands on a stepin the middle of a tie for instance? The permutations are endless. Sounds like a programmer's nightmare.
Exactly that.
Hello All,
I'm new to Quantum and was wondering if anyone here might be able to answer a few questions?
The manual mentions using MIDI controllers with automated faders:
"Great care has also been taken to automate many parameters of the sequences via midi CC or NRPNs and even support external controllers with automated faders (like the Yamaha 01v)"
Does anyone know if this means it would be possible to use something like the 01v to control the 16 faders in Quantum? Specifically, I'm looking to be able to control the 16 faders in Quantum (in Velocity mode) via the physical faders on the 01v and be able to switch between the 6 tracks and have the motorized faders automatically adjust to show the fader levels for each track. Would this be possible?
Also, I'm currently using an iPhone 7, do I need to pick up a Apple Camera Adapter? Are there any other MIDI interface options?
Hi, @morbank
Yes, an Apple Camera Connection Kit/Adapter.
In principle this could be done, although with some effort.
A curious take on it can be found here:
https://forum.audiob.us/discussion/27708/mididesigner-bcr2000-template-for-aum-au-fx-quantum-quanta-in-ab3#latest