Audiobus: Use your music apps together.
What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.Download on the App Store
Audiobus is the app that makes the rest of your setup better.
Making it all work together (AB3, AU, IAA, Link, midi/IAA sync)
I’ve been struggling with building my live rig back up again since I’ve moved to iOS 11 and AB3.
I’m starting this thread as a place for info regarding the above IOS elements (AB3, AU, IAA, Link, midi/IAA sync).
It seems t me that we have a IAA phase out and AU expansion which seems to be a good thing for users and developers alike. Since we’re yet again in transition it can be quite a painful experience involving loss, fear or the unknown, learning curves etc.
I’m finding myself bang in the middle of those technologies and often get bright ideas only to find out that they won’t work in practice due to limitations specific to those technologies.
This morning I tried to insert replicant into an AB3 effect slot only to find out it won’t listen to Loopy’s clock. I looked to point MIDI clock from Circuit but Replicant doesn’t appear as a midi destination.
So I tried frekvens as a AU effect. I had some midi mapped in standalone. Same thing, tried to point my controller at it but can’t find it in destinations and mapped controls aren’t retained in AU.
I’m hoping ones in the know can give us an explanation in some categorical way so we don’t wander in the dark followed by IAA zombies etc.