[john1192]

Originally Posted by deanrichard

I disagree, and very strongly.

AAX is a proprietary format. It's not an industry wide plugin format. The purpose of a proprietary format is to assure compatibility. When a company requires that all plugins used with their product conform to their proprietary format, it really is up to Avid to test plugins used with their products. They charge a premium price for their product so that it can be used reliably and with confidence in a professional environment. They set the standards, they issue the toolkits, they have a rigorous process that AAX developers must follow before a developer creates a plugin. In other words, Avid controls the process.

My guess is that one of the developers in the new project team made changes to how plugins work internally, and simply assumed he could make those changes without breaking existing plugins. In other words, he screwed up, and Avid's QA team screwed up by not catching it.

which plugins are your issue ?? help us help you .. lets narrow it down a bit .. john