Let us know which VST2.x plug-ins are working in Dorico

[Terry_Jones]

@Ulf

@delmonteguitar

Can some one tell me weather “Play” from East West Quantum Leap orchestra sample library works with Dorico?

Play 4.3 does work, but Play 5.0.0 is known to make trouble.
Good news is, East West is aware of this and will release an update soon,
so have a look for updates at East West.

That is good news as i have 5.0.0 installed now, hopefully it won’t take too long.

[dhbailey52]

I finally got Play 5.0.1 working in Dorico!!! Yippee!!!

Thanks to Daniel and the team!

[Terry_Jones]

@dhbailey52

I finally got Play 5.0.1 working in Dorico!!! Yippee!!!

Thanks to Daniel and the team!

Great stuff, look forward to trying this out myself now.

[Hans_Nel]

EWQL PLAY as described by the person in a post higher up did not work, but was rejected.

BUT PLAY 5.01 DOES Work with Dorico!

1. Install Play 5.01
2. Copy this file vst2whitelist.txt (found here: c:\Program Files\Steinberg\Dorico\VSTAudioEngine\Components) to your desktop. VERY IMPORTANT! Windows 10 will not allow you to meddle with files, so you have to “trick” Windows 10.
3. Open this vst2whitelist.txt file (on desktop) and make sure you have these lines in there. (Just copy and past it in there)

Kontakt 5 16out
5653544E694F376B6F6E74616B742035
play_VST_x64
565354706C6179706C61795F7673745F

4. SAVE!
5. Copy/Move the vst2whitelist.txt from your desktop back to [c:\Program Files\Steinberg\Dorico\VSTAudioEngine\Components]. If administration permission is required…give it.

PLAY NOW SHOULD WORK. IT DOES FOR ME!

[Judith_Markovich]

@jtyf

Anyone tried Ivory II?

I tried Ivory II and didn’t work on my system as of January 2017.

[dspreadbury]

I believe Ivory II should work provided it’s correctly whitelisted. Were you able to find the GUID etc., Judith?

[Nickie_Foenshauge]

1. Kontakt 5.6.6.16
2. Windows 10 Home

Kontakt 5 16out
5653544E694F356B6F6E74616B742035
Kontakt 5 8out
5653544E694F356B6F6E74616B742035
Kontakt 5
5653544E694F356B6F6E74616B742035

1. Pianoteq 5.8.1
2. Windows 10 Home

Pianoteq 5 (64-bit)
565354507435717069616E6F74657120

1. Aria Player 1.6.6.6
2. Windows 10 Home

ARIA Player VST_x64
565354474152416172696120706C6179
ARIA Player Multi VST_x64
565354474152616172696120706C6179

[dnedwek]

Thank you very much, Dorico team, for today’s code upgrade. If I may make a request for the next upgrade, please don’t over-write the whitelist file (or perhaps move the existing one to a different name).

[Derrek]

Not sure why this is so, but I added the 64-bit Aria players to my whitelist in the original release of Dorico, and this (along with several VSTs from Sonar that I did not add explicitly) have persisted through all the upgrades.

[Hans_Nel]

OK!..

EWQL SPACES also works beautifully with Dorico.

Just install SPACES as usual…no need to put the dll anywhere else,

THESE are the lines in my white list file:

Kontakt 5 16out
5653544E694F376B6F6E74616B742035
play_VST_x64
565354706C6179706C61795F7673745F
VirtualSoundStage2_x64
565345506172617669727475616C736F
QL Spaces x64
56534545575350716C20737061636573

and VOILA!! check out piture attachment!

I’m starting to think that the boys at Steinberg got a bit (just a tad) cynical regarding adding evidently quite a large number of VST2 instruments. Forgive me, I don’t mean o be rude or anything, but I know we all have the honor to deal with the BEST out there! If somebody can make things work, it’s YOU guys!

May the LORD bless you and keep you and let His face shine upon you this weekend!!

Hans

[tonywardarts]

For future updates, I’ve created a go-folder to make preserving and updating my whitelists easy.

1. Create a folder on your desktop (or other easily accessible location) called, e.g., “Dorico VST.”

2. Go to the folder where defaults.xml is located, and create a shortcut/alias. Place it in the new folder.

3. Copy (do not alias) your defaults.xml file into the new folder as well.

4. Repeat steps 2-3 for the VST whitelist file.

5. Done! Now, when Dorico updates, you can restore your whitelists by copying the files into the aliases of their proper folders. This also makes it easier to update those files for new VSTs.

[Ulf]

@tonywardarts

For future updates, I’ve created a go-folder to make preserving and updating my whitelists easy.

In order to save you from all this pain, with the next update (1.1) we will add the ability to have a second whitelist that goes into the user directory and won’t get touched by the updater. So the audio engine then reads both whitelists and merges them .

[tonywardarts]

@Ulf

@tonywardarts

For future updates, I’ve created a go-folder to make preserving and updating my whitelists easy.

In order to save you from all this pain, with the next update (1.1) we will add the ability to have a second whitelist that goes into the user directory and won’t get touched by the updater. So the audio engine then reads both whitelists and merges them .

But… my neat shortcut!!

[tonywardarts]

So, what would be the chances that the D-Team could just add all these VST2s to 1.1’s default whitelist?

[Ulf]

@tonywardarts

But… my neat shortcut!!

You won’t need to use the new user whitelist if you don’t want. You can still stick to the old scheme and use your neat shortcut.

[tonywardarts]

@Ulf

@tonywardarts

But… my neat shortcut!!

You won’t need to use the new user whitelist if you don’t want. You can still stick to the old scheme and use your neat shortcut.

I think I’ll find a way to cope.

[wcreed]

Just an FYI that EW released Play 5.0.2 today, with VST3 suport.

[carlvandoorne]

Hi,

Xln addictive keys works great!

Greetings
Carl

[Terry_Jones]

@wcreed

Just an FYI that EW released Play 5.0.2 today, with VST3 suport.

Now the $64,000,000 question… dare I risk updating to it.

[jmatos]

How can I access VST2? I can only see VST3s. Thanks