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.
SOLVED Mollilooper: midi trigger for loops not working w/AUM and audible clicking on loop trigger
I just bought mollilooper hoping to trigger looping via midi cc through an lfo or sequencer sending cc synced to tempo so loops would trigger and disengage exactly on the beat periodically... I'm not interested in using the app as a live performance tool.
When I map start looping x bar length or the start looping to midi in aum, nothing seems to trigger.
Also, I can hear some audible clicks when the looper is set to fully wet.
If I could get a sample and hold lfo to trigger the looper every 4 bars or so without any clicking, I could see this being a great part of my live Berlin school setup. I was hoping to send the audio of a sequence to mollilooper on a different channel with bleass slow machine on for either an octave down loop or less for some harmonic accompaniment to a melodic sequence.
Has anyone been able to get Midi cc to work or am I just messing up? Channel and CC# seem fine, and when I just use midi learn and map a note on my keyboard that doesn't work either.
Also, the click is a perennial issue with bloopers in my experience, but I was really hoping this wouldn't be noticeable. I think that if I were looping noisier audio or a busy beat sequence that this wouldn't be noticeable, but I've been using it on keys or pads, which is ahem daintier.
As always, any comments are super appreciated!
EDIT:
the midi control for loop triggers reads as 0-1 for cc, which made me think cc had to send value 1 or 0 to trigger on or off. It's actually that the whole range from 0-127 is used, with any of the higher half of the values triggering on and the lower half of the values triggers off.