VST3 only?

Dorico
81

Thank you Daniel and Ulf,

Problem solved. I can use my libraries. The instructions in “How to use…” are obviously unnecessarily complicated and outdated?

OT. Many years ago, when I started using Sibelius, Daniel was the limitless fountain of information and an important part of my decision to move from Finale to Sibelius. Perhaps the same happens again? The support staff for Dorico is in my opinion a crucial part of the system.


Happy again and slowly learning Dorico .

Leander422
Mac os x and all the rest

82

Are there any updates to the VST3 vs VST2 issue in Dorico v2 as of February/2019. What is the best method for using VST2 plugins with Dorico?

I’m having trouble identifying which vendors support VST3. They don’t clearly state it in their literature.

I would like to incorporate the Kontakt and Korg Legacy pluggins for starters.

83

Nothing has changed in the way VST plug-ins are handled in Dorico.
But it has become more easy to edit the whitelist and path for VST2 plug-ins.
Open the Dorico Preferences, switch to the Play tab and then scroll down to the VST Plug-ins section.
There you find 2 buttons for editing the VST2-whitelist and load path.

84

Thank you for your reply. That is certainly an improvement to what was before. I hope that users will be able to find info on this more easily. You now have an outdated knowledgebase article on it as well as numerous forum posts that are also inaccurate. This has been quite an ordeal to get VST2 plugins to work in Dorico and I’m by no means finished yet. It’s a great piece of software but your interoperability is lacking in this area.
I realize what Steinberg is trying to do by not wanting to support VST2 but remember what lengths Microsoft went to, to make sure their OS was always backward compatible with let’s say the Command Prompt. This had a lot to do with their success. After all, VST2 is also a Steinberg standard.

85

Forum posts show the date when they were posted. Given the speed of development of new features in Dorico since its launch, I don’t think there is any realistic way to update every post that now refers to an earlier version of the software.

In any case, as time goes by there will be users who still have earlier versions of the program, because they don’t have any need to upgrade just for the sake of it.

I agree knowledge base articles should state which version of the software they apply to, but that an article about Dorico 1.0 is still valid and useful while there are still people using Dorico 1.0.