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 a lot for the follow-up !!!
If anyone has a solution, do no hesitate to jump in the conversation.
@SamSamSam - Does the KSP accept midi clock in? Is having AUM be the master an option? AUM can send Midi clock, it just can't slave to it.
Any reason you just don’t set the KSP to receive midi clock?
Edit! What @wim said….sry..I replied on page 4 and it dumped me on page 5 with his response… sigh
@wim, @AlmostAnonymous ,
Yes, KSP is able to receive midi clock, but that workflow does not really work. I gave up that option.
Well, Audiobus to the rescue then for now. 😉
Can you explain a bit more of your situation?
I use multiple hardware sequencers with AUM, and I haven’t found a reason for AUM not to be the clock. Just because I have a hardware sequencer doesn’t mean it needs to be the master clock.
Thanks a lot @wim and @AlmostAnonymous for your messages.
Yes, for me it works without any problem when AUM is the master. But, it’s a bit frustrating to not be able to use the physical controller to start, stop and change the tempo.
I suppose this is also the experience of @GLacey
Start, stop, pause, rewind, etc….sure. Can all do it from a controller. Those tasks are no different than mapping anything else. Just map the start stop buttons to AUM.
Yes, I had something similar experience as @SamSamSam said.
I tried some of those midi mappings, but didn’t work as I expected, so I accepted the fact it won’t work that way and stopped looking for other workarounds than inserting AB3 into the setup.
Anyway, I’ll check it again when I’m back from vacation. Thanks for the tip!
If you have trouble getting it working as you'd like, folks here should be able to help.
Thanks, I appreciate it!
Just to chime in here, MidiFire has a solid MIDI Clock sendable to anywhere. I've been using it for years.
You can also open LoopyPro in a midi bus. Tell Loopy where midi come from (in the synchronization menu) and chose the Midi Clock Sources. Then in loopy pro you enable Ableton Link. Then in AUM you enable ableton link (no need to pay for loopy, you can do that for free). If you do that loopy convert external midi clock to ableton link that can be used by AUM.
That looks interesting. Does MidiFire receives Midi-Clock from an external device (desktop PC) and forward it to Apps like AB or AUM?
I'm interested too
Why would you need another app to forward midi clock to AB? AB can already receive midi clock (and act as a midi clock Ableton link bridge). AUM can’t use midi clock input.
MidiFire doesn't solve the problem of AUM not following Midi-Clock. It doesn't have Ableton Link, which is needed to get AUM synced to an external clock. It can solve a lot of problems, but not this one. Other apps such as AudioBus, which can provide that bridge, don't need it to receive clock from an external source.
I just tried using Loopy Pro in the way described, as a go-between to help send midi clock from one of those sqsl sequencer apps to AUM, but couldn't get it to work. I loaded loopy pro in AUM, I set the sqsl app as midi clock source. I turned on ableton link in Loopy Pro and turned it on in AUM too. I sent midi from the sqsl app to a piano loaded in AUM. I then played with the Gate rate in the sqsl app but it did nothing to change the speed of the BPM in AUM. Am I doing something wrong?
Just asking. Was the sqsl app sending MIDI Clock, or just MIDI Notes?
Yeah that is true. I’ve just never used AUM transport from the very beginning for this reason. MidiFire (and I’m assuming Audiobus) can send Midi Clock directly to apps that are programmed to receive it, even if they are hosted in AUM. This has been my workaround.
Good question - I thought I remembered that it does. I don’t see any option in the app to turn that on or off. Have never tried this before, as I only use AUM and previously didn’t know there might be a workaround. I’ll maybe take another look at the sqsl manual, cheers Dave
Btw Dave - see my edited comment - I wrongly wrote first time that it didn’t change the speed of the piano, that is not correct, it did, of course, and it always does that. What I expected though was that as I changed the rate in sqsl, the rate of synced instruments in AUM (eg a kick drum) would also change, and that the BPM value in AUM would change, but no. Maybe my expectations are misguided, but I thought that if Loopy is receiving midi clock from the sqsl app, and Ableton link was on in LP and in AUM, then this is what would happen. Btw - sqsl must be sending midi clock, as it shows in the list of clock sources in Loopy Pro, right?
Thanks! And sorry I forgot that.
Testing right now - Cubase (desktop), AB, AUM with Patterning in it. 👍🏽🧔🏼🙏🏽
Showing as a potential clock source doesn’t mean that it sends clock. Probably it doesn’t, or it would work. It has never failed in any test I’ve made.
One thing though, be sure to add an audio output to Audiobus. Just the system output with nothing feeding it is fine. It won’t make any sound. This is necessary in order to keep Audiobus from going idle when in the background.
Hi Wim, I wasn't using Audiobus, only Loopy Pro and AUM, using the method someone described above:
"You can also open LoopyPro in a midi bus. Tell Loopy where midi come from (in the synchronization menu) and chose the Midi Clock Sources. Then in loopy pro you enable Ableton Link. Then in AUM you enable ableton link (no need to pay for loopy, you can do that for free). If you do that loopy convert external midi clock to ableton link that can be used by AUM.'
I'm guessing though that when they said' open loopy pro in a midi bus' they meant in Audiobus, even though they didn't mention Audiobus?
Showing up as a clock source only means that the app has a midi output port. Loopy doesn't know whether the app actually sends clock from it.
Use a midi monitor to see if the app actually sends clock.
Sorry for the confusion. I read the post too fast and got confused over the apps being referenced. Anyway, the point was, showing as a midi source doesn’t necessarily mean an app sends clock.
Indeed, thanks, and I checked with the dev and the app doesn't in fact send midi clock. 😁 🤷♂️
Still, useful to know this trick.