I’m not convinced it’s a good idea to add this feature. The docs for this feature flag say that it is supported “for now”, which implies that this might change in the future. Also, other plugin formats do not make guarantees about which threads may call the get/set state functions. A plugin that requires this feature will likely be broken when exported as an AU/VST3/etc, even if the issue is masked in the AAX version of the plugin. Ensuring your state functions are threadsafe will ensure that your plugin will work, even if the AAX_eProperty_RequiresChunkCallsOnMainThread feature is removed, or the plugin is exported in other formats.
1 Like