sdk.steinberg.net

@jwatte thank you for the very detailed explanation

As a host you always have a pointer to the IAudioProcessor part and the IEditController part of a plug-in. The host doesn't care in this case if the implementation is in one class or two. It just calls audioProcessor->setState() and editController->setState (). The hack is needed so that a plug-in ...

This confirms what I was thinking.

Thank you

Yan

First of all. It's still not recommended to use it. We know that people coming from vst2 like to use it, because it uses the same hack friendly way of coding as vst2. So a clean separation between audio processor and edit controller is the recommended way of writing a VST3 plug-in. But to answer yo...

I have some follow up questions on the usage of the factory. 1) Can a host/daw create a factory when it starts (for example it loads all possible plugins) and whenever an instance of the plugin is needed it uses this factory? Or must a host/daw call GetInstanceFactory() for each plugin it creates? 2...

For what it is worth, the only thing that I am interested in, with this model, is the ability to share (large amounts of) data between the UI and the RT without having to use messaging and I know and am very well aware of the data race issues involved in this. I am absolutely not interested in writi...

First of all. It's still not recommended to use it. We know that people coming from vst2 like to use it, because it uses the same hack friendly way of coding as vst2. So a clean separation between audio processor and edit controller is the recommended way of writing a VST3 plug-in. But to answer yo...

Following the discussion in this thread I implemented a quick plugin that follows the SingleComponentEffect pattern and verified that it works fine both in VST3PluginTestHost as well as a VST2 plugin (meaning the vst2wrapper code does the "right" thing). I am trying to figure how if this is somethin...

Hmm... I did not know about this class or concept. I will look into it as one of my plugin could really benefit from it!

Thanks
Yan

@MarkusK I suppose I misunderstood what you were trying to do. I thought you had data in the RT code that you wanted to share in the UI and unless I am mistaken that is not what you are doing. Or is it? What is this T2Audio* pointer? How do you get it? Is it shared between RT code and UI? If so how ...