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.
MIDI Learn for Previous / Next Preset Buttons
I have a simple request for all you app/plugin devs out there:
🙏🏼 Please, please, please make your Previous Patch / Next Patch buttons MIDI-assignable. Please. 🙏🏼
When making “music”, I use all sorts of different gear, apps, plugins, etc etc. Most of it is digital, and controlled with a few affordable hardware MIDI controllers. And most controls can be quickly and easily mapped with MIDI learn, which is fantastic! Thanks for that, truly. But…I can’t change presets from my controller. It’s often the one single action that I can’t do in hardware, and requires reaching out and tapping/clicking tiny arrows. It's driving me mad!
It’s 2023. We live in the future. Why can’t users MIDI-learn those buttons too?
There are already some hacky ways to do this with AudioBus, but it's rather involved and needs to be done through AudioBus for each app. I'd rather have a universal solution that can be handled per-app/plugin, and for situations where AudioBus isn't part of the workflow—perish the thought!
“But what about programchange? Didn’t MIDI already solve this?”
programchange isn’t offered by many hardware MIDI controllers, and the implementation varies between devices (if it’s supported at all).
programchange is also unidirectional, so the number of programs per bank (and the number of banks) is unknown to the controller. Also also,
programchange is limited to values between 1 and 128, so if you have 129 patches in a bank, tough luck. Also also also,
programchange requires defining a specific bank and program number.
programchange is antiquated, restrictive, and doesn’t allow for a workflow that matches the depth and variety of modern audio production tools. Opening up Prev/Next Patch buttons to MIDI-learn allows for a simple, input-agnostic way to interface with an app/plugin.
Anyone else suffering from this? Am I missing something here? Please tell me I'm bananas and there's a simple way to achieve this that I've missed because I'm an idiot, and I'll go on living my stupid idiot life while joyfully changing presets via my hardware controller.