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.
Audiobus dock (play pause) transport and Gadget
Hi!
I just started using Audiobus (love it and the community here) to be able to launch Record from various chord apps/sequencers apps (Soundprism, Thumbjam, Firo, Arp Pro, Fiddlewax, Chord Poly Pad...) but I'm running into something unexpected:
Every time I press play from the dock, Gadget launches the very first scene of the session instead of the one opened or last played in Gadget
Is there a way around?
I would just like to practice my chord progressions and then hit record when I'm ready.
Thank you.
Comments
I don't think there's a way to change this other than to talk to Korg and ask them to make a special setting for it. Sorry!
Try this: In Gadget, tap play on the scene you would like for Audiobus to start playback on then hit stop on Gadget's transport. Now, when you tap play on the Audiobus dock it should start playback in Gadget on that scene.
I stand corrected...
Maybe just kneel corrected for the time being, I am not sure what I suggested actually addresses the OP issue.
Oh I thought you actually tried it/use it that way. I'm not very proficient with Gadget so I don't know.
Thanks,
oh so there is no way to control Gadget transports functions (like play pause record rewind) outside of Gadget?
I do, and it does work, but I wasn't sure if that was the actual problem @stelvio was having.
Sorry, not that I am aware of.
To be honest the way I work around this problem while building a track is have modstep doing all the midi editing. I later print the midi into gadget when I'm pretty sure exactly what midi goes where. And in terms of other IAA apps I just host them in audiobus or AUM and send midi to them from modstep. Since modstep is doing all the midi routing I just have to worry about its transport controls.
Not exactly the solution that can help you but more of an alternative...
TLDR:- Midi from hardware/IAA midi apps=> modstep => IAA synths/gadget.