Hi all!
I hope to get a little insight into the best practices of vst3 development. I know that Steinberg kindly insists on using the dual component architecture (AudioEffect+EditController), while other respected sources, e.g. Will Pirkle, advocate for the single component one (SingleComponentEffect).
I'd like to gather some real-world statistics and hopefully hear about your experience with either approach.
Do you use single or dual component vst3 architecture, and why?
-
- KVRian
- 1273 posts since 9 Jan, 2006
I don't use VST3 directly anymore (so this info is hopefully out of date 
) anyway I switched to single component as some hosts, including Steinberg's, couldn't be relied on to always pass parameter changes between components
) anyway I switched to single component as some hosts, including Steinberg's, couldn't be relied on to always pass parameter changes between components-
- KVRian
- 653 posts since 4 Apr, 2010
-
- KVRist
- 135 posts since 9 Apr, 2017
Tried dual the first time I build our VST3 adapter. Didn't work out really well. Switched to single component and worked like a charme.
-
Jeff McClintock Jeff McClintock https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=56398
- KVRist
- 413 posts since 30 Jan, 2005 from New Zealand
I use the modern dual-component architecture because it encourages you to use a cleaner design. And a cleaner design, especially in the realm of concurrency, pays off in terms of reducing the number of defects (bugs) you will have to deal with.
"Separation of Concerns is one of the most important concepts that a software architect must internalize"
https://medium.com/machine-words/separa ... 735b703a60
"Separation of Concerns is one of the most important concepts that a software architect must internalize"
https://medium.com/machine-words/separa ... 735b703a60
