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.
Multiple AUv3s with a single app bundle? SOLVED
I've got a few updates going through internal testing before going to app review so I'm now turning towards future projects. I wanted to ask any developers/users if it is possible to include multiple AUv3s in app bundles? Does anyone have any examples of this being done? I see 2 main reasons for this being done:
- Low/lower latency version combined in a bundle with a higher quality but high latency version
- Low CPU version combined in a bundle with a higher quality yet CPU intensive version
I've got an idea which encompasses both of these issues... Currently a lower CPU version with ~10ms latency and a high CPU version with ~60ms latency. I'm sure I will be able to get latency down further but at the moment there seems to be tradeoffs in every direction. I've seen this type of thing with Acustica plugins on desktop before but I've not come across it on iOS. I'd be very interested in seeing some examples of this on iOS. Also, if it's not the done thing/actually possible I'd be very interested to hear opinions of how to deal with the topic:
- Make the plugin low latency but lower quality audio (it is still sounding excellent).
- Make the plugin high latency but theoretically increased quality audio (I can add a few extra features that otherwise would not be possible).
- Do some sort of App Store bundle with separate apps
- Other option that I haven't thought of...
I may yet (and hope to) solve the issue by making the higher quality algorithm far more efficient so this is early stage thoughts but I'd love to hear perspectives of different people.