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.
True MIDI CC support in effect Audio Units (kAudioUnitType_MusicEffect vs kAudioUnitType_Effect)
I'm developing an audio unit effect, and at a later point I would like to add MIDI as a way of controlling it (beyond the current AU parameter handling).
I figured I would need to mark it as "aumf" before release, in order not to break it in future in people's projects.
Which got me thinking - why do Eventide plugins come in both versions? Are there some fundamental differences between the AU types other than one allows for MIDI compatibility? On an API level is there a stronger reason for this distinction other than being sort of a feature flag - I guess it would be a heavy-handed way just to implement feature flagging (i.e. telling Core Audio not to dispatch MIDI events to it, etc.)...
Is there a drawback or a risk of any sort in going with aumf (instead of aufx) for the purposes of seamlessly adding MIDI capabilities in a future app update?
Thanks in advance.