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
16
I don't think that's correct. There is one output waveform with 16 points output as MIDI CC values to create an effective CC "waveform". What's unique is the computed waveform is derived in a very creative fashion and not your usual selection of sine, triangle, sawtooth, square, sample and hold, etc.
Being an AUv3 app you can probably run 16 copies if you have the spare CPU... it's just doing math so it should allow a lot of instances. You just have to live with the many GUIs to set up iteratively. But AUM allows for you to create 1 instance and clone copies that can be tweaked in order.
Are there multiple midi cc outputs or just one?
It has up to 16 outputs from a single complex LFO waveform.
It uses some FM technique to create a complex wave from two simpler waves.
It then lets you create up to 16 separate CC outputs that are based on 16 different time points across a span of the complex wave. This creates a cascading effect across the 16 outputs, since the output values are based on 16 different phase points, or time snapshots across the waveform at any given time.
So if you take a snapshot of the wave and note the value at time point one, if you then move forward in time and the wave form cycles, the value you initially noted for time point one will roll through the other time points at the frequency of the wave, creating a value that gets output by each successive CC after a small time delay.
Have asked the dev to make it capable of slower speeds, he welcomed the suggestion and is working on it. That will make it amazing for ambient use cases. Anyway, it is a really interesting lfo app and totally different from anything else we have on iOS
Thanks for clarifying! Sounds great. Will give it a go.
Might you do a vid on this @Gavinski ?
I'm very intrigued by this app, but I find LFOs pretty hard to understand in the iOS environment, and this one looks kinda inaccessible (to me). A video explaining how to use it would almost certainly cause me to buy it....
Yes I really want to but am having issues with my ipad jack and mic, which is why I haven't done a spoken walkthrough in a while! I also found it hard to wrap my head around at first, but read the manual and you'll get it if you keep testing things out while reading!
Ok cool, I'll probably grab it then. No hurry for a vid, but would be good if you did one at some point. Good luck sorting your jack and mic buddy...
Thanks, bit of a nightmare but I'll spare you the details 😂. It's nice in some ways as it's making me focus on just making interesting musical demos, which I really enjoy more than making tutorials, in many ways!
This thread is spelled wrongly by the way - I just did a search and nothing came up. Why, because both this and @Poppadocrock's duplicate thread are spelled 'Ifoch' with a capital 'i' instead of lfoch with a small 'l' (L for LFO, right?!)
Maybe @CapnWillie could change the thread title.
Anyway, just had a weird problem where I had lfoch open in aum. I bypassed it for a while but when I put it back on the chain it wasn't altering its destination instrument any more. I closed the aum session exactly as it was and opened it again and now, magically, it was working as it should. Is this a bug in lfoch? A bug in aum? Or just some random weirdness? I wasn't able to replicate it just now, I suspect it only happened because it had been bypassed for some time, while the aum session was lying open but the transport not actually running
@a_n, or anyone else, any thoughts?
That's because the other OP misspelled it as ifoch with a capital 'i'. I also wasn't able to find this thread though when searching in the forum for lfoch with an 'L' 🤷♂️
Hello! Sorry, haven't encountered that bug yet. Will test more and if i get any news on that, i'll post here. Thanks for the feedback!
Cheers!