31st March 2014
I can't speak to what Auganizer's doing, or the ramifications of altering plist files (that's not precisely code, but it is part of the Audio Unit all the same: it's included in the component package) since I'm not really sure what exactly is being done myself. To some extent when you get into modding systems to work differently, it's a given that SOMETHING will be changed and as it happens you don't have to change the executable code to do this. It's a bit like pasting on a different icon, only a little deeper and less user-accessible. I could see scenarios (having to do with sandboxed code, probably) where making any changes to the signed package would be bad.
I don't think that holds today. Seems to work fine for now. We are all, as Sean says, rather at the mercy of Apple to not break stuff and avoiding Auganizer isn't a guarantee of total safety. Even I had to update all of my plugins and freebies and legacy plugs to run 64-bit (a couple years ago) and my stuff is about as immune to such growing pains as anything could be. There's literally nothing to it but the audio code, by design: but if Apple does something really epically broken, I'm on the hook along with everybody else to update the lot.
What I can say to Auganizer users who're also Airwindows users is the same thing some people have learned through personal hardship: I'm a tiny company, just one autistic nerd trying to scrape by through audio performance alone, and willingness to help customers.
So, if Auganizer ever breaks anything ever, email me and I will send you a fresh copy, just like I've done a bunch of times to victims of hard drive crashes
I suppose if you stole the Airwindows plug in the first place and then it broke, you wouldn't be in my records and thus out of luck, but expecting support in that situation is a little beyond fair. In that case the support is a one-time $50 of buying the thing properly…