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.
Clock sync issue with ext arpeggiator (Minilab 3)
I am having trouble getting my MIDI controller (Minilab 3) to listen to the EXT sync from Loopy Pro.
It seems only to take the clock signal if it hears the start command from LP (ie from pressing the LP transport Play button). The arpeggiator on my controller works as expected in this circumstance.
However, if I try to start the arpeggiator when the track is ALREADY playing, it doesn't pay any attention, and thence makes no sound.
This feels like a LP issue rather than a Minilab issue, but am a newb and could be mistaken. I understand that MIDI clock 'start' v 'continue' might be an issue, but I can't seem to find any settings to change that in LP.
I tried the 'sync trick' detailed here https://wiki.loopypro.com/Sync_Tricks_With_Loopy_AUv3 but that suffered from exactly the same problem, only one layer down.
Sincere thanks in advance for any help you can offer!
Comments
This sounds like a Minilab configuration issue. You might want to change the thread title to something like “Minilab 3 Arpeggiator Sync Question” to attract the attention of other Minilab users.
Hosts generally only send start or continue messages when their transports start or unpause. If that is happening, this doesn’t seem like a host-specific issue.
If the Arturia requires a start message and you aren’t starting or unpausing the host transport, you can try to manually send a start clock by putting a Send Midi Message action in a button. Loopy has a custom message type where you can enter any midi bytes, such as clock start.
Maybe the Minilab has a setting to not require hearing clock start from the host?
Thanks @espiegel123 - really appreciate the response.
The button idea is a nice workaround - a quick stop/start of the Loopy Pro midi processor AU mentioned in the Sync Tricks link would do the trick.
Yeah, the more I'm reading, the more it seems that the way the Minilab 3 listens to the clock might be the issue - apparently there's been feature requests, either to allow the Minilab to be the master clock or to let it receive clock without a start message.
I was hoping there might be a way to configure the LP clock output to accommodate it, but seemingly not. I might be able to use some kind of midi filtering software, but I'd really be getting into the weeds then...
Cheers!
I don’t see what change a host could make or how filtering software would help. If the Minilab only pays attention to clock after it receives a start message, you need to send it a start clock message.
I was under the impression that something like Streambyter might be able to intercept the clock signal and send a start signal in its place - but the workaround is probably the easiest until one of LP or Arturia makes a change.
@troutio : what change are you suggesting a host would make? The Minilab needs a clock start message. Loopy sends the start message when the clock starts.
Start/Continue is a one-time message (hex FA). Clock is a continuous stream of messages (hex F8) being sent 24 times per quarter note. So, "intercepting" it isn't a matter of converting just one midi event to another. You have to have some other event that says when to send that Start message.
There's no change that Loopy or any other host can make.