Audiobus 2 – a major update to the app-to-app audio routing app for iOS – is now available.
Audiobus 2 introduces a new interface and a number of significant new features:
- New Multi-Routing feature (In-App Purchase) allows unlimited connections and effect chaining.
- Presets let you save and share connections and the settings of the individual apps within your Audiobus workflow.
- Multi-channel input hardware support.
- New hardware latency controls
A list of apps that have been updated for compatibility is available in the Audiobus forum.
Here’s a video overview of the new features in Audiobus 2:
Presets in Audiobus 2:
State Saving in Audiobus 2:
Multi-effects in Audiobus 2:
Vio as an Effect in Audiobus:
Audiobus 2 is available in the App Store for US $4.99.
If you’ve used Audiobus 2, let us know what you think of it!
Could piping audio between devices ever be possible? – AudioBus 3 ?
Only if Apple allows it.
Apple actually doesn’t have much to do with that. At least if one’s not using any hardware.
Actually they do. Apple makes the API and does not allow any devs to use his own API. It is possible to create an API that could do such things as piping audio between devices, just like it is possible to use two apps side by side in windowed mode on a jailbroken ipad, but Apple does not allow it.
Just in case you didn’t notice: I’m one of the guys who make Audiobus.
Here’s a video that proves you’re wrong. https://www.youtube.com/watch?v=xjs0qCr3V8Q
I admit I am wrong about this one, and I did not know you are from the Audiobus team which btw I have immense respect, if it weren’t for you guys we might have never been able to connect apps together.
But there are many other examples that shows how Apple controls what developers can do on IOS. Orphion had to be modified because Apple wanted to remove it because of its private touch sensing API. IOLibrary, the precursor to ACP, was removed because of its unallowed use of the DCIM folder (and all the apps using it were forced to be modified to remove the conduit). Unapproved VST’s are not allowed in Auria. Not counting the numerous GUI and Shell modification like multi-window, skinning (and before IOS4 multi-tasking and wireless sync). Apple won’t allow them because all those apps uses unallowed API’s and system calls.
If you could truly create and distribute any kind apps for IOS like you can for OSX you would not need Apple’s approval.
Yet another fantastic update guys!
Thanks for consistently delivering a quality product.
Thank you! 🙂
i think this really highlights the importance of apps to be able to record their own automation. i’d also like to see more apps that allow you to map parameters to input level, to allow for more reactive dynamics without you having to switch views to the app itself.
do apps generally work okay trying to control a few at once with different parameters mapped to different or the the same MIDI CCs? i mean yay for audio routing, but i want to interact with it at once, the sound generator, the effects, even the thing recording, if i need to bring the levels down.
anyway, audio bus is pretty great, i just need a faster device…!
I had a bit of trouble getting it going but once I deleted then reinstalled it was all good. I was using PPG Wavegenerator, Echopad, AuFx Dub and DM1 Along with Audioshare pretty much no glitching on an iPAD 2. Fine job on this update guys.
Pure genius, thank you Sebastian et al for listening to users like me and implementing brilliantly. You guys are changing the world! Developers let’s get state saving 🙂
Sebastian awesome job on this update.