True MIDI CC support in effect Audio Units (kAudioUnitType_MusicEffect vs kAudioUnitType_Effect)

dspguy

Dear Devs,

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.

dspguy

I've improved the title, but by that time it was already off the front page, and only received 1-2 views since then. So trying to give it one more bump before giving up.

TonalityApp

No drawbacks as far as I remember, though probably worth testing it out with your app just to make sure. You may have more luck over at the developer forum: https://heroes.audiob.us/

dspguy

@TonalityApp said:
No drawbacks as far as I remember, though probably worth testing it out with your app just to make sure. You may have more luck over at the developer forum: https://heroes.audiob.us/

Oh my! Thanks very much.
I was totally oblivious to that forum, too.