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.
Can AB3 MIDI Inputs be fed by other MIDI sources?
For example, can StepPolyArp in the AB3 MIDI Input slot be fed by ChordPolyPad? The latter is not yet an official AB3 MIDI source. Thank you.
Comments
Sure can, I've just had SPA in the input slot and tested with GeoShred, ThumbJam and Navichord. Just select SPA as the output target and you're good to go.
@TheVimFuego Thanks, but for some reason it is not working for me. Outside of AB3, I have ChordPolyPad to StepPolyArp to Animoog working fine. When I launch Audiobus3, and put SPA in MIDI Input and Animoog in MIDI output, playing CPP no longer works, even if SPA is set as the MIDI output notes target. Very odd. Same thing with Thumbjam.
@TrustButVerify This is embaressing, I can't get it to work either now. I could've sworn SPA was on the bus earlier ...
On the website Audiobus devs recommend to restart, 99% issues disappear.
StepPolyArp will shut down it's own MIDI configuration screen while being connected to Audiobus's MIDI system. This is necessary to avoid double routings, double notes... etc.
You can use either external midi interfaces or Audiobus compatible MIDI controllers.
@Sebastian Thanks. I guess I can either wait for CPP to support AB3, which I assume the developer of SPA plans to do, or just manage MIDI outside AB3.
I've contacted the developer of CPP. Lets see.
Thanks, that would be very much appreciated, if CPP got AB3 ready.
Do you have plans to allow external keyboards to Audiobus MIDI space? Looks very important to me.
It is already allowed.
@DeVlaeminck, thanks. I can see it now
I usually use Midimittr (midiLE USB) and then connect a bunch of MIDI stuff via Mac. Unfortunately Audiobus doesn't see Midimittr as keyboard, hence my setup is not working with Audiobus.
It would be cool to have a MIDI input block allowing mapping from CoreMIDI to AB MIDI, this would solve the problem.
I cannot agree more. We need some solutions to get on, at least while things are developing. I respect and agree with the restrictions relevant to keep AB3 MIDI clean and safe from CoreMIDI. I also respect agree to make shure that the SDK is solid before launch. The problem is, that this is exiting, to an extend where you really want to explore the new possibilities. So we need the CoreMIDI->AB3.filter sooner rather than later.
So come on @JohannesD
You are probably the one person in the world who can do this now. Please.
Another idea might be to have an easy mode and an advanced mode, similar to what they did with gadget. So in advanced mode you could do all things possible with core midi and in the simple mode that stuff would be hidden.
@Sebastian can you comment on this idea? Is it something you foresee for Audiobus?
I think a solution to this is already under consideration.
More details on this thread you might find interesting :
https://forum.audiob.us/discussion/18196/ab3-what-qualifies-as-a-midi-sender#latest
I like it.
Core MIDI sources have one massive problem: They disappear once the app that has them is turned off.
I know it's not obvious to users but all MIDI channels are defined in an Audiobus database, which means Audiobus knows what's going to be available when a project is loaded. If we allow Core MIDI ports, then that goes out of the window and we're back in CoreMIDI hell.
Maybe I'm missing something, but couldn't you just have a pair of AB3 virtual ports that are visible to other Apps with coreMIDI support? (Input & output)
These Apps sometimes remember the last ports and channels used if they are available which would be the case as long as you launched AB3 first.
Even if it was limited to a single AB3 virtual port you could channelise the MIDI to give some flexibility with the new MIDI features.
This wouldn't pollute the new MIDI ecosystem too much and would allow people to use some of their golden oldie MIDI Apps within the new system, albeit without specific routings saved as part of the AB3 Preset.
If this is feasible, wouldn't there be potential bottle-necking issues with all the MIDI data on the single AB3 virtual port? Or does that only pertain to hardware ports.
.
Yep, on second thoughts you would probably need an input/output component that you could have multiple instances of to really make this work with more than one source/destination.