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 StoreAudiobus is the app that makes the rest of your setup better.
Comments
In Audiobus, you can route the Loopy outputs into Auria. It isn't a Loopy configuration thing.
Coke vs Pepsi, Ford vs Chevy.
Use what you like. Like what you use.
I believe there's an imminent update to AudioBus that will provide improved MIDI sync functionality so that AudioBus can act as a conduit between Ableton Link enabled apps and those that only allow for MIDI sync. Auria is one of those apps that held out on Ableton Link so this should help when syncing between Auria and an Ableton Link enabled app.
Someone on the AudioBus beta should be able to clarify (and maybe correct) this info.
It sounds as though you may not have read my post carefully. When adding Loopy into the input slot in the pipeline, don’t just add Loopy. Click the > arrow next to the name, then you will be given a list of available outputs from Loopy.
[edit] Ahh ... wait. Only loops that have something in them will be available to select, but you can indeed select each one. Maybe that’s what tripped you up.
This is most definitely true, Audiobus will soon serve as a way to sync up pretty much any group of apps as long as they have at least one of the three link options (ableton, midi clock or inter-app).
Yep! And it works great. In testing, I set up a crazy complicated tempo track in Auria Pro, with sudden dramatic tempo changes, ramped tempo changes, etc. and it tracked beautifully, sending link out to AUM and midi clock out to other apps and hardware no problem.
Auria doesn’t respond to midi clock or link, so it has to be the master, but other apps not limited in this way slave as well as their respective implementations allow. From what I can see Audiobus has not been at fault when there have been any sync issues.
Good to hear, haven't tried any tempo changes myself. Happen to have any insight regarding the best way to get Patterning (1 or 2) to sync up with a session? Seems like there's always something that doesn't respond to AB3 the first time i.e. Patterning starts, but nothing else does, than Xequence starts and Patterning stops, etc. I know this was addressed in another thread but I haven't been able to find it again.
Auria Pro seems to add more than one input for each Audiobus output. I think it’s a bug, and I think I remember reading about it long ago, but apparently it was never fixed.
Personally I don’t think I’d make use of Loopy > Auria. I’d just export the audio files from Loopy and dump them into Auria. But it’s always good to know one’s options.
I have AB3/Loopy/AP set up and working right now with 5 tracks. And sending the AP Subgroup1 to Loopy as its input.
It took me a little while to figure out a few quirks:
in AB I needed to assign AP as an audio input in order to also assign subgroup 1 to another lane.
as someone else noted, AP created more tracks than needed and the track order was not in the same order as the inputs. Once I straightened out the assignments, all was good.
My ipad can’t show the full config on one screen. here is what the AB setup looks like split in two screen caps.
Is AP only allowing 8 stereo tracks in this context for you or always?
I just went up to 9 tracks without issue.
I am not sure I understand your quandary.
I didn’t use the input matrix, but I confirmed that all 9 Loopy channels were playing through their correct faders in AP.
Btw, unless I needed those loops wired into AP, I wouldn’t set them up this way. I’d just load them up in AB3 or AUM and run it synced to AP. Because to monitor the AB inputs in AP, the tracks need to be record enabled which results in lots of unnecessary audio being recorded into AP.
@wim @tja @espiegel123
Wow, you boys went on a mighty long journey their ref Loopy/AudioBus/AUM/Auria. Once you've come to some solid conclusions, that content should live in the Wiki. It would be a real pity if it were lost in this thread.
Nice work!
There is an existing knowledge base article pointing to a Loopy/AB3/AUM setup discussion that covers this. So, it'll get wiki-ized