Transition from 4.1.0 to 4.3.1 and AAX I/O issue

I think that current approach should be changed - otherwise we’ll always have a solution when no plugin update is possible if you want to add supported I/O.

So everyone who release a plugin with one I/O settings will stuck with no chance to smooth update even if it comes to simple adding new supported layout. And then the only way would be releasing new product with another name/binaries etc. - which is nonsense for small update.

This approach (continued from the very beginning of AAX wrapper) is unfortunately against the AAX SDK assumptions and IMO it should be fixed.

Just my two cents :slight_smile: