Quote:
Originally Posted by schwa  The AU SDK is completely different. It's very highly designed and opaque. The overall design of the thing is much more carefully thought out than VST, the SDK is a bunch of actual encapsulations that give us a small number of fairly well defined places where we enter it. But because of the opacity and complexity, the SDK contains dozens of files and hundreds of functions and templates and multiply inherited methods, control can bounce around and back and forth and it is extremely hard to debug the SDK itself without maintaining a huge context in your head. |
By SDK are you talking about the audiounit base classes that come as part of the examples in the developer tools, that are used in the example plugin?
I always treat things like that which come as examples as just that.. but if the example doesnt work properly thats not so great!
As far as I know there isnt anything stopping you from implementing a bare bones audiounit in a similar style you would a vst using the functions described here:
Core Audio: Reference
what steve described does sound incredibly frustrating though, i can see why apple might want to keep their software close the their chests but i think thats misguided in this case.
i think logic is more the exception than the rule though, i've never had any problems developing on OS X, and perhaps apple don't realise how crucial big name third party plugin support is, which probably isnt the case with any of their other software.
i always got the impression emagic were quite unfriendly to third party developers too though. to me it seemed they didnt really care about people using plugins other than their own.. it took them forever to support multiple out vsts properly.