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.
How do I solo inputs
Hello to all, so essentially I am running the fairlight, ielectric, wavemapper, and others in my band but when I have them all launched and ready in audiobus, I hear all 3 synths concurrently running. How do I get it to only play the selected input? Is this just a quirk on my applications or is there a setting I need to do. Thanks anyone's help would be appreciated! Also, if it makes any difference, I am using irig midi into an amp thru my headphone jack.
Comments
You need to assign different midi channels to each app, and then set your controller (which is what I assume you're doing) set to the same midi channel of the app you want to sound.
This is a use case Audiobus' MIDI implementation could solve.
@syrupcore how so?
If Audiobus took on the some of the stuff that MIDI Bridge does, you could, for instance, point your controller at specific apps in the audiobus input slot and bypass others.
I think the thing most of us want from AB's MIDI implementation is clock but live use cases like this will likely seem trivial for these dudes compared to clock!
@syrupcore well sure that'd be great but I think @funjunkie27 had the better answer either way.
I am still unsure how Audiobus plans to solve all the worlds problems by adding a master midi clock. Won't all the apps still have the same problems accepting the messages no matter who sends it? Or are we talking about re-writing the MIDI standard and waiting for all devs to update to this standard as part of an sdk update? Imaginably a complex one. Also you are talking like Audiobus MIDI is a known fact.. I might have missed it but I never heard Sebastian or Michael say they were doing anything either way. Are they? Did I miss it?
No, I don't think they've said anything explicit but lots of head nods in the general direction of midi.
And yes, @funkjunkie27 nailed it for now. I'm saying that if the AudioBus app also included MIDI routing as has been hinted at, directing your hardware controller to a specific app via virtual midi and telling it to exclude others seems like an obvious use case to design for.
Or you could have midi triggering all apps at once, and just have an audio mixer within AudioBus to fadeout, fadein, mute or solo different apps.
You don't need midi implementation to make this happen.