Ugh, I don't think that was the best advice. Particularly on a freshly installed system. Oh well...masterhiggins wrote:Hi there. Thanks for the info. I've performed the cleanup scrips with Onyx. MacHelpMate appears to be for an older version of OS X (10.6). I ran all of the maintenance tasks, repaired the permissions, and manually repaired the permissions on the AU and VST folders. I wasn't able to see an option for deep cleaning on reboot, but I'll try to look more tomorrow.mcnoone wrote:Try this.
http://www.machelpmate.com/index.php?op ... &Itemid=33
Run all the maintenance tasks.
Then repair the permissions.
See if it helps.
The cache cleaning, and "deep cleaning on reboot" are the important ones.
Also try to manually repair permissions on the vst, and au folders.
It's not a matter of laziness. Rather, sanity.
AdmiralQuality,
Why do you suppose some developers choose to use a VST3>AU wrapper instead of just porting to AU directly? Do most developers do it or is it just a "lazy" way to package an AU plugin? I'm not a developer, of course, but I'd imagine that wrapping a plugin in another format would only increase the odds that the plugin would inherit vulnerabilities from the weakest point (in this case VST3). Is this not true? Thanks!
-Sam
We don't like to write the same code twice, only differently. It's hard enough to keep one version of the code sane. 90% of our work goes into GUI. To do an entirely separate code base for the two platforms means twice as much work developing the plug-in, and twice as much work maintaining it and tracking its issues.
And no, there's nothing inherently wrong with wrapping. Because both VST and AU versions are supposed to do the same things, it makes perfect sense to develop for one and wrap to the other. (And as AU has no use on Windows, VST wins as the common format.) But it's just that Steinberg have done a fantastically bad job with VST3.x, which offered a wrapper to AU as one of its "selling points". I use another, open source wrapper called Symbiosis, and it works great.
The value of a wrapper is there's only ONE wrapper to test and debug for ALL products that use it. Really a VST2.4 and an AU do almost exactly the same things. It's just a matter of translating one interface protocol to the other. (And no, there's no noticeable performance penalty.)
You shouldn't assume there's anything "weaker" about VST by the way. It's just that VST 3.x is a giant steaming turd, hence the lack of adoption by the industry and no hosts that I'm aware of that require it (that can't load a VST 2.4). VST 2.4 is wonderfully well tested and used by literally thousands of stable products. It's actually AU that has the horrible rep and very poor support from Apple. (They even neglected to include the necessary headers to compile an AU in their latest development platform! You have to go digging them up yourself and patching them in. Uncool!)
