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
@artkerns I understand... but I just wish Gadget sent a midi clock out
.
Thanks Art!
This really is a great app...I've been using it to control the Moog Theremini among other things, which is a great controller/synth that really benefits from having more LFOs/ modulation to drive its many CC hooks. This is just what I was looking for!
Another great app/addition would be one that would have envelope generators that could be triggered in various ways and send out CC info.
Think about it!
This is actually a rather marvellous idea... Going to modulating the Brussels filter for some turbo charged bass
Has anyone been able to get clock sync working? I have followed the manual's instructions for "Simple MIDI-synced LFO" exactly, and cannot get it working. I tried with Cubasis, Loopy, Gadget, and even Art's own Funkbox app. I set the master app to send clock out. I set MidiLFOs Midi In to that app. I go to LFO1 and click SYNC to turn that button red. The slider says NO MIDI CLOCK. I start the master app. It still says no clock.
In Cubasis, after I hit play and go back to MidiLFOs, The LFO stops running, the app becomes unresponsive for a few seconds, and then it crashes.
I'm on an iPad 2 running iOS 8.4.
I got it working. Slaving to Loopy. I had to restart it once I'd launched loopy. It was a bit temperamental to connect. Then it worked fine.
Keep trying with Loopy.
>
And this one
https://liine.net/en/products/lemur/premium/lfo-studio/
Thanks!
yes, so many toys, so little time
I tried and tried with Loopy, and got it to work, once, but I couldn't repeat it. The one time it worked, I did as you suggested and restarted MidiLFOs and it synced (although it reported the tempo to be double that of Loopy's.)
I got it working with Funkbox by telling Funkbox to not send clock to MidiLFO, and only send it to the virtual port. And MidiLFOs reported Funkbox's tempo correctly
Cubasis, still no sync. MidiLFOs crashes after I start Cubasis and switch back to MidiLFOs. The screen freezes, including the animated dot, hangs for 3 or 4 seconds, then reboots itself. This happens if MIDI IN is set to ALL, Network Session, or Cubasis.
Has anyone gotten this to sync with Cubasis?
@gburks
There is a 'Backgound' setting in the main options. Have you got that switched on?
@xen, Yes, I have it set to on.
I got double tempo from loopy. I fixed this by unchecking midiLFOs in loopy's midi settings.
Whenever you see the double tempo thing with any apps it's almost always because the app is getting the MIDI clock signal twice. Could be because of port settings, could be that two sync'a apps are sending that app clock.
Hey Art...
Any timeline on the update to this fine app?
Hey, an update is coming. I am finishing up a second MIDI related app that shares some of the same MIDI code, so I've been working on them and testing them together and wanted to release the new one alongside a midiLFO update. But finishing iOS apps always takes a lot longer and expected and as usual this one is behind schedule. I'll try to get the update out soon even if the other app continues to lag.
Syrupcore is exactly right that twice the tempo usually means the app is receiving two clocks. Most apps automatically send on their virtual output, so if you also tell it to send a clock to midiLFOs virtual input and midiLFO is listening to all inputs, it will see a clock on both the other apps MIDI output (which for midiLFO is a MIDI input) and its own MIDI input. Not confusing at all, right? I'm hoping to get this working a little easier and more automatically as I update the apps but there will be some trial and error along the way.
It definitely shouldn't crash with Cubasis or any other app, I just tried it and it does for some reason, so I will fix that. Thanks for the interest and patience.
@artkerns, thanks for looking into the Cubasis sync issue! I'm having fun with this app even without sync but really looking forward to using this in Cubasis!
Tip of the day: this app is great for automating the x & y variables in BitWiz.
Can each lfo send to seperate apps?
Yes!
This is a a really cool application, a big step towards turning the iPad itself into a synth. Thanks @artkerns!
Gadget experimentation - so many cc to assign, really fun with Tokyo etc. seems that the effect of the LFOs on a given gadget are only audible when that gadget is foreground, not sure what this means for the render of these tracks- is it necessary to press record for the LFO action to be rendered hmmm I think I answered my own question?
Woah, really makes Egoist come alive! I didnt realise initialy that reusing the same lfo on multiple paramters would work so well.
@Littlewoodg - it shouldn't be the case that you only hear the effect in Gadget when it's in the foreground. I've never had that before with sending midi cc changes to Gadget. Are you sure?
Only the gadget that is in the foreground, or else is selected in the mixer with the yellow dot, can receive midi control. But you can record the automation into the track and move on to another track.
Yep. That's right.
I thought @Littlewoodg meant the app needs to be foreground though. Which I'm sure is not the case.
Thanks @gburks-
And thanks @Matt_Fletcher_2000, it's a slight problem with the Gadget nomenclature- the app is Gadget and its components are gadgets, so the effect of LFOs on "that gadget" in my post meant Helsinki...and per @gburks it seems that "that gadget" needs to be selected, and recorded to get that LFO action baked into the eventual render...
Ah. Yep. That makes sense then.
Using it with Egoist I find it stops after a while and i have to maximize midiLFO in order for it to reconnect. Not a huge deal but for those wanting to do live shenanigans could be an issue.
Hey @AudioGus, the default background mode for midiLFOs is 5 minutes, after that it will stop calculating and sending the LFOs. If you tap "midiLFOs" and go to options, you can set background mode to "ON" which keeps it going forever. Just remember to flick-quit the app when you're done so it doesn't use up your battery in the background, or change background mode back.
Oh I see, thank you much! Makes sense. And thanks for this awesome app, I have been loving it!
@artkerns
Regarding the cubasis issue I find on my ipad air it works flawlessly but on my mini2 it crashes. Same exact apps and setting but yah something about the mini for me...
Updated.
'Tap tempo
Dot and triplet timing options
Faster and slower LFO options
"TRG" link option where all linked LFOs retrigger when any of the linked LFOs are triggered
Option to trigger LFO with any incoming MIDI note
Velocity of incoming MIDI notes can now be used as a MOD
New TOUCH mode turns on LFO only when screen touched, or while MIDI in note is held down
Tapping on the LFO in LOOP mode now triggers it instead of turning it on/off
Set MIDI CC# automatically with incoming MIDI CC and open output popup
Set high or low MIDI CC values with incoming MIDI CC and open CC popup
Display glitches fixed'