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.
Sync Auria Pro with Quantum Sequencer
I am trying to slave Quantum to Auria Pro's midi clock.
Have tried standalone & routing through Audiobus, AUM, Midi Bus, & MidiFlow, with no success.
Auria has no option to receive & slave to midi clock, only MTC.
Quantum only sends & receive midi clock
Tried every possible configuration I can think of & also tried the same with Fugue Machine. Does anyone know how to get them to sync, or a date that's syncs more easily (was looking at MultitrackStudio) ?
Comments
It works with latest Auria Pro and Quantum, however, it's very fiddly.
In Auria Pro, set Send Clock to Quantum.
In Quantum Devices, set the "Quantum" Input "Active" On and "Receive Midi Clock" On
Note, it's important to set both apps to "Quantum" as that's the named port that Auria is sending to and Quantum is receiving from. Don't set Auria to send to "Quantum" and Quantum to receive from "Auria", that's not how MIDI ports work.
In Quantum Options, set "Tempo Master / Slave or Note In" to Slave and "Midi Clock" to On
Note, there seems to be a bug in 1.8 where if you try to cycle around from Slave back to Master Quantum will crash. So don't do that! If you do crash Quantum, Auria will need to be reset to send clock to Quantum; that setting won't persist through a Quantum crash.
Theoretically, this should work, however, it's more than likely that starting Auria doesn't actually trigger Quantum.
Press the Play button in Quantum (it will be running at its internal clock speed) then press Stop.
This will likely have switched the "Tempo Master / Slave or Note In" setting back to Master. Set it again to Slave and now if you press Play, it should say "Waiting for Midi Clock"
Now if you run Auria, Quantum should play, synced to Auria's MIDI clock.
Easy, right?