VST2 and VST3 initialisation order

Hi, when creating VST3 versions of existing plugins I’ve noticed that the order of creation of certain events is different.

For VST2, setStateInformation() is called before createEditorIfNeeded(), which makes sense as state can be loaded before creating the UI.

For VST3, however, these are called the other way round. Was this an intentional chance for VST3, seems to make sense having the previous order for VST2.


I think that’s completely up to the DAW in question, not something defined by the spec (for either VST2 or VST3).

1 Like

ah, thx - good to know!

It’d be lovely if there was a wiki where all of this was described and updated for each DAW whenever we spot how something works :slight_smile: