Approach to building an AU which i… | Apple Developer Forums

Approach to building an AU which is both effect and instrument

I've been selling an AU for some time now that includes both instrument and effect versions as separate bundles.

One of the issues with this has been namespace collisions of objective-C class names when both instrument and effect versions are loaded. I've followed this advice:

https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/LoadingCode/Tasks/NameConflicts.html

Specifically, I have macros such as the following:

#ifdef AUDIO_UNIT_EFFECT
#define AntimatterAUViewFactory ComSubatomicAudulusEffectAntimatterAUViewFactory
#else
#define AntimatterAUViewFactory ComSubatomicAudulusAntimatterAUViewFactory
#endif

However I've noticed in Xcode 6, this defeats interface builder's ability to parse headers and thus I can't fully edit my xib files.

So I'm curious how others deal with building an AU which has both instrument and effect versions? Could both versions be put in a single bundle?

(Looking forward to the new app extension based AU API!)