Many thanks – for this and all you and the Team are doing.
I am using Dorico 3.0.10 Pro.
I reinstalled all of my software programs on a clean MacBook Pro (repaired by Apple with a new keyboard, a new trackpad and a new logic board including a new SSD).
I installed “Kontakt 5” and “Kontakt 6 Player” via “Native Access”.
The following is the result what I did in terminal:
prko$ cd /Applications/Dorico\ 3.app/Contents/Applications/VSTAudioEngine3.app/Contents/Components/VSTPlugManager.bundle/Contents/Resources prko-MBP2018:Resources prko$ ./vst2xscanner -p /Library/Audio/Plug-Ins/VST/Kontakt\ 5\ 16out.vst <?xml version="1.0" encoding="UTF-8"?> <vst2xplugin><path>/Library/Audio/Plug-Ins/VST/Kontakt 5 16out.vst</path><subCategory>Instrument</subCategory><cid>5653544E694F376B6F6E74616B742035</cid><editorCid>5653454E694F376B6F6E74616B742035</editorCid><name>Kontakt 5 16out</name><vendor>Native Instruments GmbH</vendor><sdkVersion>VST 2.4</sdkVersion><vendorVersion>126.96.36.199</vendorVersion><latencySamples>0</latencySamples><canDoublePrecision>0</canDoublePrecision><audioInputBusCount>0</audioInputBusCount><audioOutputBusCount>11</audioOutputBusCount><mainAudioInputArr>0</mainAudioInputArr><mainAudioOutputArr>3</mainAudioOutputArr></vst2xplugin>
What should I do?
Have I missed something?
Here is the diagnose report:
Dorico Diagnostics.zip (441 KB)
Hm, the output of the vst2scanner looks normal, still Kontakt 5 is on the blacklist. But once it is on the blacklist, it won’t get rescanned anymore.
Therefore, try to delete the file /Users//Library/Preferences/VSTAudioEngine3/Vst2xPlugin Blacklist VSTAudioEngine3.xml.
That will enforce a rescan on the next Dorico startup. What does it then look like?
Thank you very much!
It works now!
Dear Lillie and devs,
I’ve been struggling a little to whitelist Kontakt 6, because following the instructions in Help (https://steinberg.help/dorico_pro/v3/en/dorico/topics/play_mode/play_mode_vst_instruments_whitelisting_t.html?hl=whitelist) is actually misleading…
This help document is for Dorico3, therefore the folder in which all the xml documents have to be edited or deleted is called VSTAudioEngine3, whereas the document leads to the folder concerning Dorico 2. As I have Dorico 1, 2 and 3 in my machine, I understood that this number had nothing to do with VST but was about the version of Dorico. It might be useful to correct this
You shouldn’t need to manually whitelist Kontakt 6 in any case, since it’s just called “Kontakt” and is included in the default whitelist that ships with Dorico.
Well, Kontakt 5 was available in the VSTi list, but not Kontakt 6 (I bought the upgrade with the black friday offer), and I did struggle. Just thought it could be useful for you to have some feedback about this kind of little problems in the doc
Did you already have the Kontakt Player? When I purchased Kontakt 6, it just overwrote the Kontakt Player (also called Kontakt in my list). I had to check the “About” menu item to be sure it was indeed Kontakt 6.
I had Kontakt 5, and I still have it. Maybe my setup is strange, I don’t know (I don’t think I’ve done anything wrong though). But the doc is not accurate, that was the only purpose of my post
What I have heard is that NI decided to call Kontakt 6 just Kontakt to avoid users’ having to make changes (such as in the WhiteList) to access Kotakt each time a future upgrade becomes available. I suspect it is, in this one instance, causing a small amount of confusion as it initially did in my case.
To be absolutely clear, this is by no means the problem I was pointing. The help file clearly points to a folder that belongs to Dorico 2 instead of Dorico 3 (/Users/username/Library/Preferences/VSTAudioEngine2 instead of /Users/username/Library/Preferences/VSTAudioEngine3)
I’ve alerted Lillie to the issue.
Was there ever a fix found for the issue with Kontakt 6 being blacklisted in Dorico 3? I am struggling with this issue and none of the proposed solutions in this thread have fixed the issue.
I have tried adding “Kontakt” to the whitelist (being careful with EOL encoding), I have even tried copying the Kontakt entry from the blacklist XML file to the correspondng whitelist one myself.
Running vstscanner manually seems to work:
c:\Program Files\Steinberg\Dorico3\VSTAudioEngine\Components>vst2xscanner -p "C:\Program Files\Steinberg\VSTPlugins\Native Instruments\Kontakt.dll" <?xml version="1.0" encoding="UTF-8"?> <vst2xplugin><path>C:\Program Files\Steinberg\VSTPlugins\Native Instruments\Kontakt.dll</path><subCategory>Instrument</subCategory><cid>5653544E6924446B6F6E74616B740000</cid><editorCid>5653454E6924446B6F6E74616B740000</editorCid><name>Kontakt</name><vendor>Native Instruments GmbH</vendor><sdkVersion>VST 2.4</sdkVersion><vendorVersion>188.8.131.52</vendorVersion><latencySamples>0</latencySamples><canDoublePrecision>0</canDoublePrecision><audioInputBusCount>0</audioInputBusCount><audioOutputBusCount>59</audioOutputBusCount><mainAudioInputArr>0</mainAudioInputArr><mainAudioOutputArr>3</mainAudioOutputArr></vst2xplugin>
Nothing new on this at all? This is a major problem for my use of Dorico 3, as all my orchestral libs have been resaved to Kontakt 6 format. Any potential tips on solving this would be greatly appreciated. I had the same issue with Cubase blacklisting Kontakt, but here it was a simple case of adding it to the whitelist. That doesn’t seem to do anything at all in Dorico.
Sorry Jesper, just saw your posting now. Could you please attach a diagnostic report here, so I can first get an overview?
No problem. I have attached the diagnostic report.
Dorico Diagnostics.zip (900 KB)
Thanks for the data. Very strange that Kontakt 6 gets blacklisted. Please try following:
Navigate to C:/Users/Jesper/AppData/Roaming/Steinberg/VSTAudioEngine3_64
and delete the two files ‘Vst2xPlugin Blacklist VSTAudioEngine3.xml’ and ‘Vst2xPlugin Infos VSTAudioEngine3.xml’
and then restart Dorico. That will trigger a rescan of all VST2 plug-ins.
Because once a plug-in is on the blacklist, it won’t get scanned anymore.
So chances are, that then Kontakt 6 will get recognized, because as you wrote, manually invoking the scanner does produce the expected output.
If it still gets blacklisted, please create a new diagnostic report.
No dice. I have actually tried that already, but gave it another go now, unfortunately with no luck still. I cannot attach the new diagnostic report because it is too large (2.28 MB).
I have also tried removing the whole VSTAudioEngine3_64 folder, also without it fixing the issue.
There is a Memory Dump File in the Crash folder in the report, is that a clue?
Here is the diagnostics report with the Crashes folder removed.
Dorico Diagnostics.zip (887 KB)