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.
StepPolyArp strange arp behavior when Loopy clock is running
Midi keyboard input (Oxygen Pro) => StepPolyArp => Scaler2 piano => output
StepPolyArp is setup for a simple 4 quarter note pattern (arp mode)
When the loopy clock is off/paused, I can retrigger the arp pattern instantly by releasing all keys and pressing a new key. This is great for adding some quick transitional notes as needed while playing.
When the loopy clock is running, the arp pattern retrigger delays to the next downbeat or perhaps next half beat. It is either inconsistent or follows a rule I don't understand.
I can see how both options (snapping or no snap) can be useful in different situations, but how do I actually control this behavior? I currently need no snap all the time (if clock is running or not).
After some experimentation I have found that this behavior is tied to the "Speed" field in steppolyarp. This is the setting that governs the length of each block in the arp grid.
Apparently, when the midi clock is running steppolyarp seems to quantize the start of the arp pattern to this grid. When I had it set to 1/8, this was very noticeable and problematic for this song. However, when I have it set to 1/32 (and stretch my patterns accordingly) it is much less noticable.
I don't know if this is intended behavior, just what I have observed. What is the real expected behavior?
A second question is with the pitch quantization to your selected "scale". For example, if I am in C major and I want my arp to play the normal chord progressions (C, Dm, Em, F, G, Am, Bdim), I would assume that I should set my pitches to (+0, +4, +7) and then Sharps from that calc would get "quantized" to the non sharp note and I would have my proper chord progression. Does this work? If so, how would it work in other keys? Does it always shift down a semitone when "quantizing"?
Comments
I emailed the developer on this and he quickly cleared it up (amazing support!!):
The time quantization of the ARP when a clock is running is the expected behavior. It is quantized to the next grid step. This is actually in the manual.
For the scaling, steppolyarp quantizes note pitch by shifting UP to the next valid note. You should use (+0, +3, +6) to create the normal chord progression, with the understanding that this won't work in all scales.