Brian Willoughby wrote: > The AudioUnit documentation from Apple - what little there is - is plainly explicit that each plugin must use a unique class name for its Cocoa UI. Violating this requirement results in unpredictable results because it is unsupported. You need to avoid having multiple plugins with the same ObjC classes in them.
Mike/AQ wrote: > You might want to take a look at Symbiosis AU-VST. It does a great job of wrapping. Thanks guys, much appreciate your time! Symbiosis resolves the problem by generating Objective-C classes at runtime. It generates unique class names to avoid conflicts with other instances of the wrapper. For anyone interested in this technique in future, here is a link. https://www.mikeash.com/pyblog/friday-qa-2010-11-6-creating-classes-at-runti me-in-objective-c.html What I've resorted to at the movement is a script to modify the wrapper binary by search/replacing the Objective-C class name with a randomly generated name. For this to work, the replacement name must be exactly the same number of characters as the original name. Also the random number generator needs to be high quality to ensure two plugins don't end up with the same class name. *Seems* to work fine so far, even if it seems like a nasty kludge. Thanks again, Jeff McClintock _______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
