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
Thanks for the rapid reply.
Just so happens I'm deeply immersed in mLFO right at this moment and that was one of the things I was testing...!
To be honest, it is a little on the high side. Not in the bigger scheme of things but for a simple MIDI utility you hope that overhead is pretty much negligible.
Really? I've been testing with an instance of Factory with Autony sending MIDI notes, and without mLFO DSP was around 20%. With mLFO loaded and 4 LFOS running, I'm only seeing peaks of 21 - 23% - this is on a 3rd gen 11" iPad Pro...
MIDI utilities on iOS can be a little on the expensive side when compared with their desktop peers. It’s why I tend to look into efficiency first. Although sometimes efficiency looks worse than it is as the device is running in efficiency mode or worse still switching between efficiency and power modes. To get a truer sense of efficiency, it’s better to test in busier sets with multiple instruments loaded. This ensures the load kicks the processor into overdrive. The other thing to consider is how the plugin is running in Cubasis 3, which benefits from multicore processing.
Thanks - I'll bear that in mind for future testing - I generally look at DSP loading in AUM although now I have a more powerful machine it's usually less of an issue these days!
How does it compare to MIDI Mod? Both are currently priced at $2.99.
https://apps.apple.com/us/app/midi-mod/id1465677026
Seems minimal on cpu to me. I’m not coder but most AK apps have sounds, effects and generally a lot more going on, which based off my understanding will naturally drain more CPU then just sending out cc data.
@jonmoore & @enkaytee
What you're seeing there is a combination of mLFO's overhead and overhead from the effect the modulations have on Factory. Factory is going to add overhead receiving the messages, processing them, possibly animating its UI elements, and processing the sound. There will also be host processing overhead. There's no way to know how much each app is contributing.
The best you can do to measure is to compare idle host CPU to host CPU with mFLOs running not routed to anything else. However, a 1%-2% difference in DSP is statistically insignificant on iOS anyway. Any app is going to add at least that much just by being loaded and sitting there. And as we all know CPU measuring is far from exact science on iOS to begin with.
Maybe so… but still low for the AK framework.> @aaa said:
Unfortunately midi mod is not Au.
Yea CPU/DSP are really relative, but you can get a general idea based on your usual performance on your personal device.
Oh yeah. Bought. Fingers crossed for S&H too…
Update, first impressions: good, I believe you can in fact uncouple the lfo rate from the host tempo by hitting the word ‘host’ - but, bug report, if you ‘zoom in’ to an individual lfo parameter, it fills the AU box with no way back to the original ‘overview’ screen that I can find
This stumped me too but @enkaytee provided the solution via this image:
(Tap where the arrow points to exit)
@Proppa , @enkaytee : thanks! That fixed it. Not at all obvious though… maybe a simple ‘Close’ button would be a bit easier to grok
Update with random LFO Waveform is out
Yes!
Well, it is pseudo-random waveform. In fact there is a static "random" wave that doesn't change every cycle. This is not, in my opinion, what some of us were expecting
Is there a way to trigger the “random” wave to change?
UPDATE: I couldn’t find a trigger to change the wave, but Rozeta LFO does sample and hold very of course.
Yup is not sample and hold in the latest update.
Is there anything in this which is better than Alessandro's "Send Midi" LFO app? Send Midi has a playable x/y pad for each pair of LFOs and they all have their own midi port. You can rename them too.
Other than having 16 LFOs vs 8 I don't see much else...
I never realized you can rename them. Nice!
LFOs can't modulate other LFOs. Or is that something else I've overlooked?
Ah thanks
Not sure if you can do that with Send Midi, at least I haven't tried it. I think also that this new app might be able to go slower, do you know how slow it can go?
Just had this reply from the dev regarding the random waveform:
"The waveform that is displayed in the UI is not random (for performance reasons), but the audio engine does generate a random value at every pass. For example, if the ‘Beats’ value is set to 1, the audio engine will generate a random value between Min and Max every 1 beat. If the ‘Beats’ value is set to 0.25, the value will be generated every 0.25 beats, that is every 1/16 is musical time."
So a static wobbly waveform then?
Thanks for the infos👏
Ok I understand now. One random value is generated every cycle and the waveform is just an icon
Yep - exactly...👍
Got it! 💡
Is anyone having serious crackling issues with this app. I’m on iOS 15.3, simple setup in AUM, and when I assign MLFO to any parameter I get this gnarly crackling sound that never goes away. Just Put in Rozeta lfo to test and it’s smooth, no issues. There’s No cpu/DSP spikes, just one lfo sine wave going to Bleass filter’s frequency and I’m getting horrible crackling. Tried other destinations and getting the same loud noisey/crackily sound, no matter what I assign it to, its creating the same issue. What’s weird is it did not do this when I originally downloaded it a few weeks back. Tried it in another session same issue and not sure why an lfo barely moving a filter frequency would even make such a loud continuous crackle that overtakes the actual sound. Is anyone having this issue with MLFO?
Not sure what’s going on… I know I can delete and reinstall but curious if anyone has come across this or is having a similar problem, cheers. Hoping it’s an overlooked user error or something developer can fix if needed.
Still a bit unclear - does this really offer anything more than art kerns' midilfo? Apart from the labeling feature, which for me personally is not important. It's also hard to beat Art's interfaces, he's the king of iOS midi in my book